I have a solution with 30 project inside.
I have rebuild the solution with the 30 projects successfully.
However, when I click on Batch Build... and by selecting all to build, I get 360 Warnings.
Here is a snapshot of my screen.
On the Output panel:
========== Build: 30 succeeded, 60 failed, 30 up-to-date, 0 skipped ==========
Here is the link where I have downloaded the project.
Related
I've looked at more pages than I can count about how to solve the "I didn't change anything, so why is VS rebuilding my project" problem. And they were helpful for resolving a number of issues with "copy always" flags, and custom build steps that always run. But I'm left with one that won't go away. It passes all the up-to-date fast dependency checks, but continues to start the build anyway. I've traced through all the MSBuild output at the diagnostic level, but I think the "normal" (not minimal) level is sufficient to point in the right direction. Here's the output:
1>------ Build started: Project: OnePawDataSerializer, Configuration: Debug x64 ------
1>Build started 12/20/2019 5:04:37 PM.
1>GenerateTargetFrameworkMonikerAttribute:
1>Skipping target "GenerateTargetFrameworkMonikerAttribute" because all output files are up-to-date with respect to the input files.
1>CoreCompile:
1>Skipping target "CoreCompile" because all output files are up-to-date with respect to the input files.
1>_CopyFilesMarkedCopyLocal:
1> Touching "D:\Volpe\NuCS-HiEx\NuCS-Repo\Applications\FAB4DA\OnePawDataSerializer\obj\x64\Debug\OnePawDataSerializer.csproj.CopyComplete".
1>_CopyAppConfigFile:
1>Skipping target "_CopyAppConfigFile" because all output files are up-to-date with respect to the input files.
1>CopyFilesToOutputDirectory:
1> OnePawDataSerializer-> D:\Volpe\NuCS-HiEx\NuCS-Repo\Applications\FAB4DA\bin\Debug64\OnePawDataSerializer.exe
1>
1>Build succeeded.
1> 0 Warning(s)
1> 0 Error(s)
1>
1>Time Elapsed 00:00:00.20
========== Build: 1 succeeded, 0 failed, 15 up-to-date, 0 skipped ==========
At this level of output verbosity it doesn't show all the stuff that looks like this:
1>------ Up-To-Date check: Project: CommonDataModelUtilities, Configuration: Debug x64 ------
1>All outputs are up-to-date.
1>Time Elapsed 19 ms
But they all indicate that everything is up to date. In the "normal"-level output, it shows a couple of internal targets being skipped, but then seems to need to execute one called "_CopyFilesMarkedCopyLocal", which doesn't seem to actually copy anything, but does appear to create a file with the name of the project file appended by ".CopyComplete". This appears to be the only instance of the build actually "doing" something tangible, so I'm inclined to suspect that this has something to do with why I'm not seeing this:
========== Build: 0 succeeded, 0 failed, 16 up-to-date, 0 skipped ==========
when I build. But I can't figure out why it's doing it. Any thoughts?
This appears to be the only instance of the build actually "doing"
something tangible, so I'm inclined to suspect that this has something
to do with why I'm not seeing this: ========== Build: 0 succeeded, 0
failed, 16 up-to-date, 0 skipped ========== when I build. But I can't
figure out why it's doing it. Any thoughts?
MSBuild uses incremental compilation, which only compiles files that have been modified, and skips building for files that have not changed. So when build your project again without any changes, it will like this as you wish:
========== Build: 0 succeeded, 0 failed, 16 up-to-date, 0 skipped ==========
This is the normal behavior generated by MSBuild.
But if you build your project again without changing any project files and build always execute, l am afraid that the issue is caused by some project files' settings(set Copy to Output Directory to Copy Always). (Or you can see the files in the xxx.csproj file and then you will find some files add the node <CopyToOutputDirectory>Always</CopyToOutputDirectory>)
According to the build log info from your picture, the targets _CopyFilesMarkedCopyLocal and CopyFilesToOutputDirectory are responsible for copying project resources which you specify as the picture shows to the output path. And when you set the file to Copy Always, MSBuild will always consider this operation to be up to date, so it will always execute.
Note: Build is the process by which msbuild executes a bunch of target targets which contains the compile target. If the files are already compiled and they are not changed, the target will skip. Besides, if some projects are not changed, MSBuild will skip compiling them and regard them as up - to - date.
To prove it l have do a test:
1) I set the project file called JavaScript1.js to Copy Always as the picture shows above.
2) Then when I build the project multiple times, it always turns that the build executes successfully.
In addition, if you want this behavior, you could set Copy to Output Directory to Do not copy. Or if you want to output these files, you can set to Copy if newer.
Update1
If cannot see this abnormal behavior directly, l think you can set MSBuild project build output verbosity to Diagnostic.This mode will display every detailed info about build process.
And l have observed that the build log only shows two targets which are
running _CopyFilesMarkedCopyLocal and CopyFilesToOutputDirectory.
So please check the target CopyFilesToOutputDirectory, _CopyFilesMarkedCopyLocal, Copy task in the Diagnostic build log by the search box and you can search any detailed info about this.
And in my side, l can see this info in the first line of build output which is explain why my project always rebuild:
Project 'ConsoleApp1' is not up to date. Project item 'C:\Users\Admin\source\repos\ConsoleApp32\ConsoleApp32\JavaScript1.js' has 'Copy to Output Directory' attribute set to 'Copy always'.
Hope it could help you.
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.
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.)
After some changes to my project, Visual Studio started to always re-compiles all sources, causing all dependent project to also re-compile, slowing down development considerably. Why is that?
Happens only when XML documentation file is checked and there's some file with Copy always. If you change either of these, the sources don't get re-compiled.
Happens only when compiling inside Visual Studio - when compiling using MSBuild from commandline, the sources don't get re-compiled.
Visual Studio 2012 Update 4.
This appears to be a bug in Visual Studio, when project has XML documentation file checked some files with Copy always.
Repro:
Create new project - C# class library.
Project Properties => Build => check XML documentation file
Project => Add => New Item => Text file TextFile1.txt
Change TextFile1.txt Copy to Output Directory to Copy always
Right-click project => build
project compiles
Right-click project => build
Expected: Project shouldn't be built, build output should say:
========== Build: 0 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
Actual: Project is build, output is:
------ Build started: Project: ClassLibrary1, Configuration: Debug Any CPU ------
ClassLibrary1 -> bin\Debug\ClassLibrary1.dll
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
Intestigation: Turning on detailed log, you see:
Target "CoreCompile" in file "C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.CSharp.targets" from project "ClassLibrary1.csproj" (target "Compile" depends on it):
Building target "CoreCompile" completely.
Output file "bin\Debug\ClassLibrary1.XML" does not exist.
Looking in procmon, you see that devenv.exe renames "ClassLibrary1.XML" into "vsA381.tmp" just before MSBuild.exe runs. Stack trace for the rename:
KERNEL32!MoveFileW+0x17
csproj!CMoveOutOfTheWayScope::EnterScope+0x85
csproj!CVsProjBuildableProjectCfg::StartBuildProcessWithTarget+0x50b
csproj!CVsProjBuildableProjectCfg::StartBuildProcess+0xc
csproj!CVsProjBuildableProjectCfg::StartBuildEx+0x15
msenv!CSUIBuilder::DoBuild+0x1a3
msenv!CSUIBuilder::Run+0x66
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).