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.)
Related
I am attempting to upload my UWP to the windows store. To do so, I am trying to create an App Package. I am following the steps described on the Microsoft Docs webpage (https://learn.microsoft.com/en-us/windows/uwp/packaging/packaging-uwp-apps), but failing when I try to create the app package. The error I'm getting is:
1>------ Build started: Project: IrishRailTimetables, Configuration: Release x86 ------
1> IrishRailTimetables -> C:\Users\c-raf\OneDrive\Documents\College Work\Year_3\Mobile App\IrishRailTimetables\IrishRailTimetables\bin\x86\Release\IrishRailTimetables.exe
1>LOGGERBASEDEXECTASK : ILC error ILC1104: The directory is not empty.
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
========== Deploy: 0 succeeded, 0 failed, 0 skipped ==========
I have no idea what I'm doing wrong. Any help would be greatly appreciated.
Some times visual studio process existing or previous debugging files ,so next time when you debug existing files is not updated with new changes or unknown to new changes.
**Error - Old debugging Files not updated with changes.
so you need to follow these steps-
1) Goto Build > Clean Solution and Close vs.
2) Empty "bin" , "obj" folder of project.
3) You Should also view in taskmanager for any running process of .vs and close it.
4) Then Reopen Your Project and Build it.
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 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?
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).
I've got the weirdest thing I've seen in a long while with VS2010.
I have the same solution, checked out from svn, into two different folders.
One builds one doesn't... but MSBuild doesn't actual fail to build. All the assemblies build and it will run, but VS2010 keeps saying one project fails. If anyones seen this before or can see what I'm missing in my logs it would help heaps.
Looking closer at the second log, I read three "Build succeeded." messages but a final "========== Build: 2 succeeded or up-to-date, 1 failed, 0 skipped ==========". Go figure. There's no post build events. I really don't get this one.
------ Build started: Project: Data.Connection, Configuration: Debug Any CPU ------
Build started 23/09/2010 9:55:30 a.m..
Build succeeded.
Time Elapsed 00:00:00.02
------ Build started: Project: Common, Configuration: Debug Any CPU ------
Compile complete -- 0 errors, 0 warnings
Build succeeded.
Time Elapsed 00:00:01.12
------ Build started: Project: ClientA, Configuration: Debug Any CPU ------
Build started 23/09/2010 9:55:31 a.m..
Build succeeded.
Time Elapsed 00:00:02.14
========== Build: 3 succeeded or up-to-date, 0 failed, 0 skipped ==========
and
------ Build started: Project: Connection, Configuration: Debug Any CPU ------
Build started 23/09/2010 9:53:16 a.m..
Build succeeded.
Time Elapsed 00:00:00.03
------ Build started: Project: Common, Configuration: Debug Any CPU ------
Compile complete -- 0 errors, 0 warnings
Build started 23/09/2010 9:53:16 a.m..
Build succeeded.
Time Elapsed 00:00:00.87
------ Build started: Project: ClientA, Configuration: Debug Any CPU ------
Build started 23/09/2010 9:53:17 a.m..
Build succeeded.
Time Elapsed 00:00:01.95
========== Build: 2 succeeded or up-to-date, 1 failed, 0 skipped ==========
As a note for anyone else who comes across this, the actual problem was related to NTFS's maximum path length.
To explain further NTFS has a maximum length to a full path to a file (http://msdn.microsoft.com/en-us/library/aa365247.aspx). Our path structure was something along the lines of ( g:[...]\projects\Client\Client.Project\Client.Project.Library[...]. In short we blew out the maximum path length.
Renaming some of the directory names resolved the issue.
Just a shame that VS2010 couldn't give a more reasonable error message / explanation.
Not sure exactly. My guess would be that you have absolute references in something (maybe one of your project files, as they are MSBuild files as well).
You know you can, via visual studio, right-click on a project in your solution, select the "Unload Project", and then edit the csproj file to meet your needs, right?
You may want to try that, and see if there's an absolute reference in one of the projects that is breaking.
The logs are the same except for the name and the duration.
It could be a path problem like Richard B said, try searching the "X:\Projects\TaskRunner" in your .csproj/.vbproj files.
This might also be a rights problem, are the rights for the two directories the same? Are there svn problems (locks?)?
Either way, Making a rebuild or a clean and then a build and increasing the verbosity of the logger would help.
I had this in a weird context when I tried to build the project on another machine. The actual error was a missing ";" !! There were definitely no errors flagged at build. I found the error by running Code Analysis - I checked the box in project settings for enable code analysis on build.