visual studio 2005: skipping builds for unknown reason?

Question

I have a visual studio solution with a number of projects. Configuration manager is carefully configured to build all projects except one ( the one skipped is a test project ). After building solution in command-line i got following:

"building XXX Debug|x64"

------ Skipped Build: Project: AAA ------

------ Skipped Build: Project: BBB, Configuration: Debug Win32 ------

Project not selected to build for this solution configuration

------ Build started: Project: CCC, Configuration: YYY Debug ia64 ------

< here goes build >

As you can see, project BBB is skipped becouse it is not selected in configuration manager, project CCC and rest build ok and project AAA is skipped with NO REASON GIVEN. Anyone knows why visual studio may skip project build without any reason? All configuration names ( XXX, YYY Debug, Debug ) and platforms ( x64 / Win32 / ia64 ) are correctly configured in configuration manager.

Possible duplicate of [How to determine why visual studio might be skipping projects when building a solution](http://stackoverflow.com/questions/1319772/how-to-determine-why-visual-studio-might-be-skipping-projects-when-building-a-so) — FrequentGuest, May 11 '17 at 07:35

score 3 · Accepted Answer · answered Mar 01 '09 at 19:29

3

Is project AAA selected for configuration Debug|x64 ?

Also I had the same situation when freshly downloaded solution (without .soa file) had the default configuration to Itanium, so all system without its support were skipping all solution projects to build. Properly build was starting only after selecting win32 manually.

answered Mar 01 '09 at 19:29

abatishchev

98,240
88
296
433

yes, AAA is selected for "Debug|x64" to build "AAA Debug|ia64". It builds inside IDE perfectly. – grigoryvp Mar 01 '09 at 19:38
Ok. How do you compile your solution with command line? using devenv.exe /.. or msbuild.exe /.. ? – abatishchev Mar 01 '09 at 22:26
devenv.exe, it's bundled with vs2005 – grigoryvp Mar 02 '09 at 06:27
1

devenv IS VS2005 :) use msbuild! this is APPROPRIATE batch builder by Microsoft. it's free and most supported. using devenv is not good idea, not best practice, not what it professional should do – abatishchev Mar 02 '09 at 07:54

score 0 · Answer 2 · answered Mar 01 '09 at 22:30

0

Run the project from the command line using MSBUILD.exe and set the parameter for logging (verbosity) = detailed or diagnostic. You should then get me more output telling you why msbuild considered skipping the one in question. e.g.

msbuild XXXX.csproj /verbosity:detailed

Nb. Diagnostic output is very very verbose

answered Mar 01 '09 at 22:30

Preet Sangha

64,563
18
145
216

unfortunately i'm limited to devenv.exe due to company policy. It does not have /verbosity command-line key :( – grigoryvp Mar 02 '09 at 06:35
1

set the environment var: verbosity=diag – Preet Sangha Mar 16 '09 at 10:04

score 0 · Answer 3 · answered Mar 01 '09 at 22:37

0

Normal builds within Visual Studio are incremental: Visual Studio will skip building a project if it thinks none of the source files have been changed - note that it only checks code files, not resources or other "stuff".

Try doing a clean build by selecting Build|Clean Solution then Build|Rebuild Solution and see if you get the same results.

You may need to manually clean up the build artifacts for each project (by default, the \Bin\ and \Obj\ subdirectories within each project directory).

answered Mar 01 '09 at 22:37

Bevan

43,618
10
81
133

i'm using /clean and /build the build process is straightforward: temp folder created, latest version of solution and projects fetched from sourcesafe, build performed, temp folder deleted. No intermediate artifacts, cache etc can survive. – grigoryvp Mar 02 '09 at 06:36

visual studio 2005: skipping builds for unknown reason?

3 Answers3