I think this is a simple question with a simple answer, but I guess I'm missing some important keyword(s) in my searching.
I've just installed VisualSVN 1.5.3 with VS 2005. I'm pretty well experienced with Tortoise and Ankh combination. I've just completed a small project in C# (.NET 3.5) and I'd like to start a coherent strategy for maintaining this project and others like it into the future. The basic idea was well-described by 'discoguy77' back in august with the thread "Will VisualSVN work without checking in solutions?". Let's simplify a bit further and say we have a project to be compiled into a dll called LIB, and two solutions: MyApp, and HisApp both of which use LIB. My question (really just a restatement of discoguy77's) relates to the fact that VSVN seems to require that I can only IDE-versioning with projects that are checked in as solutions. That is, there is only one menu option for getting or adding from/to a repository, and that's at the solution level. Am I understanding this right? If so, how can I check out just a project (eg, for a library assembly) and use within a separate solution, either MyApp or HisApp? I'm envisioning getting LIB functional/stable in MyApp, and using it in HisApp with occasional minor enhancements or bug-fixes, whatever. I'd be interested in a general discussion of best practices, but what I really want is to do something simple: work with multiple VS projects under a single solution and have VSVN play along (Ankh does). Is this too much to ask? Many thanks. -Chris.
