By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,296 Members | 1,469 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,296 IT Pros & Developers. It's quick & easy.

VStudio 2005 Solution always rebuilding

P: n/a
Does anyone have any idea why my 2005 solution is choosing to rebuild,
everytime i execute any project within its space?

There's nothing overly strange with the project assemblies within, a
few class libraries, a couple of console apps, one custom setup
project and one windows installer project.

i've never seen this behavior before, and i've checked all the
projects' settings that i can think of.

thanks, dave
Dec 12 '07 #1
Share this Question
Share on Google+
8 Replies


P: n/a
What do you mean by "rebuild"? Are you seeing "Rebuild All started" in the
build output?

Have you modified any build dependancies, or do you have any custom build
steps or build events?

--
Browse http://connect.microsoft.com/VisualStudio/feedback/ and vote.
http://www.peterRitchie.com/blog/
Microsoft MVP, Visual Developer - Visual C#
"Dave" wrote:
Does anyone have any idea why my 2005 solution is choosing to rebuild,
everytime i execute any project within its space?

There's nothing overly strange with the project assemblies within, a
few class libraries, a couple of console apps, one custom setup
project and one windows installer project.

i've never seen this behavior before, and i've checked all the
projects' settings that i can think of.

thanks, dave
Dec 12 '07 #2

P: n/a
On Dec 12, 2:10 pm, Peter Ritchie [C# MVP] <PRS...@newsgroups.nospam>
wrote:
What do you mean by "rebuild"? Are you seeing "Rebuild All started" in the
build output?

Have you modified any build dependancies, or do you have any custom build
steps or build events?

--
Browsehttp://connect.microsoft.com/VisualStudio/feedback/and vote.http://www.peterRitchie.com/blog/
Microsoft MVP, Visual Developer - Visual C#

"Dave" wrote:
Does anyone have any idea why my 2005 solution is choosing to rebuild,
everytime i execute any project within its space?
There's nothing overly strange with the project assemblies within, a
few class libraries, a couple of console apps, one custom setup
project and one windows installer project.
i've never seen this behavior before, and i've checked all the
projects' settings that i can think of.
thanks, dave- Hide quoted text -

- Show quoted text -
by rebuilding mean when hitting f5 i see "Build Started... / then
Building..." as it chugs through and rebuilds all my 10 projects. No
changes have been mades since the last execution.

I do have post build steps that copy app.config files from source
library directories into unit test directories, but i have similar
post build actions in other solutions that don't cause this behvior.

thanks, dave
Dec 12 '07 #3

P: n/a
There *was* briefly a bug in Zone Alarm a while back (1 yr perhaps) that
somehow prevented file dates being changed. This bug had exactly the effect
you describe.
Probably not your problem but possibly worth looking outside VS if all else
fails.

Cheers
Doug Forster
Dec 13 '07 #4

P: n/a
Okay, that's not a "rebuild" in Visual Studio terms.

Whenever you run the application within Visual Studio, it starts a build.
If there's nothing it thinks has changed since the last build it will simply
not compile anything. There's many reasons why Visual Studio thinks it
should recompile files upon each F5. Dependencies is one way, setting up a
custom compile tool for to build a content file is another. If I remember
correctly sometimes having setup/deployment projects may also cause more
builds than are necessary. One way of checking this is to unload the
setup/deployment project from the project to see if that affects how much
gets compiled during the debug build. Right click the project in the
Solution Explorer, and select Unload Project...

--
Browse http://connect.microsoft.com/VisualStudio/feedback/ and vote.
http://www.peterRitchie.com/blog/
Microsoft MVP, Visual Developer - Visual C#
"Dave" wrote:
On Dec 12, 2:10 pm, Peter Ritchie [C# MVP] <PRS...@newsgroups.nospam>
wrote:
What do you mean by "rebuild"? Are you seeing "Rebuild All started" in the
build output?

Have you modified any build dependancies, or do you have any custom build
steps or build events?

--
Browsehttp://connect.microsoft.com/VisualStudio/feedback/and vote.http://www.peterRitchie.com/blog/
Microsoft MVP, Visual Developer - Visual C#

"Dave" wrote:
Does anyone have any idea why my 2005 solution is choosing to rebuild,
everytime i execute any project within its space?
There's nothing overly strange with the project assemblies within, a
few class libraries, a couple of console apps, one custom setup
project and one windows installer project.
i've never seen this behavior before, and i've checked all the
projects' settings that i can think of.
thanks, dave- Hide quoted text -
- Show quoted text -

by rebuilding mean when hitting f5 i see "Build Started... / then
Building..." as it chugs through and rebuilds all my 10 projects. No
changes have been mades since the last execution.

I do have post build steps that copy app.config files from source
library directories into unit test directories, but i have similar
post build actions in other solutions that don't cause this behvior.

thanks, dave
Dec 13 '07 #5

P: n/a
On Dec 12, 3:59 pm, Peter Ritchie [C# MVP] <PRS...@newsgroups.nospam>
wrote:
Okay, that's not a "rebuild" in Visual Studio terms.

Whenever you run the application within Visual Studio, it starts a build.
If there's nothing it thinks has changed since the last build it will simply
not compile anything. There's many reasons why Visual Studio thinks it
should recompile files upon each F5. Dependencies is one way, setting up a
custom compile tool for to build a content file is another. If I remember
correctly sometimes having setup/deployment projects may also cause more
builds than are necessary. One way of checking this is to unload the
setup/deployment project from the project to see if that affects how much
gets compiled during the debug build. Right click the project in the
Solution Explorer, and select Unload Project...

--
Browsehttp://connect.microsoft.com/VisualStudio/feedback/and vote.http://www.peterRitchie.com/blog/
Microsoft MVP, Visual Developer - Visual C#
Yes i agree and i tried exactly as you suggested before posting this
question. I thought the setup project(s) could be hampering the build
process, but unloading them still caused dependencies / the solution
to think it needs rebuilding.

You're also right that f5 results in rebuilds everytime, and VStudio
has always run this way. I've just got something funky going on I
think.
Dec 13 '07 #6

P: n/a

"Dave" <dj*********@gmail.comwrote in message
news:c7**********************************@d4g2000p rg.googlegroups.com...
On Dec 12, 3:59 pm, Peter Ritchie [C# MVP] <PRS...@newsgroups.nospam>
wrote:
>Okay, that's not a "rebuild" in Visual Studio terms.

Whenever you run the application within Visual Studio, it starts a build.
If there's nothing it thinks has changed since the last build it will
simply
not compile anything. There's many reasons why Visual Studio thinks it
should recompile files upon each F5. Dependencies is one way, setting up
a
custom compile tool for to build a content file is another. If I
remember
correctly sometimes having setup/deployment projects may also cause more
builds than are necessary. One way of checking this is to unload the
setup/deployment project from the project to see if that affects how much
gets compiled during the debug build. Right click the project in the
Solution Explorer, and select Unload Project...

--
Browsehttp://connect.microsoft.com/VisualStudio/feedback/and
vote.http://www.peterRitchie.com/blog/
Microsoft MVP, Visual Developer - Visual C#

Yes i agree and i tried exactly as you suggested before posting this
question. I thought the setup project(s) could be hampering the build
process, but unloading them still caused dependencies / the solution
to think it needs rebuilding.

You're also right that f5 results in rebuilds everytime, and VStudio
has always run this way. I've just got something funky going on I
think.
I always had this problem with C++ projects that were started with wizards
and had Help selected. The Help part of the project would build every run
regardless of whether or not any changes had been made. I started excluding
Help files from the project until I was ready to create the Help content.
YMMV
Dec 13 '07 #7

P: n/a
Actually, that's a good point. I've found that having a C++ project in a
solution causes extraneous and invalid builds... I haven't tracked down
exactly why/how yet.
--
Browse http://connect.microsoft.com/VisualStudio/feedback/ and vote.
http://www.peterRitchie.com/blog/
Microsoft MVP, Visual Developer - Visual C#
"BobF" wrote:
>
"Dave" <dj*********@gmail.comwrote in message
news:c7**********************************@d4g2000p rg.googlegroups.com...
On Dec 12, 3:59 pm, Peter Ritchie [C# MVP] <PRS...@newsgroups.nospam>
wrote:
Okay, that's not a "rebuild" in Visual Studio terms.

Whenever you run the application within Visual Studio, it starts a build.
If there's nothing it thinks has changed since the last build it will
simply
not compile anything. There's many reasons why Visual Studio thinks it
should recompile files upon each F5. Dependencies is one way, setting up
a
custom compile tool for to build a content file is another. If I
remember
correctly sometimes having setup/deployment projects may also cause more
builds than are necessary. One way of checking this is to unload the
setup/deployment project from the project to see if that affects how much
gets compiled during the debug build. Right click the project in the
Solution Explorer, and select Unload Project...

--
Browsehttp://connect.microsoft.com/VisualStudio/feedback/and
vote.http://www.peterRitchie.com/blog/
Microsoft MVP, Visual Developer - Visual C#
Yes i agree and i tried exactly as you suggested before posting this
question. I thought the setup project(s) could be hampering the build
process, but unloading them still caused dependencies / the solution
to think it needs rebuilding.

You're also right that f5 results in rebuilds everytime, and VStudio
has always run this way. I've just got something funky going on I
think.

I always had this problem with C++ projects that were started with wizards
and had Help selected. The Help part of the project would build every run
regardless of whether or not any changes had been made. I started excluding
Help files from the project until I was ready to create the Help content.
YMMV
Dec 13 '07 #8

P: n/a
On Dec 12, 5:10 pm, Peter Ritchie [C# MVP] <PRS...@newsgroups.nospam>
wrote:
Actually, that's a good point. I've found that having a C++ project in a
solution causes extraneous and invalid builds... I haven't tracked down
exactly why/how yet.
--
Browsehttp://connect.microsoft.com/VisualStudio/feedback/and vote.http://www.peterRitchie.com/blog/
Microsoft MVP, Visual Developer - Visual C#

"BobF" wrote:
"Dave" <djohanns...@gmail.comwrote in message
news:c7**********************************@d4g2000p rg.googlegroups.com...
On Dec 12, 3:59 pm, Peter Ritchie [C# MVP] <PRS...@newsgroups.nospam>
wrote:
>Okay, that's not a "rebuild" in Visual Studio terms.
>Whenever you run the application within Visual Studio, it starts a build.
>If there's nothing it thinks has changed since the last build it will
>simply
>not compile anything. There's many reasons why Visual Studio thinks it
>should recompile files upon each F5. Dependencies is one way, setting up
>a
>custom compile tool for to build a content file is another. If I
>remember
>correctly sometimes having setup/deployment projects may also cause more
>builds than are necessary. One way of checking this is to unload the
>setup/deployment project from the project to see if that affects how much
>gets compiled during the debug build. Right click the project in the
>Solution Explorer, and select Unload Project...
>--
>Browsehttp://connect.microsoft.com/VisualStudio/feedback/and
>vote.http://www.peterRitchie.com/blog/
>Microsoft MVP, Visual Developer - Visual C#
Yes i agree and i tried exactly as you suggested before posting this
question. I thought the setup project(s) could be hampering the build
process, but unloading them still caused dependencies / the solution
to think it needs rebuilding.
You're also right that f5 results in rebuilds everytime, and VStudio
has always run this way. I've just got something funky going on I
think.
I always had this problem with C++ projects that were started with wizards
and had Help selected. The Help part of the project would build every run
regardless of whether or not any changes had been made. I started excluding
Help files from the project until I was ready to create the Help content.
YMMV- Hide quoted text -

- Show quoted text -
My last job had loads of managed C++ code mixed in with .NET projects
and yes I had issues of C++ projects building there also. We often
just excluded the C++ from the solution until needed as suggested
herein.

I'm only working with C# now though. Regardless, I may just unload
setup projects for now, so builds will be quick(er) at least.
Dec 13 '07 #9

This discussion thread is closed

Replies have been disabled for this discussion.