Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / General / December 2005

Tip: Looking for answers? Try searching our database.

Project References or Assembly References?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
cmay - 15 Dec 2005 15:03 GMT
On my current project we work on basically 1 big intranet site that is
made up of about 20 or so projects.

There are some differing opinions as to if we should have 1 large
solution with each project referencing each other, or if we should be
compiling the projects into assemblies and referencing those.

The benefit of compiling the projects and doing references by DLL is
that you can work on a single project w/o having to load up and build
every project in the entire solution.

The downside is you have to rework the references if you want to debug
stuff (if you need to debug across projects you can't have DLL
references, you need project references) and also we have run into some
issues where 2 assembiles are expecting different versions of the same
common assembly and it takes some work trial and error to find the
problematic DLL.

On the other side, if you use project references you have to load up
every project in your application just to make a small change, and
rebuilding will take much longer.

Is there any guidance out there on this issue?
Kevin Spencer - 15 Dec 2005 18:42 GMT
Are you using Source Control? If you use Source Control, you can have a
whole slew of projects in your solution, and each developer keeps his/her
project(s) checked out, to prevent other developers from changing it. Using
the Configuration Manager prevents any projects the developer doesn't want
built from being built when debugging. And you can still step through code
in the other Projects.

Signature

HTH,

Kevin Spencer
Microsoft MVP
.Net Developer
You can lead a fish to a bicycle,
but it takes a very long time,
and the bicycle has to *want* to change.

> On my current project we work on basically 1 big intranet site that is
> made up of about 20 or so projects.
[quoted text clipped - 19 lines]
>
> Is there any guidance out there on this issue?
cmay - 15 Dec 2005 19:51 GMT
Kevin,

First off, sorry about the multiple posts... google had some error
pages when I was posting, guess it was in fact going through.

Anyway, yes we are using VSS, and I am familar with the technique you
describe.

The new TFS feature of "shelving" would make this methodology work even
better IMO.

Is this (using project references) the "best practice" as far as MS is
concerned?
Kevin Spencer - 15 Dec 2005 22:19 GMT
I haven't had the opportunity yet to work with TFS, but I'm looking forward
to it. Just waiting for the release of the Team System first. As for using
Project references, well, we've been doing that for so long I couldn't tell
you how we came across it. You can always check out the Microsoft Best
Practices site and see what you can find there:

http://msdn.microsoft.com/practices/

Signature

HTH,

Kevin Spencer
Microsoft MVP
.Net Developer
You can lead a fish to a bicycle,
but it takes a very long time,
and the bicycle has to *want* to change.

> Kevin,
>
[quoted text clipped - 9 lines]
> Is this (using project references) the "best practice" as far as MS is
> concerned?

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.