How to determine why a visual studio can skip projects when building a solution

Question

I am debugging someone else's work, and the solution is quite large. When I try to collect the whole thing, several projects as part of the solution are not created, but simply skipped. Viewing the output window during the build process says:

1> ------ Missed Rebuild All: Project: pr1lib ------

How can I determine why these assemblies were skipped? I can not find additional output.

This is with VS2008, and the solution consists of C # and c ++ code.

Answer 1

Right-click on the solution, select Properties, and then Configuration Properties. Here you can choose which projects to build.

[ edit ]:
See Kdt Comment: ... when I looked in the configuration properties ... the project build target was configured for Mixed Platforms, while the solution was configured for Any Processor assembly.

* When this problem arose with me, the main project was only “Any processor”, and it installed the child DLL on “any processor”, however I deleted this profile and left only “x86”. Choosing x86 for dll only will make it get started
[/ Edit]

Answer 2

I had the same problem - "unloading project" and "reloading project" solved the problem!

Answer 3

Assembly, restoration, and cleaning operations were skipped. Unloading and rebooting did not help, and rebooting Visual Studio did not restart.

As soon as I removed the project from the solution and added it back, it is no longer skipped. To remove it, in Solution Explorer, right-click the project> Delete> OK. To add it back, in Solution Explorer, right-click the solution> Add> Existing Project and select your project

Answer 4

If confixguration is x64 and the x64 compiler is not installed, it skips the project.

Answer 5

Visual Studio 2008, this may be because a 64-bit compiler would not be installed.

Control Panel → Programs and Features → Microsoft Visual Studio 2008 professional → [double click]

In the Visual Studio dialog

Next → Add / Remove Components → (Sub) Visual C ++ → (Select) x64 Compiler and Tools

Answer 6

Hey, just fixed it. Thought it might help. You most likely did not install the appropriate compilers with the visual studio. This happened to me today - by default, the VS 2008 installer does not install the x64 C ++ compiler.

If you have Service Pack 1 (SP1), uninstall it before changing the VS installation. When this is done, install SP1 again.

Answer 7

The problem exists in VS 2010; proposed solutions: editing the assembly configuration, cleaning, changing / changing the parameters of the target structure, DO NOT work. But unloading and reloading the project occurs.

Answer 8

My solution is the same as mentioned before: Delete → Add existing project

But this solution implies that links between projects disappear

To avoid adding links again: if you use a version control system, such as GIT or TFS or something else, you can achieve the goal with the following steps:

1. Make sure all changes are committed / recorded before the operation.

2. View all projects, excluding them from the solution and adding existing ones to them.

3. Please note that the .sln file has changed

4. Save the new .sln file, but discard changes to all .cspoj files in the version control system

Answer 9

Go to the build menu and select "Configuration Manager". This will show which projects are configured to build in your chosen configuration.

Answer 10

Had the same problem, it turned out that the project setup was for the Itanium processor, replacing it with Intel.

Answer 11

Fulfilled the same problem with VS2005, all configurations were correct. He even missed the Clean Project team.

Finally, unloading / reloading did the magic.

Answer 12

Right-click on “Solution” in your solution explorer, then click “Properties” at the bottom of the menu. In the properties window, click on Configuration Properties → Configuration in the left pane, you will see a list of projects in the right pane, make sure that the “Build” box is checked in the pop-up window.

Answer 13

If your solution contains a NuGet project file (* .nuproj), try downloading it and then rebuild your solution.

This worked for me after none of the above actions worked.

Answer 14

I had a similar thing that happened to me. I am not sure what the problem is, but it will not Clean, Build, Restore, etc. I work in Visual Studio 2017 and wanted to build netstandard2.0 . The problem for me was that somehow the type of the project was wrong, maybe I started with the netcoreapp class netcoreapp , something like this, stuck in the Solution file, I don’t remember. Be that as it may, I made a netstandard copy of the project, created a new netstandard class library netstandard all the backups, and it helped me. Hth someone.

Answer 15

I had a weird one that might be worth documenting among other features here ..

I added the Shared Project to my solution with code that was used in two or three other projects. As you know, shared projects are just code, not a project in the traditional sense. You cannot “build” a common project, it's just code that is built into other projects and then built there.

But somehow, my solution file was updated, as if the overall project was on its own, which needed to be built. I assume that whenever I tried to compile and did not change the code in the general project, he believed that "nothing has changed, skip these assemblies"

I found a generic project in solution.sln file for example:

 Project("{D954291E-2A0B-460D-934E-DC6B0785DB48}") = "Api.Common", "Api.Common\Api.Common.shproj", "{EC580471-D78A-4509-AC46-BD565553AD60}" 

.. what well. What is not good is that this project also appeared in GlobalSection(ProjectConfigurationPlatforms) = postSolution for example:

  {EC580471-D78A-4509-AC46-BD565553AD60}.Debug|Any CPU.ActiveCfg = Debug|Any CPU {EC580471-D78A-4509-AC46-BD565553AD60}.Debug|Any CPU.Build.0 = Debug|Any CPU {EC580471-D78A-4509-AC46-BD565553AD60}.Release|Any CPU.ActiveCfg = Release|Any CPU {EC580471-D78A-4509-AC46-BD565553AD60}.Release|Any CPU.Build.0 = Release|Any CPU 

I deleted these four lines from my .sln file and now everything seems happy again

Answer 16

1. Close visual studio
2. Open sln file with notepad
3. delete everything like this: {B546C55D-9321-4FC0-B25C-46844222BEBE}. Debugging with Fakes | x86.ActiveCfg = Debugging with Fakes | x86 (there will be many)

4. save the file 5. open a visual studio and everything is better

Answer 17

I upgraded to 15.9.11, ... after some builds the same problem: most projects are skipped (which are built a second ago without any problems). Unloading / reloading the solution always helps in my case, but it will happen again soon.

I have no idea why ... except for the big mistake in VS2017

I checked the configuration manager, all the checkboxes are set for assembly.

This may be somehow related to nuget packages, but this is just a guess

The solution has only c ++ / vcxproj, but not csproj. 64 and 32 are both installed

Answer 18

The first thing you need to do is find out why the assembly is missing projects. Therefore, to get a detailed build result, change the verbosity to detailed in the next place in Visual Studio .

Answer 19

make sure you do a clean first. Visual Studio usually will not rebuild a project that is not outdated (as far as this is concerned), and will simply reuse the code of the object that it already has.

Running cleanup should clear all previously compiled code, and VS should not skip the project (provided that the configuration manager has projects selected for assembly ... see previous answer).

Hope this helps.

Answer 20

I find that sometimes, when you have a target platform installed that allows you to speak x86 in your solution and in your projects, the project is actually not always chosen.

To perform a double check, go to the project properties and see if you can select this platform in the Build-> Platform setting, if you cannot, then you will need to go to the configuration manager and create this configuration.

Answer 21

I am having a problem with some Windows CE projects on a new PC. “Unload the project” and “Refresh the project” seem to have fixed the problem, but in fact Visual Studio just switched to another platform and built it.

It turned out that although my WinCE platform was shown to be an active platform, Visual Studio did not "really" consider it. The solution was to reinstall the WinCE SDK with administrator privileges :

• Verify that Visual Studio 2008 is not running.
• Open "Visual Studio 2008 Command Prompt" as an administrator. In Windows 7, simply right-click on the short circuit and select the option “Run as administrator”.
• Enter the following command: msiexec /log SDKInstallLog.txt /package <the path to your .msi file>
• When you are asked if you want to make a custom or a complete set for the installation, and ask the installer to omit the installation of documentation (this step was not necessary in my case, in fact I just asked him to "restore" the existing installation.)
• Install

Answer 22

VS 2008 will skip x64 targets if you do not have an x64 compiler installed. VS 2008 is not the default. Kind of spirit, thing.

Answer 23

I had a very similar problem after creating a project from a decompiler from Telerik, and then trying to recompile it. The project was skipped whenever I tried to rebuild it. I tried many suggestions above, but for me it was the .NET Framework selected in the project properties.

Right-click the project in the solution file, select properties, application tab, change the target structure from 4.0 to 3.5.

Then, rebuild, and I got a bunch of links to the error assembly, which makes sense, since I haven't added links to them yet.

Answer 24

I update one small update to Visual Studio 2017, and then the installer reminds me to restart the computer, but I do not restart. When I build my project or solution in Visual Studio 2017, I encounter the same problem described above. key, so I rebooted the computer, I did it.:>

Answer 25

I had this problem in Visual Studio 2017 15.9.4, and after some searching and postponing time, I found that in my solution the .csproj file of one of the projects was damaged after merging in TFS. (I could build other projects by unloading the problematic project from the solution). As I solved my problem, I compared the .csproj file before and after the merge and fixed it. And by fix, I mean that since my own project type was .netStandard, I deleted unnecessary lines, including the Configuration PropertyGroup, all and others in the new .csproj file, to make it look like the previous version of .netstandard.

Answer 26

I had a similar problem, I had one project, which for some reason could not load in the solution explorer. When I downloaded this project, it worked like a charm.

Answer 27

I just got into this problem:

Updated VS 2017 to the latest version 15.9.11, and several of my projects have been updated to .net core 2.2. I initially downloaded all the projects, tried to build / clean / restore, and everything was skipped. Follow below for a solution:

1. I unloaded each project and reloaded them.
2. Closed all VS instances and opened VS as an administrator (right-click on the shortcut and select the option “Run as administrator”)

It all came back into action, and I was able to successfully build all the projects.

Answer 28

Visual Studio 2017

After adding the configuration in the Configuration Manager

Right click on Project -> Project Only -> Build Only / Rebuild Only / Clean Only

if all other settings are correct.