Nope, we don't have to agree. It's ok with me. <g>

I think part of the decision-making on how to proceed with this depends on what Source Control you're using. Sounds like you're using Source Safe. Source Safe is a lot more flexible, IMHO. We're using TFS (Team Foundation Server). There are lots of things I like about TFS (it's speed being the major benefit), but it has it's quirks ... some of which are a real PITA. If I recall, I think it's inflexibility with mapping of workspaces is the main reason I took the approach we are taking.

With either methodology, you *still* have to get the latest stuff for all your applications each time the Framework changes, so I think that's a non-issue. With TFS, the Framework "librarian" (that's me ... and I hate that some of the guys have started calling me that <g>) will make things easier by merging Framework changes to all applications (this is easy to do in TFS), so each individual developer will not need to worry about that ... all a developer has to do is get the latest stuff in their application directory from TFS for whichever app they are working on.

~~Bonnie




>See Bonnie I have to disagree with you on this one, a solution is nothing more then a holder for projects, those projects can be all under 1 main directory or across many directories.
>On your approach you still create your solution tree in SS I guess so you will have to branch all your 17 framework projects into the new solution, alot more work and more error prone then just go into the new solution file in VS.net and right click on it and say add existing project 17 times.
>Other thing is then if you change something in your framework then all developers need to get the framework versions from SS across all solutions, IMO this is a PITA.
>
>But this is only my opinion, we don't need to agree on this. ;)
>
>>Hi Alexandre,
>>
>>For a small-sized Framework, or if one is not using Source Control, that might be ok. Our Framework consists of 17 projects spread out over several different layers. I think it's much easier to start out with everything in place rather than have to add 17 existing projects to a new solution every time I start a new app.
>>
>>~~Bonnie
>>
>>
>>
>>>Hi Bonnie sry to jump in but you don't need to do all of this, in your solution you just right click on it and say add existing project, then select your framework project and voila that's all you need VS.NET 2005 will see that the project is already under SS control and all is OK.
>>>