Code Sharing using vs.net 2005 (no team suite)

[Matt Owens]

Hi,

Im setting up a new project in which I'd like to share code across
numerous other projects, specifically a control library and an array
of common objects. Im not really sure how best to go about this, i've
done this two ways in the past and both have proved a little
problematic.

1) Create a new solution in a common area with a common name for all
projects to share. This is fine, although there's the overhead of
having 2 solutions open at once as I tend to develop components (or at
least augment them) simultaneously as I do the view or IDE instance.
Also with this method its a bit of a build nightmare, unless you use
the GAC which can be longwinded.

2) Create a project in a common place and import that (open from
source safe) into my project solution and use there. This seemed a
better solution to be honest the biuld output directories are a pain.

Does anyone know of a better solution to tightly integrate code across
numerous projects? Should I make extensive use of the GAC? Am I
missing an easier solution?

Thanks and regards
Matt

[Cor Ligthert[MVP]]

Matt,

Do it whatever you want using source save. You have with dotNet nothing to
do with the GAC as long as you not are using old COM objects.

I would avoid more projects as it is not about typical functional projects
(meant for the programmer not for the enduser). Such a functional project
can be a method or a class library, however be then sure that nothing can
change in that anymore as you start your end user project.

The last is not needed, you can build a solution that exists from more
projects, however is just my idea how it should be done.

Just my opinion.

Cor

"Matt Owens" <m.*****@lbs-ltd.comschreef in bericht
news:11**********************@y42g2000hsy.googlegr oups.com...

Hi,

Im setting up a new project in which I'd like to share code across
numerous other projects, specifically a control library and an array
of common objects. Im not really sure how best to go about this, i've
done this two ways in the past and both have proved a little
problematic.

1) Create a new solution in a common area with a common name for all
projects to share. This is fine, although there's the overhead of
having 2 solutions open at once as I tend to develop components (or at
least augment them) simultaneously as I do the view or IDE instance.
Also with this method its a bit of a build nightmare, unless you use
the GAC which can be longwinded.

2) Create a project in a common place and import that (open from
source safe) into my project solution and use there. This seemed a
better solution to be honest the biuld output directories are a pain.

Does anyone know of a better solution to tightly integrate code across
numerous projects? Should I make extensive use of the GAC? Am I
missing an easier solution?

Thanks and regards
Matt