Hey guys and gals,

I've been using basic subversion source control for a while now on all my commercial DNN module development and I have to say it works really nicely. I've recently been messing around with the branch/merge capability to branch off feature changes etc. but due to the fact that the feature could entail db changes it really means doing the feature change against a whole new DNN instance so the db changes aren't messed up in the trunk version of the module. When I do this, of course I also have to change the IISUrl settings in the vbproj file so it starts the proper web app while I'm developing/debugging the new feature. When I try to merge the feature back it's also merging the vbproj file settings which I don't want.

Is anyone here successfully using subversion to manage their DNN module branches or are you only using it for trunk updates and that's it?

I'd like to get a little more out of subversion because sometimes the feature changes take place over time and I want the trunk available for quick bug fixes etc.

Anyone using subversion and DNN at all? Maybe we can compare notes and come up with something.

Hi Nick,

I'm using Visual SVN Client for VS and also their Visual SVN Server product, very nice combo. I kind of figured out today what I think I'll do. Basically I can work on both the trunk and feature branch at the same time, then merge the feature into the trunk using Tortoise and then revert the vbproj file merge so it goes back to the last checked in version of the trunk. That will at least get me to the point where all the code is merged. The only thing I'll lose there is if I've added, renamed files in the branch. If so I'll just have to manually add them to the trunks vbproj file and check in again.