I am using Visual Studio 2010 Ultimate and suddenly the output window won't show any messages after building solution. For example:
1>------ Build started: Project: libdnet-stripped, Configuration:
Release Win32 ------
2>------ Build started: Project: tran_cli, Configuration: Release
Win32 ------
========== Build: 0 succeeded, 2 failed, 4 up-to-date, 0 skipped ==========
And Error List is empty. How can I fix it?
Related
I'm trying to deploy and debug my project on remote machine. My attempt to deploy and debug my code fails and Visual Studio provides me with following log:
1>------ Deploy started: Project: ProjectName, Configuration: Debug x64 ------
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========
Any ideas how I may get more output with some actual error codes?
Environment:
MSVS 2019 16.11.5
Verbosity level -- diagnostic both for build output and log file
Is there any way to get the embedded make in VS2015 to show why it is rebuilding a particular item?
I have a solution with many sub-projects. When I rebuild I get:
1>------ Build started: Project: ProjX, Configuration: Release Win32 ------
1> ProjX.vcxproj -> [yadda yadda]\Build\Release\ProjX.dll
========== Build: 1 succeeded, 0 failed, 33 up-to-date, 0 skipped ==========
This is repeated each time I build, so something has a screwy time/date stamp, but what? How can I debug this. (Yes, it is not a real problem - but just annoying.)
I am trying to publish my project in Microsoft Visual Studio 2010. I have debugged it and it is working as intended. When I attempt to publish it it builds successfully then fails to publish. I have opened the output window to see what is happening. This is what it says in the output window:
------ Build started: Project: JBIPP, Configuration: Debug Any CPU ------
JBIPP -> J:\Bridges\Code\JBIPPDEV\WebApplication2\bin\WebApplication2.dll
------ Publish started: Project: JBIPP, Configuration: Debug Any CPU ------
Connecting to \\IIS2dev\JBIPP...
Unable to create the Web site '\\IIS2dev\JBIPP'. The path '\\IIS2dev\JBIPP' does not exist or you do not have access. The specified path is invalid.
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
========== Publish: 0 succeeded, 1 failed, 0 skipped ==========
Any suggestions on how to get this thing published would be appreciated.
I create a simple Win32 projects, edit the configuration and add new platform configurations (x64). I then batch rebuild my project and I get this output:
------ Rebuild All started: Project: Skribe, Configuration: Release x64 ------
main.c
Generating code
Finished generating code
Skribe.vcxproj -> D:\Dev\Skribe\Build\VS2010\Solutions\..\..\..\Output\Bin\x64\Release\Skribe.exe
------ Rebuild All started: Project: Skribe, Configuration: Debug x64 ------
main.c
Skribe.vcxproj -> D:\Dev\Skribe\Build\VS2010\Solutions\..\..\..\Output\Bin\x64\Debug\Skribe.exe
Skribe.vcxproj -> D:\Dev\Skribe\Build\VS2010\Solutions\..\..\..\Output\Bin\x64\Debug\Skribe.exe
------ Rebuild All started: Project: Skribe, Configuration: Release Win32 ------
main.c
Generating code
Finished generating code
Skribe.vcxproj -> D:\Dev\Skribe\Build\VS2010\Solutions\..\..\..\Output\Bin\Win32\Release\Skribe.exe
------ Rebuild All started: Project: Skribe, Configuration: Debug Win32 ------
main.c
Skribe.vcxproj -> D:\Dev\Skribe\Build\VS2010\Solutions\..\..\..\Output\Bin\Win32\Debug\Skribe.exe
========== Rebuild All: 4 succeeded, 0 failed, 0 skipped ==========
The debug x64 build outputs the exe creation message twice and I cannot figure out why. This worries because of a related question I asked where a rebuild actually fails but a clean/build succeeds.
Does anyone know why the extra message is shown? I've done nothing else other than create a solution, exe project, add x64 configuration and batch rebuild.
I'm trying to publish an ASP.NET MVC 3 app but I am getting
------ Publish started: Project: MyProject, Configuration: Debug Any CPU ------
Not allowed to begin a design-time build at this time for publish. Please try again later.
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
========== Publish: 0 succeeded, 1 failed, 0 skipped ==========
I've published before successfully ... I even tried restarting Visual Studio and then the whole PC!
Any thoughts?
I'm not sure why this fails, quite honestly, but I restarted VS 2010 like #Keven Coulombe suggested and after that the publish went through. My guess is this might happen after debugging other projects, and having VS open for extended periods (For me this was about one week).