472,990 Members | 3,750 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 472,990 software developers and data experts.

Project-->Project References Large Project

Does anyone have experience using project->project references in large
solutions? What are the plus/minuses that you have found?

Currently, we are using the binary assembly references for our code,
but this becomes problematic when you want to build from multiple
branches/working directories.

Any thoughts on this would be appreciated.

Thanks

Jan 25 '07 #1
3 2076
Hi,

I recommend using project references over assembly references. Personally,
I like having all of the projects in one solution as long as it doesn't
hamper development (too much clicking and searching can get annoying).

It may seem a bit strange having all of my required utility libraries added
to every solution that uses them as projects, but I do that also. I like to
be able to update the utility libraries when I find bugs or to add new
features while I'm using them.

Another benefit of project references is that it helps to be able to quickly
debug all of the projects from within the same solution by using breakpoints
and being able to step into other projects. Although this is possible
without project references, you'd have to reference the assembly with the
debug symbols, which brings me to my last point...

Project references also allow you to build a debug or release configuration
by just changing the solution configuration. With assembly references you'd
have to do some rewiring first for release builds.

An alternative for team development is to use smaller solutions that contain
only the projects that a particular team requires, with assembly references
to the other projects, and then create one major solution that builds the
final release with project references to all. The build solution would tie
in all of the teams components and could be used for a nightly debug build
and the ultimate release build.

The only problem that I've seen with project references (if you want to call
it a problem) is that source control complains about the binding root being
different from the solution for each of the utility projects.

Another advantage, regarding dependency and build order, can be found on
MSDN:

Project References
Project-to-Project References and File References
http://msdn2.microsoft.com/en-us/lib...ew(VS.80).aspx

--
Dave Sexton
http://davesexton.com/blog
http://www.codeplex.com/DocProject (Sandcastle in VS IDE)

"DonJefe" <MN****@gmail.comwrote in message
news:11**********************@v33g2000cwv.googlegr oups.com...
Does anyone have experience using project->project references in large
solutions? What are the plus/minuses that you have found?

Currently, we are using the binary assembly references for our code,
but this becomes problematic when you want to build from multiple
branches/working directories.

Any thoughts on this would be appreciated.

Thanks

Jan 25 '07 #2
Sounds logical. How about build time? Some of our guys think that will
greatly increase the build time and the rebuild time when you have a
"build broken, fix one project, rebuild" scenario.
On Jan 25, 12:22 pm, "Dave Sexton" <dave@jwa[remove.this]online.com>
wrote:
Hi,

I recommend using project references over assembly references. Personally,
I like having all of the projects in one solution as long as it doesn't
hamper development (too much clicking and searching can get annoying).

It may seem a bit strange having all of my required utility libraries added
to every solution that uses them as projects, but I do that also. I liketo
be able to update the utility libraries when I find bugs or to add new
features while I'm using them.

Another benefit of project references is that it helps to be able to quickly
debug all of the projects from within the same solution by using breakpoints
and being able to step into other projects. Although this is possible
without project references, you'd have to reference the assembly with the
debug symbols, which brings me to my last point...

Project references also allow you to build a debug or release configuration
by just changing the solution configuration. With assembly references you'd
have to do some rewiring first for release builds.

An alternative for team development is to use smaller solutions that contain
only the projects that a particular team requires, with assembly references
to the other projects, and then create one major solution that builds the
final release with project references to all. The build solution would tie
in all of the teams components and could be used for a nightly debug build
and the ultimate release build.

The only problem that I've seen with project references (if you want to call
it a problem) is that source control complains about the binding root being
different from the solution for each of the utility projects.

Another advantage, regarding dependency and build order, can be found on
MSDN:

Project References
Project-to-Project References and File Referenceshttp://msdn2.microsoft.com/en-us/library/ez524kew(VS.80).aspx

--
Dave Sextonhttp://davesexton.com/bloghttp://www.codeplex.com/DocProject(Sandcastle in VS IDE)

"DonJefe" <MNa...@gmail.comwrote in messagenews:11**********************@v33g2000cwv.g ooglegroups.com...
Does anyone have experience using project->project references in large
solutions? What are the plus/minuses that you have found?
Currently, we are using the binary assembly references for our code,
but this becomes problematic when you want to build from multiple
branches/working directories.
Any thoughts on this would be appreciated.
Thanks
Jan 25 '07 #3
Hi,

DonJefe wrote:
Sounds logical. How about build time? Some of our guys think that will
greatly increase the build time and the rebuild time when you have a
"build broken, fix one project, rebuild" scenario.
The build is differential, so once a referenced project is built, it is
not built again, unless you change something in the project itself or in
one of the projects this one references. Additionally, managed build is
much faster than unmanaged build, so it's not really an issue. We have a
fairly big application, and we run hourly builds without problems.

There are huge advantages using project references over assembly
references. The version problems can give huge headaches...

Dave's proposal to use smaller solutions for invidual development works
great too.

HTH,
Laurent
--
Laurent Bugnion [MVP ASP.NET]
Software engineering: http://www.galasoft-LB.ch
PhotoAlbum: http://www.galasoft-LB.ch/pictures
Support children in Calcutta: http://www.calcutta-espoir.ch
Jan 25 '07 #4

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

8
by: Mahesh | last post by:
Hi All, When I copy and paste the project and open newer solution in Visual Studio.NET that newer solution still references files of older solution (It opens the older projects files). I...
7
by: Adam Clauss | last post by:
I have a fairly large project (over 1800 files). When I open up the solution, the entire IDE slows to a crawl. CPU usage sits at about 50% for a couple minutes, and then everything is normal...
4
by: Mark Oliver | last post by:
Hi, I have a large project I wrote in 2003 version 7.1.3088. The project has 128 .cs files with over 1000 References. When I moved a small utility over I had to manually remove then...
0
by: Adam J. Schaff | last post by:
Hello all. I am part of a team about to start work on a large enterprise application. There will be a main application and a bunch of smaller applications that are all related and use the same...
8
by: Axter | last post by:
I normally use a program call Doxygen to document my source code.(http://www.stack.nl/~dimitri/doxygen) This method works great for small and medium size projects, and you can get good...
30
by: David T. Ashley | last post by:
I have a large project on a Linux box that may eventually have several hundred 'C' source files, which need to be compiled and linked into several executables. Not all of the executables will...
2
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 4 Oct 2023 starting at 18:00 UK time (6PM UTC+1) and finishing at about 19:15 (7.15PM) The start time is equivalent to 19:00 (7PM) in Central...
0
tracyyun
by: tracyyun | last post by:
Hello everyone, I have a question and would like some advice on network connectivity. I have one computer connected to my router via WiFi, but I have two other computers that I want to be able to...
4
NeoPa
by: NeoPa | last post by:
Hello everyone. I find myself stuck trying to find the VBA way to get Access to create a PDF of the currently-selected (and open) object (Form or Report). I know it can be done by selecting :...
3
NeoPa
by: NeoPa | last post by:
Introduction For this article I'll be using a very simple database which has Form (clsForm) & Report (clsReport) classes that simply handle making the calling Form invisible until the Form, or all...
1
by: Teri B | last post by:
Hi, I have created a sub-form Roles. In my course form the user selects the roles assigned to the course. 0ne-to-many. One course many roles. Then I created a report based on the Course form and...
0
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 1 Nov 2023 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM) Please note that the UK and Europe revert to winter time on...
0
NeoPa
by: NeoPa | last post by:
Introduction For this article I'll be focusing on the Report (clsReport) class. This simply handles making the calling Form invisible until all of the Reports opened by it have been closed, when it...
4
by: GKJR | last post by:
Does anyone have a recommendation to build a standalone application to replace an Access database? I have my bookkeeping software I developed in Access that I would like to make available to other...
3
SueHopson
by: SueHopson | last post by:
Hi All, I'm trying to create a single code (run off a button that calls the Private Sub) for our parts list report that will allow the user to filter by either/both PartVendor and PartType. On...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.