msbuild

问题 I use MsBuild to Registry a VS Addin. I need implement target Uninstall in MSBuild. How can I delete my addin path in SOFTWARE\Microsoft\VisualStudio\9.0\AutomationOptions\LookInFolders registry using MsBuild ? For install, I use <Target Name="RegistryExtensions"> <Message Text="Registry AddIn..."></Message> <Registry.Set RegistryHive="LocalMachine" Key="SOFTWARE\Microsoft\VisualStudio\9.0\AutomationOptions\LookInFolders" Value="$(ProgramFiles)\LifeCycle\AddIns" DataType="String" /> <Message

问题 I have a project developed in 4.0 framework and it is working fine when running with visual studio. But when i execute the same project with MSBuild in command prompt , the project not getting build which shows error of "Al.exe is not found" "C:\\Windows\\Microsoft.NET\\Framework\\v4.0.30319\\Msbuild.exe" The above issue occurs only if the project contains resource files and build with msbuild through command prompt. The msbuild command runs through process start methods using the below code,

问题 Problem: DataFolder.config file is not reverting back to previous state (the patch element's value). Also, none of the custom config file transforms are being pushed out to the destination folder. What's interesting is the ConnectionStrings.config file is being converted back to the original state after the transformation, but not the DataFolder.config . <Target Name="BeforeBuild"> <!-- Web.config, ConnectionStrings.config, DataFolder.config Duplicates original config files into a temp file -

问题 I've built a custom msbuild task based on the old CodePlex project: http://sqlsrvintegrationsrv.codeplex.com/SourceControl/latest#main/SSISMSBuild/Project/Microsoft.SqlServer.IntegrationServices.Build.csproj After finally getting this to build in VS 2015 (using the SQL Server 2016 SMSS assemblies) I can use the compiled project DLL to build SSIS projects. However, I can only get the SSIS project to build (e.g. using a project file such as at https://speaksql.wordpress.com/2013/06/07/a-journey

问题 I am trying to compile the TensorFlow CMake build as an external project on Windows. This requires the 64-bit toolchain to not run out of memory during compilation. However, even though the CMAKE_GENERATOR for the top-level project is Visual Studio 14 2015 Win64 , and this is passed to the external project via the CMAKE_GENERATOR variable, the 32 bit toolchain is used to compile the external project. What I observe: When the build is started, a 64 bit MSBuild process spawns to drive the main

问题 Trying to build my project on the build server gives me the following error: Microsoft (R) Build Engine Version 4.0.30319.1 error MSB4019: The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\TeamData\Microsoft.Data.Schema.SqlTasks.targets" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk. error MSB4019: The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\WebApplications

问题 I created a new ASP.Net core project and set it up in source control which publishes to Azure when I do a check-in. I was able to get everything setup correctly and it was working fine. However, I then added a class library project to the solution and now instead of publishing my website project the MSBuild task is attempting to publish my class library which of course fails. The line in the deployment command is: "%MSBUILD_PATH%" "%DEPLOYMENT_SOURCE%\MySolution.sln" /nologo /verbosity:m /p

问题 I have the following lines in my MSBuild project file: <PropertyGroup> <TestResultsFileName Condition=" '$(TestResultsFileName)' == '' "> TestResults.trx </TestResultsFileName> <TestResultsFilePath>$(OutDir)\$(TestResultsFileName)</TestResultsFilePath> </PropertyGroup> I need to create another file, having the same name as TestResultsFilePath only with the .xml extension. So I want to have a property to hold the file path of the other file. At first, I thought that something like this would

问题 I am building a solution file with code similar to the following; <Target Name="Build"> <MSBuild Projects="$(MySolution)" Targets="Build" BuildInParallel="false" Properties="Configuration=$(Configuration);Platform=$(Platform);"> <Output ItemName="MyOutputs" TaskParameter="TargetOutputs"/> </MSBuild> <Message Importance="High" Text="MyOutputs=@(MyOutputs)" /> </Target> And the output from that message that is supposed to show a list of assemblies that were built is missing some projects -

问题 I'm building a multi-architecture installer for a C++ program with NSIS. I'm using Visual Studio 2010. All is well except I don't know how to make the installer depend on the build for all architectures. I have created a project to run makensis as a build step, and configured it to depend on all other projects in the solution. I'm currently building for Win32 and X86_64 architectures. The NSIS project is only built as a part of X86_64 configuration. But it packs files built in both X86_64 and