This is usually (in my experience!) Caused by incorrect configuration settings. In Visual Studio, at the solution level, you can go to the Build menu and select Configuration Manager . Make sure that for all applicable configurations (selected using the Active Solution Configuration drop-down list), the installer project has a checkmark in the Build column.
Now you need to make sure that when you call devenv, you pass the appropriate assembly configuration (i.e. the one that has the Build marked for the installation project) as follows:
C:\PathToVisualStudio\devenv.exe /Rebuild Release C:\PathToProject\ProjectName.sln" /Out "PathToProject\vs_errors.txt"
(In this example, Release is the build configuration I'm aiming for)
This command also logs Visual Studio output into a text file named vs_errors.txt in the same folder as your solution, so you can look at this to determine if there are other reasons why the installation project could not be created.
source share