Re: Partitioned Single Solution Model
From: Peter Lillevold (peter_at_dezibel.com)
Date: 02/20/05
- Next message: Juergen Marquardt: "VC6 and SourceSafe: Wrong database connected"
- Previous message: patrick_t_griffiths: "file history after share"
- In reply to: John Cronan: "Re: Partitioned Single Solution Model"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 20 Feb 2005 10:34:41 -0800
Hi John!
Hehe, I would like that t-shirt too.
I'm not sure what you mean by "wait for MSBuild". MSBuild is the build engine
for both Visual Studio 2005 and the Build part of Team System.
And the project reference model is the same as in VS2003, so dont expect
any help there.
The only other option is to go with binary dependencies. With VS2003 this
is hard because you would manually have to distribute new binaries within
VSS or to some other common repository. With a Continuous Integration system,
like Team Build, you could have the binaries automatically compiled and distributed
whenever new code is checked into source control. This scenario let you operate
with solutions containing only those projects you actually need to work with.
Regards,
Peter Lillevold
http://blogs.eternia.cc/peter
> Thanks, Peter.
>
> MS' best practices document doesn't really make the
> dependency/references issue completely clear IMO. Oh, well, I was able
> to get it set up anyway.
>
> Do I get a T-shirt for this? "I set up Partitioned Single Solution in
> Visual Studio .NET"?
>
> Do you happen to know if any of this is easier in Team Services or do
> we have to wait for MSBuild?
>
> JC
>
> "Peter Lillevold" <peter@dezibel.com> wrote in message
> news:18763632442324229386432@msnews.microsoft.com...
>
>> Hi!
>>
>> Yes, Im doing Partitioned Single Solutions.
>>
>> You are perfectly correct. If A depends on B, whatever solution you
>> put A
>> into, you must also include B.
>> And for our example here, C is the top project since it depends on
>> both A
>> and B. Thus a solution containing C must also include A and B.
>> Now, the benefit of partitioning solutions is that if you're on a
>> team
>>
> that
>
>> is not involved with project C (Team1 in our example) you can
>> perfectly
>>
> well
>
>> set up a solution including only A and B.
>> For Team2 there is nothing to gain here. Even if a dev is not
>> interested
>> in either project A or B you must include them in order to have
>> project
> references
>
>> in project C.
>>
>> Figure 3.3 illustrates this quite well I think:
>>
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda
> /html/tdlg_ch3.asp
>
>> Regards,
>> Peter Lillevold
>> http://blogs.eternia.cc/peter
>>> Hi guys,
>>>
>>> I have run into a references problem with Partitioned Single
>>> Solution. It goes like this:
>>>
>>> If projects A & B are in the same solution then A needs a project
>>> reference to B. If A & B are in different solutions A needs a binary
>>> reference to B. So you can't have multiple solutions where one
>>> contains both and one contains only A. It's impossible.
>>>
>>> So I have to ask: Has anybody successfully done Partitioned Single
>>> Solution?
>>>
>>> John
>>>
>>> "Peter Lillevold" <peter@dezibel.com> wrote in message
>>> news:6340632440876078220016@msnews.microsoft.com...
>>>
>>>> Hello kh,
>>>>
>>>> The trick is to have one master solution in VSS containing all
>>>> dependent
>>>> projects.
>>>> In your case that would be A, B and C. Next step is to have one or
>>>> more
>>> solution
>>>
>>>> files,
>>>> one for each team or "sub-project". These solution files have only
>>>> those
>>>> projects you want
>>>> to work with. Again, in your case, the Team1 solution should
>>>> contain
>>> projects
>>>
>>>> A and B (since B depends on A) and Team2 should contain A, B and C
>>>> (since C depends on both A and B).
>>>>
>>>> You can choose to have these team solution files in VSS or not,
>>>> though
>>>>
>>> since
>>>
>>>> several people are
>>>> going to use them it is probably a good idea to have them in there.
>>>> Peter Lillevold
>>>> http://blogs.eternia.cc/peter
>>>>> fwiw, this is not a web project
>>>>>
>>>>> "kh" wrote:
>>>>>
>>>>>> Hi. I have been reading the "Team Development with Visual Studio
>>>>>> .NET and Visual SourceSafe" guide on MSDN. The "Partitioned
>>>>>> Single Solution Model" sounds like it might fit the bill for my
>>>>>> current client project, but I do not understand how I would first
>>>>>> set this up in VS.NET and then add the Solution(s) to SourceSafe.
>>>>>>
>>>>>> Say I have an existing single Solution with three Projects (A, B,
>>>>>> and C) but I want some developers to work on Projects A and B in
>>>>>> a one Solution and other developers to work on Project C in
>>>>>> another Solution.
>>>>>>
>>>>>> Project B depends on Project A, and Project C depends on Projects
>>>>>> A and B. What steps should I follow so that I have a "Master
>>>>>> Solution" for production builds and subsolutions for the two
>>>>>> developer groups? And how do I then add these to SourceSafe?
>>>>>>
>>>>>> Many thanks
>>>>>>
>>>>>> kh
>>>>>>
- Next message: Juergen Marquardt: "VC6 and SourceSafe: Wrong database connected"
- Previous message: patrick_t_griffiths: "file history after share"
- In reply to: John Cronan: "Re: Partitioned Single Solution Model"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
