Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Multiple .NET targets - "One" Source - Best scheme

1 view
Skip to first unread message

Ioannis

unread,
Oct 23, 2009, 7:29:01 AM10/23/09
to
I have a solution with many asseblies, both class libraries and applications,
which I'm about to release as different products. The solution and the
corresponding projects are already attached to source safe and currently all
projects target .NET Framework 2.0.
What I'd like is to have a flexible and robust source safe "scheme" and be
able to target the other .NET Framework versions (3.0, 3.5, the upcoming 4.0,
etc.) as well, but maintaining efficiently my sources. For example, fixing a
bug in a source file for version 2.0 will also updates version 3.5.

I am a little confused right now.


--
If the facts don''t fit the theory, change the facts.
Albert Einstein

Jeff Clausius

unread,
Oct 23, 2009, 9:45:59 AM10/23/09
to
Ioannis,

Is the code the same between .NET versions or is it different taking
advantage of specific .NET Framework features? If the code is
different, you could look at sharing and branching between the different
assemblies into sibling folders w/ different names for the respective
.NET versions.

Then if you fixed a bug in one of the branches and you wanted to get
those changes into a different project folder, you could merge the
file's branch back to the source. And from there, I think you can merge
those changes to the other .NET branches.

HTH

Jeff Clausius
SourceGear

---------------------

Hold on to your hats VSS users! It's coming!! SourceOffSite 5 -
http://www.sourcegear.com/sos

Ioannis

unread,
Oct 28, 2009, 8:20:01 PM10/28/09
to
Currently, the codes contain only a subset of the .NET Framework features
needed
and this is version 2.0.

The idea was to first create the code using a "least common denominator",
then
deploy for all the available .NET versions, and then maintain the separate
.NET versions, but taking advantage of each version's features.

As soon as we release the products for the other .NET versions (3.0, 3.5,
and 4.0), then we'll start using distinct features based on the .NET version
of the products.

I guess I'll have to focus on "sharing" and "branching".

Thank you Jeff.

--
If the facts don''''t fit the theory, change the facts.
Albert Einstein


"Jeff Clausius" wrote:

> Ioannis,
>
> Is the code the same between .NET versions or is it different taking
> advantage of specific .NET Framework features? If the code is
> different, you could look at sharing and branching between the different
> assemblies into sibling folders w/ different names for the respective

> ..NET versions.

Jeff Clausius

unread,
Oct 29, 2009, 12:11:56 PM10/29/09
to
NP. Good luck.


Jeff Clausius
SourceGear

---------------------

SourceOffSite 5 is here, and the new UI is changing the way people think
about Visual SourceSafe! Try the demo today -
http://www.sourcegear.com/sos/

0 new messages