Recently we migrated our project from VS205 to VS2010. Post migration we are observing the problem with automated build. Please, see below the details.
Build machine is set up with CruiseControl and a NAnt script for automated builds with devenv.
Building with VS2010 causes a number of (most) projects to start, but not finish (the only message for each project is “Rebuild All started…”). This is the pattern we have observed:
-------Rebuild All started: Project: Scheduler, Configuration: BuildTWinWithPortalSvc x86 ------
------ Rebuild All started: Project: CSerial, Configuration: BuildTWinWithPortalSvc Win32 ------
------ Rebuild All started: Project: sockeeg, Configuration: BuildTWinWithPortalSvc Win32 ------
TwinPortalSetup.vd project gives the message:
An error occurred while validating. HRESULT=’80004005’
Building (on the same machine) with the command line or from the IDE results in no errors.
This script is almost identical to the one that builds the VS2005 solution, which works fine.
Related
I am trying to use Xoreax Incredibuild(v 8.01) to buid LLVM solution file using “BuildConsole” but I am not seeing any speedup in the build times.
In the LLVM logs I can see a message Maximum number of concurrent builds reached. Waiting for a build to complete
I believe this could be the reason that I am not seeing the benefit of using Incredibuild to build LLVM.
Version of Visual Studio used by Incredibuild to build the solution file is 2015.
Has anyone else encountered such a message and if so what is the reason/solution?
I have also tried using IB_profile.xml file to build LLVM and see if it helps in getting rid of the above message but
I am seeing the same message when using XML file to integrate Incredibuild with LLVM.
This is the Make command that I am using to build LLVM with Incredibuild:
BuildConsole LLVM.sln /build "Release|x64" /prj="INSTALL" /AvoidLocal=On /profile=IB_profile.xml
This is the content of IB_profile.xml file:
<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
<Profile FormatVersion="1">
<Tools>
<Tool Filename="devenv" AllowIntercept="true" AllowRemote="true" AllowPredictedBatch="true" VCCompiler="true" OutputFileMasks="*.exe,*.dll" />
<Tool Filename="cl" AllowRemote="true" AllowPredictedBatch="true" VCCompiler="true" OutputFileMasks="*.exe,*.dll" />
</Tools>
</Profile>
Below is the snippet of LLVM logs:
BuildConsole LLVM.sln /build "Release|x64" /prj="INSTALL" /AvoidLocal=On /profile=IB_profile.xml
-----------------------------------------------------------------
Build Acceleration Console 8.2 (build 1885)
Copyright (C) 2001-2017 Xoreax Software Ltd. All rights reserved.
-----------------------------------------------------------------
-- Generating done
CMake Warning:
Manually-specified variables were not used by the project:
CMAKE_MODULE_LINKER_FLAGS
-- Build files have been written to: C:/TEMP/rohit/win64/LLVM
BuildConsole LLVM.sln /build "Release|x64" /prj="INSTALL" /AvoidLocal=On /profile=IB_profile.xml
-----------------------------------------------------------------
Build Acceleration Console 8.2 (build 1885)
Copyright (C) 2001-2017 Xoreax Software Ltd. All rights reserved.
-----------------------------------------------------------------
Maximum number of concurrent builds reached.
Waiting for a build to complete...
--------------------Build System Warning---------------------------------------
Predicted Execution mode automatically disabled:
Predicted Execution mode cannot be set together with DisableStdOutIdentify flag.
Please note the disabled predicted execution feature has no effect on build integrity.
-------------------------------------------------------------------------------
Active code page: 437
Microsoft Visual Studio 2015 Version 14.0.25420.1.
Copyright (C) Microsoft Corp. All rights reserved.
1>------ Build started: Project: LLVMSupport, Configuration: Release x64 ------
2>------ Build started: Project: LLVMTableGen, Configuration: Release x64 ------
3>------ Build started: Project: obj.llvm-tblgen, Configuration: Release x64 ------
4>------ Build started: Project: LLVMMC, Configuration: Release x64 ------
5>------ Build started: Project: LLVMMCDisassembler, Configuration: Release x64 ------
6>------ Build started: Project: LLVMMCParser, Configuration: Release x64 ------
7>------ Build started: Project: LLVMOption, Configuration: Release x64 ------
8>------ Build started: Project: LLVMDebugInfoDWARF, Configuration: Release x64 ------
9>------ Build started: Project: LLVMSymbolize, Configuration: Release x64 ------
10>------ Build started: Project: LTO_exports, Configuration: Release x64 ------
11>------ Build started: Project: LLVMDebugInfoPDB, Configuration: Release x64 ------
12>------ Build started: Project: LLVMLineEditor, Configuration: Release x64 ------
13>------ Build started: Project: count, Configuration: Release x64 ------
14>------ Build started: Project: gtest, Configuration: Release x64 ------
15>------ Build started: Project: gtest_main, Configuration: Release x64 ------
16>------ Build started: Project: llvm-PerfectShuffle, Configuration: Release x64 ------
My name is Yoni Davidson and I am from IncrediBuild support team.
Building the LLVM Solution using BuildConsoel shouldn't require profile.xml since it is a Visual Studio Solution and IncrediBuild should handle it.
Therefore, it is possible that either you dont have remote machines (Helpers) and/or perhaps you dont have enough parallel tasks so the performance is more or less as you have with Visual Studio since everything runs locally.
The "Maximum number of concurrent builds reached" means that you are trying to start another build with IncrediBuild while the previous one is still running. This is not allowed and therefore, you receive this message. In any case, this is not the reason for the build performance you have.
I will be happy to assist you with this problem so I suggest that you will contact us directly: support#incredibuild.com or simply right click on IncrediBuild tray icon -> contact support.
Looking forward hearing from you.
I have an ASP.NET core 1.0 project I created in Visual Studio 2015 (update 3). If I try to build the project within VS I get the following in my output window and there are no errors in the Error List:
1>------ Build started: Project: QuickStartIdentiyServer4, Configuration: Debug Any CPU ------
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
However, if I build the project using the dotnet CLI command (dotnet build) it builds and runs just fine.
UPDATE:
Apparently, .net core does not work properly when running Visual Studio as Admin. You would think everything should work as Admin, I guess not... go figure.
There are simply too many reasons why this type of thing might happen. The easiest way to diagnose the problem is to change the build output verbosity under options to verbose. This might help put you on the trail:
With regards to this type of thing happening with .Net Core and ASP Core. I have noticed that the project.json dependencies json fragment is a bit buggy especially if you start renaming projects and changing their file system location.
If you see in the diagnostic below you know there is some dangling reference issue:
Done building target "_GetDependencyFragmentFiles" in project "<<?YOUR_CORE_PROJECT?>>.xproj" -- FAILED
May be you are not seeing build errors. Go to Error List window and change 'Show Issues generated' box from 'Build + Intellisense' to 'Build Only' and try to build again.
See if this helps.
I'm using Visual Studio 2010 and BizTalk 2010.
When I add a new Empty BizTalk Server Project and build it, I get the following output:
------ Build started: Project: ThrowAway1, Configuration: Debug Any CPU ------
ThrowAway1 -> c:\...\Projects\ThrowAway1\ThrowAway1\bin\Debug\ThrowAway1.dll
ThrowAway1 -> c:\...\Projects\ThrowAway1\ThrowAway1\bin\Debug\ThrowAway1.dll
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
I already tried deactivating the release build. But I still get two build events - which also affects the post build event.
With a default console application I get only one build event.
My goal is to run my own deployment PowerShell script in the post build event. The script is coming along nicely but it is called two times by this behavior.
This appears to be the expected behavior of a BizTalk Project.
I'm only speculating that it's because many BizTalk artifacts are compiled in a two step process. Orchestrations to C# then C# to the output Assembly for example.
The only thing I can recommend is to either make the script deterministic or maybe a side project that runs the post build for the entire Solution.
You can also investigate the BizTalk Deployment Framework: http://biztalkdeployment.codeplex.com/
As a pragmatic solution:
Checking the .btproj MSBuild file and its imports
<Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" />
<Import Project="$(MSBuildExtensionsPath)\Microsoft\BizTalk\BizTalkC.targets" />
where BizTalkC.targets imports
<Import Project="$(MSBuildExtensionsPath)\Microsoft\BizTalk\BizTalkCommon.targets" />
shows the usage of $(SecondBuild) in BizTalkCommon.targets.
This can be used in the post build event:
if "$(SecondBuild)"=="true" (
rem Run script.
)
For the first build $(SecondBuild) will be empty/undefined.
In our VSTS2010 solution, we have a x86-target project that depends on an AnyCPU-target project. When I build the solution, it skips the AnyCPU project, claiming:
------ Skipped Build: Project: myproj, Configuration: Debug Any CPU ------
Project not selected to build for this solution configuration
Then it tries to build the x86 project. This fails, because the AnyCPU project DLL is unavailable.
Am I doing something wrong? What additional information would be helpful in understanding the problem?
Build + Configuration Manager. Tick the Build checkbox.
I have a visual studio solution with a number of projects.
Configuration manager is carefully configured to build all projects except one ( the one skipped is a test project ). After building solution in command-line i got following:
"building XXX Debug|x64"
------ Skipped Build: Project: AAA ------
------ Skipped Build: Project: BBB, Configuration: Debug Win32 ------
Project not selected to build for this solution configuration
------ Build started: Project: CCC, Configuration: YYY Debug ia64 ------
< here goes build >
As you can see, project BBB is skipped becouse it is not selected in configuration manager, project CCC and rest build ok and project AAA is skipped with NO REASON GIVEN. Anyone knows why visual studio may skip project build without any reason? All configuration names ( XXX, YYY Debug, Debug ) and platforms ( x64 / Win32 / ia64 ) are correctly configured in configuration manager.
Is project AAA selected for configuration Debug|x64 ?
Also I had the same situation when freshly downloaded solution (without .soa file) had the default configuration to Itanium, so all system without its support were skipping all solution projects to build. Properly build was starting only after selecting win32 manually.
Run the project from the command line using MSBUILD.exe and set the parameter for logging (verbosity) = detailed or diagnostic. You should then get me more output telling you why msbuild considered skipping the one in question. e.g.
msbuild XXXX.csproj /verbosity:detailed
Nb. Diagnostic output is very very verbose
Normal builds within Visual Studio are incremental: Visual Studio will skip building a project if it thinks none of the source files have been changed - note that it only checks code files, not resources or other "stuff".
Try doing a clean build by selecting Build|Clean Solution then Build|Rebuild Solution and see if you get the same results.
You may need to manually clean up the build artifacts for each project (by default, the \Bin\ and \Obj\ subdirectories within each project directory).