Just a general question I would love some opinions on. How do you all manage having products "out there" in different flavors and versions as well as a version under development?

Basically I am trying to figure out a better way to have a given version of a given program preserved while I move on with development. For instance, I publish and distribute a version of an application, lets call this version 1. To support version 1's userbase I need to have a copy of that code, database, and other pieces that make up my application so I can debug here if necessary. Now I have version 1.5 in development that has some simple, and some not so simple changes to all the assets of version 1. See where I am going. It was easy in VFP, (inzip your application folder and you were good to go), with .NET, SF, DDT, BO projects, security projects, version control, etc I am just not sure what is the best way to go as we start having some more stuff out there in he world in different flavors and versions to support.

This is probably something some of you take for granted and I would appreciate your opinions. I have several products now that I have to maintain the environment described above.

Keith Chisarik

Just a final thanks, I am up and running and have my biggest current project ripped out of VSS and into subversion with three developers working on the trunk and a BRANCH for my current production version... awesome!

I love the flexibility of the product too, many more features than I ever had with VSS, I scared some of my guys when I showed the them "Blame" button 

Keith Chisarik

That is an important button...and there is no arguing about who screwed something up! (it just sucks when it proves that you (meaning me) screwed it up )

Hey guys, I have been using the Vault tool for a while, but after the links posted here about the VisualSVN client and server I just thought it would be worth setting up a test.

I had tried SVN a year ago or so, and for me it was such a pain to set the server and then working with it, etc., that I just went to Vault. This VisualSVN Server solved it, it is amazing. Then I installed the Client and here goes some impressions:

• The integration with VS has been working fine. To be honest, VS seems to be working a lot faster.
• I like the Update process better, making it easy to work offline with the notebook when needed. New files added to the solution while offline are found a lot easier then with Vault.
• The price is good, US$49.00 each seat. There is a discount policy apparently for quantities. Vault is something near US$200.00.
• It is a file system based source control, so there has been some need to create command line batch files using svnadmin to produce backups, Vault is based on SQL Server, but no big deal.

So, so far so good.

Hummm, guess it is time to move to VisualSVN, I did a quick look at the demo video and I liked what I saw too.  Still need to digest Greg's long post about branches, man, too many things too fast .

Edhy Rijo