Unnecessary builds in VS2005 when build configuration is switched
- From: "Vladimir Ivanov" <vivanov@xxxxxxxxxxxxxxxxxx>
- Date: Wed, 30 Aug 2006 15:12:43 +0300
Hello All!
I found strange bug (or feature?) in VS 2005
It can be reproduced using following scenario:
1. Create blank solution
2. Add new two C# projects of type Class Library named A and B
3. Add project B reference to project A (make A dependent on B)
4. Execute build using default (Debug) build configuration
5. Switch to Release configuration then immediately switch back to Debug
6. Execute build -- Attention: project A will be unnecessary recompiled!
I found following fact: each time solution configuration is switched Visual
Studio creates empty file A\obj\$(Configuration)\build.force (only for
poject A).
When this file exists build command executed from visual studio recompiles
project A then deletes build.force file.
build.force file existence is taken into account only when solution is
building from Visual Studio, but completely ignored when solution is
building from command line using msbuild.exe.
It is very unpleasant behavior if solution contains many dependent projects,
because frequent configuration switches will force to unnecessary and
long-time build.
Is there any workaround or clean resolution of trouble described about?
--
Regards,
Vladimir Ivanov
.
- Prev by Date: RE: Bug with ListBoxControl
- Next by Date: Re: Bug with ListBoxControl
- Previous by thread: RE: Table Adapter
- Next by thread: Re: Can't develop unmanaged VB with VS.NET 2003?
- Index(es):
Relevant Pages
|