Geo
Geo

Reputation: 96867

Visual Studio skips build

When I try to build my project I get the following message in the build window :

========== Build: 0 succeeded or up-to-date, 0 failed, 1 skipped ==========

I tried rebuilding , then building again , but it doesn't help . Is there a way to view more detailed messages ? The "skipped" part doesn't give me any info on what's wrong . I am using Visual Studio 2005 Professional Edition .

Upvotes: 14

Views: 11386

Answers (7)

ulidtko
ulidtko

Reputation: 15570

Yet another reason why this could happen (as it happened to me):

When your VS installation is missing x64 compiler toolchain, and you're building for x64.

To solve this, find MSVS in appwiz.cpl ("Programs and Features"), click "Uninstall/Change", then go to the x64 toolchain checkbox under C++ and check it.

Upvotes: 3

Christian C. Salvadó
Christian C. Salvadó

Reputation: 827536

Check on your solution properties, then go to "Configuration Properties", and make sure that all the projects that you want to build, have the build flag checked:

Upvotes: 12

bobobobo
bobobobo

Reputation: 67254

This recently happened to me when I tried to compile a project that was apparently orphaned from it's parent solution.

When I finally did get it to compile, it wouldn't work because some library from another project was missing (that was supposed to be part of the solution to get a successful build).

Upvotes: 1

Wbucks
Wbucks

Reputation: 9

I have found the solution *.sln file to be the problem. Reverted back to a previous version and it fixed the problem. Often the project references a project that is the actual offender, so try and build up the reference list to see where the problem is.

Upvotes: 0

Coentje
Coentje

Reputation: 520

Check with the configuration manager like CMS said and make sure that you have the right platform set. A lot of the time when you use something like the MS Application Blocks the default platform is set to Itanium.

Upvotes: 13

Jasper Bekkers
Jasper Bekkers

Reputation: 6809

I generally run into that when the PC is low on resources (RAM), after closing things the build runs fine.

Upvotes: -3

kenny
kenny

Reputation: 22354

Hmmm... I remember cursing at that one once? Just guessing from my awful memory, but perhaps the output directory path doesn't exist?

Upvotes: 0

Related Questions