471,108 Members | 1,663 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

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

F5 Causes dependancy check of every project

Tom
I have a large soultion 20+ projects C++ MC++ and C#. When I hit F5 no
matter what. It checks to see if it needs to build every project.
"projectX" is up to date. It takes like 10 seconds. I know other
people must of had this problem. Does anyone have a solution, Aside
for turning off projects in the configuration manager?
Jul 21 '05 #1
4 1122
Hi Tom

How did you add the projects as references to your solution? Of the two
ways: select the dll output from each project and add as a reference OR
select from the Projects tab on the Add Reference dialog, I have found that
the latter is significantly quicker when building a large solution. It also
eliminates some problems that occur with resolving references.

HTH

Charles
"Tom" <ts******@gmail.com> wrote in message
news:c7**************************@posting.google.c om...
I have a large soultion 20+ projects C++ MC++ and C#. When I hit F5 no
matter what. It checks to see if it needs to build every project.
"projectX" is up to date. It takes like 10 seconds. I know other
people must of had this problem. Does anyone have a solution, Aside
for turning off projects in the configuration manager?

Jul 21 '05 #2
Tom
I did it from the projects Tab with a local copy. The reason being
this does cause all the dll locking issues that you get when you
reference the dll directly. Also the compiler should know what dlls it
needs to build when changes are made. Otherwise I would have to figure
out what assemblies I had to build manualy corrrect?

"Charles Law" <bl***@nowhere.com> wrote in message news:<uS**************@TK2MSFTNGP14.phx.gbl>...
Hi Tom

How did you add the projects as references to your solution? Of the two
ways: select the dll output from each project and add as a reference OR
select from the Projects tab on the Add Reference dialog, I have found that
the latter is significantly quicker when building a large solution. It also
eliminates some problems that occur with resolving references.

HTH

Charles
"Tom" <ts******@gmail.com> wrote in message
news:c7**************************@posting.google.c om...
I have a large soultion 20+ projects C++ MC++ and C#. When I hit F5 no
matter what. It checks to see if it needs to build every project.
"projectX" is up to date. It takes like 10 seconds. I know other
people must of had this problem. Does anyone have a solution, Aside
for turning off projects in the configuration manager?

Jul 21 '05 #3
Hi Tom

I assume you mean "... does *not* cause all the dll locking issues ...".
Microsoft have confirmed that there is a problem with referencing the dll
directly, so it is better to do it the way you are doing it.

That said, I haven't noticed any significant delay in building my solutions
(I have nine projects in the current solution). In fact, I noticed a marked
improvement in compile time when I switched to referencing the projects
rather than the dlls. I am using VB.NET, which might make a difference, but
I wouldn't have thought so. Perhaps someone else can suggest a reason.

Charles
"Tom" <ts******@gmail.com> wrote in message
news:c7*************************@posting.google.co m...
I did it from the projects Tab with a local copy. The reason being
this does cause all the dll locking issues that you get when you
reference the dll directly. Also the compiler should know what dlls it
needs to build when changes are made. Otherwise I would have to figure
out what assemblies I had to build manualy corrrect?

"Charles Law" <bl***@nowhere.com> wrote in message
news:<uS**************@TK2MSFTNGP14.phx.gbl>...
Hi Tom

How did you add the projects as references to your solution? Of the two
ways: select the dll output from each project and add as a reference OR
select from the Projects tab on the Add Reference dialog, I have found
that
the latter is significantly quicker when building a large solution. It
also
eliminates some problems that occur with resolving references.

HTH

Charles
"Tom" <ts******@gmail.com> wrote in message
news:c7**************************@posting.google.c om...
>I have a large soultion 20+ projects C++ MC++ and C#. When I hit F5 no
> matter what. It checks to see if it needs to build every project.
> "projectX" is up to date. It takes like 10 seconds. I know other
> people must of had this problem. Does anyone have a solution, Aside
> for turning off projects in the configuration manager?

Jul 21 '05 #4
Tom
So I have like close to 20 projects a mixture of C# and C++. When I
hit F5 (not even F7) even if I just built it touches every project it
take about 15 seconds. This makes it very difficult to debug software.
This means there is a 15 sec turn over even if nothing has changed.

"Charles Law" <bl***@nowhere.com> wrote in message news:<ej**************@TK2MSFTNGP14.phx.gbl>...
Hi Tom

I assume you mean "... does *not* cause all the dll locking issues ...".
Microsoft have confirmed that there is a problem with referencing the dll
directly, so it is better to do it the way you are doing it.

That said, I haven't noticed any significant delay in building my solutions
(I have nine projects in the current solution). In fact, I noticed a marked
improvement in compile time when I switched to referencing the projects
rather than the dlls. I am using VB.NET, which might make a difference, but
I wouldn't have thought so. Perhaps someone else can suggest a reason.

Charles
"Tom" <ts******@gmail.com> wrote in message
news:c7*************************@posting.google.co m...
I did it from the projects Tab with a local copy. The reason being
this does cause all the dll locking issues that you get when you
reference the dll directly. Also the compiler should know what dlls it
needs to build when changes are made. Otherwise I would have to figure
out what assemblies I had to build manualy corrrect?

"Charles Law" <bl***@nowhere.com> wrote in message
news:<uS**************@TK2MSFTNGP14.phx.gbl>...
Hi Tom

How did you add the projects as references to your solution? Of the two
ways: select the dll output from each project and add as a reference OR
select from the Projects tab on the Add Reference dialog, I have found
that
the latter is significantly quicker when building a large solution. It
also
eliminates some problems that occur with resolving references.

HTH

Charles
"Tom" <ts******@gmail.com> wrote in message
news:c7**************************@posting.google.c om...
>I have a large soultion 20+ projects C++ MC++ and C#. When I hit F5 no
> matter what. It checks to see if it needs to build every project.
> "projectX" is up to date. It takes like 10 seconds. I know other
> people must of had this problem. Does anyone have a solution, Aside
> for turning off projects in the configuration manager?

Jul 21 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by Christopher | last post: by
7 posts views Thread by Simon Jefferies | last post: by
reply views Thread by Jerry Spence1 | last post: by
7 posts views Thread by =?Utf-8?B?TWlrZSBMb2dhbg==?= | last post: by
5 posts views Thread by dhcrusoe | last post: by

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.