项目文件包含 ToolsVersion="14.0" 设置,而此版本的 MSBuild 不支持该工具版本

最新推荐文章于 2024-06-08 23:28:25 发布
原创 最新推荐文章于 2024-06-08 23:28:25 发布 · 1.3w 阅读 · 2 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

本文提供了解决项目中平台工作集从V140改为V100的具体步骤，通过调整配置属性，轻松解决编译错误。
部署运行你感兴趣的模型镜像 
解决方法：
右键点击你的项目，选择属性，再点击配置属性中的常规，常规中有个平台工作集，把V140改成V100，点击应用即可。

您可能感兴趣的与本文相关的镜像

Kotaemon

Kotaemon

AI应用

Kotaemon 是由Cinnamon 开发的开源项目，是一个RAG UI页面,主要面向DocQA的终端用户和构建自己RAG pipeline

vs项目转换版本工具
05-15
转换vs项目版本，方便我们进行项目升降版本的工具，非常好用
ToolsVersion="14.0"，，这个报错。
一路奔跑94的博客
03-15 5537
报这个错误，改个文件就ok 用VS2010打开解决方案时，输出窗口有如下提示信息： 1>Project file contains ToolsVersion="14.0". This toolset may be unknown or missing, in which case you may be able to resolve this by installing...
MSBUILD : error MSB4132: 无法识别工具版本“2.0”。可用的工具版本为 “4.0“
xcf007的专栏
06-08 2712
MSBUILD : error MSB4132: 无法识别工具版本“2.0”。可用的工具版本为 "12.0", "14.0", "4.0"。MSBUILD : error MSB4132: 无法识别工具版本“2.0”。可用的工具版本为 "4.0"。在此解决方案中一次生成一个项目。若要启用并行生成，请添加“/m”开关。在此解决方案中一次生成一个项目。若要启用并行生成，请添加“/m”开关。解决方案2005的，需要升级。
水中机器鱼项目开发问题：项目文件包含 ToolsVersion=“14.0“。此工具集可能未知或缺失 解决方法
Yujian2563的博客
12-23 2303
右键点击项目，选择属性，再点击配置属性中的常规，常规中有个平台工作集，点下拉菜单栏，修改为V100，点击应用。
项目文件包含 ToolsVersion="12.0" 设置,而此版本的 MSBuild 不支持该工具版本
在线笔记
10-08 7562
解决方法： 右键点击你的项目，选择属性，再点击配置属性中的常规，常规中有个平台工作集，把V120改成V100，点击应用即可。 管理员在2009年8月13日编辑了该文章文章。 --> --> window
【网络编程】VS2012 ToolsVersion="14.0" 设置，但此工具集未知或缺失
oh geez
12-15 4221
原因应该是我用vs2012打开了一个2010的项目。 解决办法： 用文本编辑器（例如Notepad++）打开VC项目（后缀名为.vcxproj），找到这一行内容： <Project DefaultTargets="Build" ToolsVersion="14.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">...
如果 MSBuild 构建过程中出现工具集版本不匹配的错误，如何排查和解决？
06-05
项目文件（如 `.csproj` 或 `.vbproj`）中可能包含 `<ToolsVersion>` 元素，用于指定工具集版本。例如： ```xml <ToolsVersion>15.0</ToolsVersion> ``` 如果项目的工具集版本与实际使用的 MSBuild 版本不匹配，...
解决node-gyp编译找不到MSBuild2.0的问题
解决此类问题的根本方法之一就是安装 **Visual C++ 2015 Build Tools**，因为它包含了 MSBuild 14.0、VC++ 编译器 v140 及相关 SDK，完全满足现代 node-gyp 对构建工具的需求。此外，该工具包体积小、安装快，无需...
msbuild' 不是内部或外部命令，也不是可运行的程序 或批处理文件。
最新发布
11-09
- 右键"此电脑" → 属性 → 高级系统设置 → 环境变量 - 在`Path`变量中添加MSBuild路径（根据实际版本修改）： ```bash # .NET Framework 4.x 路径 C:\Windows\Microsoft.NET\Framework\v4.0.30319 C:\...
你的脚本报警msbuild不是内部或外部命令，也不是可运行程序
09-10
但请注意，这个路径下的MSBuild可能版本较旧，不支持新版本的Visual Studio项目。 因此，推荐使用方法二（vswhere）来定位MSBuild，因为它可以自动找到最新版本的Visual Studio的MSBuild。 最后，如果用户没有...
<?xml version="1.0" encoding="utf-8"?> <!-- Licensed to the .NET Foundation under one or more agreements. The .NET Foundation licenses this file to you under the MIT license. See the LICENSE file in the project root for more information. --> <Project ToolsVersion="14.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003"> <!-- Common targets for managed compilers. --> <UsingTask TaskName="Microsoft.CodeAnalysis.BuildTasks.MapSourceRoots" AssemblyFile="$(MSBuildThisFileDirectory)Microsoft.Build.Tasks.CodeAnalysis.dll" /> <Import Project="Microsoft.Managed.Core.CurrentVersions.targets" /> <Target Name="ShimReferencePathsWhenCommonTargetsDoesNotUnderstandReferenceAssemblies" BeforeTargets="CoreCompile" Condition="'@(ReferencePathWithRefAssemblies)' == ''"> <!-- FindReferenceAssembliesForReferences target in Common targets populate this item since dev15.3. The compiler targets may be used (via NuGet package) on earlier MSBuilds. If the ReferencePathWithRefAssemblies item is not populated, just use ReferencePaths (implementation assemblies) as they are. Since XAML inner build runs CoreCompile directly (instead of Compile target), it also doesn't invoke FindReferenceAssembliesForReferences listed in CompileDependsOn. In that case we also populate ReferencePathWithRefAssemblies with implementation assemblies. --> <ItemGroup> <ReferencePathWithRefAssemblies Include="@(ReferencePath)" /> </ItemGroup> </Target> <Target Name="_BeforeVBCSCoreCompile" DependsOnTargets="ShimReferencePathsWhenCommonTargetsDoesNotUnderstandReferenceAssemblies"> <ItemGroup Condition="'$(TargetingClr2Framework)' == 'true'"> <ReferencePathWithRefAssemblies> <EmbedInteropTypes /> </ReferencePathWithRefAssemblies> </ItemGroup> <!-- Prefer32Bit was introduced in .NET 4.5. Set it to false if we are targeting 4.0 --> <PropertyGroup Condition="('$(TargetFrameworkVersion)' == 'v4.0')"> <Prefer32Bit>false</Prefer32Bit> </PropertyGroup> <!-- TODO: Remove this ItemGroup once it has been moved to "_GenerateCompileInputs" target in Microsoft.Common.CurrentVersion.targets. https://github.com/dotnet/roslyn/issues/12223 --> <ItemGroup Condition="('$(AdditionalFileItemNames)' != '')"> <AdditionalFileItems Include="$(AdditionalFileItemNames)" /> <AdditionalFiles Include="@(%(AdditionalFileItems.Identity))" /> </ItemGroup> <PropertyGroup Condition="'$(UseSharedCompilation)' == ''"> <UseSharedCompilation>true</UseSharedCompilation> </PropertyGroup> </Target> <!-- ======================== SkipAnalyzers Support ======================== --> <UsingTask TaskName="Microsoft.CodeAnalysis.BuildTasks.ShowMessageForImplicitlySkipAnalyzers" AssemblyFile="$(MSBuildThisFileDirectory)Microsoft.Build.Tasks.CodeAnalysis.dll" /> <Target Name="_ComputeSkipAnalyzers" BeforeTargets="CoreCompile"> <!-- First, force clear non-user facing properties '_SkipAnalyzers' and '_ImplicitlySkipAnalyzers'. --> <PropertyGroup> <_SkipAnalyzers></_SkipAnalyzers> <_ImplicitlySkipAnalyzers></_ImplicitlySkipAnalyzers> </PropertyGroup> <!-- Then, determine if '_SkipAnalyzers' needs to be 'true' based on user facing property 'RunAnalyzers'. If 'RunAnalyzers' is not set, then fallback to user facing property 'RunAnalyzersDuringBuild'. Latter property allows users to disable analyzers only for non-design time builds. Design time builds are background builds inside Visual Studio, see details here: https://github.com/dotnet/project-system/blob/main/docs/design-time-builds.md. Setting 'RunAnalyzersDuringBuild' to false, without setting 'RunAnalyzers', allows users to continue running analyzers in the background in Visual Studio while typing (i.e. intellisense), while disabling analyzer execution on explicitly invoked non-design time builds. --> <PropertyGroup Condition="'$(RunAnalyzers)' == 'false' or ('$(RunAnalyzers)' == '' and '$(RunAnalyzersDuringBuild)' == 'false')"> <_SkipAnalyzers>true</_SkipAnalyzers> </PropertyGroup> <!-- PERF: For builds which are indirectly triggered inside Visual Studio from commands such as from 'Run Tests' or 'Start Debugging', we implicitly skip analyzers and nullable analysis to speed up the build. We only do so by default when 'TreatWarningsAsErrors' is not 'true'. For the scenario where 'TreatWarningsAsErrors' is 'true', users can explicitly enable this functionality by setting 'OptimizeImplicitlyTriggeredBuild' to 'true'. NOTE: This feature is currently supported only for SDK-style projects, i.e. UsingMicrosoftNETSdk = true. --> <PropertyGroup Condition="'$(_SkipAnalyzers)' == '' and '$(IsImplicitlyTriggeredBuild)' == 'true' and '$(UsingMicrosoftNETSdk)' == 'true' and '$(OptimizeImplicitlyTriggeredBuild)' != 'false' and ('$(TreatWarningsAsErrors)' != 'true' or '$(OptimizeImplicitlyTriggeredBuild)' == 'true')"> <_ImplicitlySkipAnalyzers>true</_ImplicitlySkipAnalyzers> <_SkipAnalyzers>true</_SkipAnalyzers> <Features>run-nullable-analysis=never;$(Features)</Features> </PropertyGroup> <!-- Display a message to inform the users about us implicitly skipping analyzers for speeding up indirect builds. --> <ShowMessageForImplicitlySkipAnalyzers Condition="'$(_ImplicitlySkipAnalyzers)' == 'true'"/> <!-- Semaphore file to indicate the time stamp for last build with skipAnalyzers flag. --> <PropertyGroup> <_LastBuildWithSkipAnalyzers>$(IntermediateOutputPath)$(MSBuildProjectFile).BuildWithSkipAnalyzers</_LastBuildWithSkipAnalyzers> </PropertyGroup> <!-- '_LastBuildWithSkipAnalyzers' semaphore file, if exists, is passed as custom additional file input to builds without skipAnalyzers flag to ensure correct incremental builds. Additionally, we need to pass this file as an 'UpToDateCheckInput' item with 'Kind = ImplicitBuild' for project system's fast-upto-date check to work correctly. See https://github.com/dotnet/project-system/issues/7290 for details. --> <ItemGroup Condition="Exists('$(_LastBuildWithSkipAnalyzers)') and '$(_SkipAnalyzers)' != 'true'"> <CustomAdditionalCompileInputs Include="$(_LastBuildWithSkipAnalyzers)"/> <UpToDateCheckInput Include="$(_LastBuildWithSkipAnalyzers)" Kind="ImplicitBuild"/> </ItemGroup> </Target> <!-- We touch and create a semaphore file after build to indicate the time stamp for last build with skipAnalyzers flag. --> <Target Name="_TouchLastBuildWithSkipAnalyzers" Condition="'$(_SkipAnalyzers)' == 'true'" AfterTargets="CoreCompile"> <Touch AlwaysCreate="true" Files="$(_LastBuildWithSkipAnalyzers)"/> </Target> <!-- ======================== .editorconfig Support ======================== --> <ItemGroup> <_AllDirectoriesAbove Include="@(Compile->GetPathsOfAllDirectoriesAbove())" Condition="'$(DiscoverEditorConfigFiles)' != 'false' or '$(DiscoverGlobalAnalyzerConfigFiles)' != 'false'" /> <!-- Work around a GetPathsOfAllDirectoriesAbove() bug where it can return multiple equivalent paths when the compilation includes linked files with relative paths - https://github.com/microsoft/msbuild/issues/4392 --> <PotentialEditorConfigFiles Include="@(_AllDirectoriesAbove->'%(FullPath)'->Distinct()->Combine('.editorconfig'))" Condition="'$(DiscoverEditorConfigFiles)' != 'false'" /> <EditorConfigFiles Include="@(PotentialEditorConfigFiles->Exists())" Condition="'$(DiscoverEditorConfigFiles)' != 'false'" /> <GlobalAnalyzerConfigFiles Include="@(_AllDirectoriesAbove->'%(FullPath)'->Distinct()->Combine('.globalconfig'))" Condition="'$(DiscoverGlobalAnalyzerConfigFiles)' != 'false'" /> <EditorConfigFiles Include="@(GlobalAnalyzerConfigFiles->Exists())" Condition="'$(DiscoverGlobalAnalyzerConfigFiles)' != 'false'" /> </ItemGroup> <!-- ======================== Property/metadata global .editorconfig Support ======================== Generates a global editor config that contains the evaluation of requested MSBuild properties and item metadata Requested properties/items are requested via item groups like: <CompilerVisibleProperty Include="PropertyNameToEval" /> <CompilerVisibleItemMetadata Include="ItemType" MetadataName="MetadataToRetrieve" /> --> <UsingTask TaskName="Microsoft.CodeAnalysis.BuildTasks.GenerateMSBuildEditorConfig" AssemblyFile="$(MSBuildThisFileDirectory)Microsoft.Build.Tasks.CodeAnalysis.dll" /> <Target Name="GenerateMSBuildEditorConfigFile" BeforeTargets="BeforeCompile;CoreCompile" DependsOnTargets="PrepareForBuild;GenerateMSBuildEditorConfigFileShouldRun;GenerateMSBuildEditorConfigFileCore" /> <Target Name="GenerateMSBuildEditorConfigFileShouldRun"> <PropertyGroup> <GeneratedMSBuildEditorConfigFile Condition="'$(GeneratedMSBuildEditorConfigFile)' == ''">$(IntermediateOutputPath)$(MSBuildProjectName).GeneratedMSBuildEditorConfig.editorconfig</GeneratedMSBuildEditorConfigFile> <GenerateMSBuildEditorConfigFile Condition="'$(GenerateMSBuildEditorConfigFile)' == ''">true</GenerateMSBuildEditorConfigFile> <_GeneratedEditorConfigHasItems Condition="'@(CompilerVisibleItemMetadata->Count())' != '0'">true</_GeneratedEditorConfigHasItems> <_GeneratedEditorConfigShouldRun Condition="'$(GenerateMSBuildEditorConfigFile)' == 'true' and ('$(_GeneratedEditorConfigHasItems)' == 'true' or '@(CompilerVisibleProperty->Count())' != '0')">true</_GeneratedEditorConfigShouldRun> </PropertyGroup> </Target> <Target Name="GenerateMSBuildEditorConfigFileCore" Condition="'$(_GeneratedEditorConfigShouldRun)' == 'true'" Outputs="$(GeneratedMSBuildEditorConfigFile)"> <ItemGroup> <!-- Collect requested properties, and eval their value --> <_GeneratedEditorConfigProperty Include="@(CompilerVisibleProperty)"> <Value>$(%(CompilerVisibleProperty.Identity))</Value> </_GeneratedEditorConfigProperty> <!-- Collect the requested items and remember which metadata is wanted --> <_GeneratedEditorConfigMetadata Include="@(%(CompilerVisibleItemMetadata.Identity))" Condition="'$(_GeneratedEditorConfigHasItems)' == 'true'"> <ItemType>%(Identity)</ItemType> <MetadataName>%(CompilerVisibleItemMetadata.MetadataName)</MetadataName> </_GeneratedEditorConfigMetadata> <!-- Record that we'll write a file, and add it to the analyzerconfig inputs --> <FileWrites Include="$(GeneratedMSBuildEditorConfigFile)" /> <EditorConfigFiles Include="$(GeneratedMSBuildEditorConfigFile)" /> </ItemGroup> <!-- Transform the collected properties and items into an editor config file --> <GenerateMSBuildEditorConfig PropertyItems="@(_GeneratedEditorConfigProperty)" MetadataItems="@(_GeneratedEditorConfigMetadata)" FileName="$(GeneratedMSBuildEditorConfigFile)"> </GenerateMSBuildEditorConfig> </Target> <!-- ======================== DeterministicSourcePaths ======================== Unless specified otherwise enable deterministic source root (PathMap) when building deterministically on CI server, but not for local builds. In order for the debugger to find source files when debugging a locally built binary the PDB must contain original, unmapped local paths. --> <PropertyGroup> <DeterministicSourcePaths Condition="'$(DeterministicSourcePaths)' == '' and '$(Deterministic)' == 'true' and '$(ContinuousIntegrationBuild)' == 'true'">true</DeterministicSourcePaths> </PropertyGroup> <!-- ========== SourceRoot ========== All source files of the project are expected to be located under one of the directories specified by SourceRoot item group. This target collects all SourceRoots from various sources. This target calculates final local path for each SourceRoot and sets SourceRoot.MappedPath metadata accordingly. The final path is a path with deterministic prefix when DeterministicSourcePaths is true, and the original path otherwise. In addition, the target validates and deduplicates the SourceRoot items. InitializeSourceControlInformation is an msbuild target that ensures the SourceRoot items are populated from source control. The target is available only if SourceControlInformationFeatureSupported is true. A consumer of SourceRoot.MappedPath metadata, such as Source Link generator, shall depend on this target. --> <Target Name="InitializeSourceRootMappedPaths" DependsOnTargets="_InitializeSourceRootMappedPathsFromSourceControl" Returns="@(SourceRoot)"> <ItemGroup Condition="'@(_MappedSourceRoot)' != ''"> <_MappedSourceRoot Remove="@(_MappedSourceRoot)" /> </ItemGroup> <Microsoft.CodeAnalysis.BuildTasks.MapSourceRoots SourceRoots="@(SourceRoot)" Deterministic="$(DeterministicSourcePaths)"> <Output TaskParameter="MappedSourceRoots" ItemName="_MappedSourceRoot" /> </Microsoft.CodeAnalysis.BuildTasks.MapSourceRoots> <ItemGroup> <SourceRoot Remove="@(SourceRoot)" /> <SourceRoot Include="@(_MappedSourceRoot)" /> </ItemGroup> </Target> <!-- Declare that target InitializeSourceRootMappedPaths that populates MappedPaths metadata on SourceRoot items is available. --> <PropertyGroup> <SourceRootMappedPathsFeatureSupported>true</SourceRootMappedPathsFeatureSupported> </PropertyGroup> <!-- If InitializeSourceControlInformation target isn't supported, we just continue without invoking that synchronization target. We'll proceed with SourceRoot (and other source control properties) provided by the user (or blank). --> <Target Name="_InitializeSourceRootMappedPathsFromSourceControl" DependsOnTargets="InitializeSourceControlInformation" Condition="'$(SourceControlInformationFeatureSupported)' == 'true'" /> <!-- ======= PathMap ======= If DeterministicSourcePaths is true sets PathMap based on SourceRoot.MappedPaths. This target requires SourceRoot to be initialized in order to calculate the PathMap. If SourceRoot doesn't contain any top-level roots an error is reported. --> <Target Name="_SetPathMapFromSourceRoots" DependsOnTargets="InitializeSourceRootMappedPaths" BeforeTargets="CoreCompile" Condition="'$(DeterministicSourcePaths)' == 'true'"> <ItemGroup> <_TopLevelSourceRoot Include="@(SourceRoot)" Condition="'%(SourceRoot.NestedRoot)' == ''"> <EscapedKey>$([MSBuild]::ValueOrDefault('%(Identity)', '').Replace(',', ',,').Replace('=', '=='))</EscapedKey> <EscapedValue>$([MSBuild]::ValueOrDefault('%(MappedPath)', '').Replace(',', ',,').Replace('=', '=='))</EscapedValue> </_TopLevelSourceRoot> </ItemGroup> <PropertyGroup Condition="'@(_TopLevelSourceRoot)' != ''"> <!-- Prepend the SourceRoot.MappedPath values to PathMap, if it already has a value. For each emitted source path the compiler applies the first mapping that matches the path. PathMap values set previously will thus only be applied if the mapping provided by SourceRoot.MappedPath doesn't match. Since SourceRoot.MappedPath is also used by SourceLink preferring it over manually set PathMap ensures that PathMap is consistent with SourceLink. --> <PathMap>@(_TopLevelSourceRoot->'%(EscapedKey)=%(EscapedValue)', ','),$(PathMap)</PathMap> </PropertyGroup> </Target> <!-- ======= CopyAdditionalFiles ======= If a user requests that any @(AdditionalFiles) items are copied to the output directory we add them to the @(None) group to ensure they will be copied. --> <Target Name="CopyAdditionalFiles" BeforeTargets="AssignTargetPaths"> <ItemGroup> <None Include="@(AdditionalFiles)" Condition="'%(AdditionalFiles.CopyToOutputDirectory)' != ''" /> </ItemGroup> </Target> <!-- ======================== CompilerGeneratedFilesOutputPath ======================== Controls output of generated files. CompilerGeneratedFilesOutputPath controls the location the files will be output to. The compiler will not emit any generated files when the path is empty, and defaults to a /generated directory in $(IntermediateOutputPath) if $(IntermediateOutputPath) has a value. EmitCompilerGeneratedFiles allows the user to control if anything is emitted by clearing the property when not true. When EmitCompilerGeneratedFiles is true, we ensure that CompilerGeneatedFilesOutputPath has a value and issue a warning if not. We will create CompilerGeneratedFilesOutputPath if it does not exist. --> <PropertyGroup> <EmitCompilerGeneratedFiles Condition="'$(EmitCompilerGeneratedFiles)' == ''">false</EmitCompilerGeneratedFiles> <CompilerGeneratedFilesOutputPath Condition="'$(EmitCompilerGeneratedFiles)' != 'true'"></CompilerGeneratedFilesOutputPath> <CompilerGeneratedFilesOutputPath Condition="'$(EmitCompilerGeneratedFiles)' == 'true' and '$(CompilerGeneratedFilesOutputPath)' == '' and '$(IntermediateOutputPath)' != ''">$(IntermediateOutputPath)/generated</CompilerGeneratedFilesOutputPath> </PropertyGroup> <Target Name="CreateCompilerGeneratedFilesOutputPath" BeforeTargets="CoreCompile" Condition="'$(EmitCompilerGeneratedFiles)' == 'true' and !('$(DesignTimeBuild)' == 'true' OR '$(BuildingProject)' != 'true')"> <Warning Condition="'$(CompilerGeneratedFilesOutputPath)' == ''" Text="EmitCompilerGeneratedFiles was true, but no CompilerGeneratedFilesOutputPath was provided. CompilerGeneratedFilesOutputPath must be set in order to emit generated files." /> <MakeDir Condition="'$(CompilerGeneratedFilesOutputPath)' != ''" Directories="$(CompilerGeneratedFilesOutputPath)" /> </Target> <!-- ======================== Component Debugger Support ======================== Add the specified VS capability if a user indicates this project supports component debugging --> <ItemGroup> <ProjectCapability Include="RoslynComponent" Condition="'$(IsRoslynComponent)' == 'true'"/> </ItemGroup> </Project> 要求“SourceRoot”路径以斜杠或反斜杠结尾:“D:\Nuget\.nuget\packages”
06-25
在使用 MSBuild 时，如果遇到 `SourceRoot...例如，某些项目可能依赖特定版本的 MSBuild（如 15.0），可通过命令行参数 `-MSBuildVersion` 指定使用的 MSBuild 版本，以避免版本不一致引发的路径或构建异常 [^1]。 ---
ToolsVersion
weixin_30437847的博客
07-23 230
MSBuild要使用properties metadata等属性必须要在Project node里加上ToolsVersion="3.5"属性，如下 <Project ToolsVersion="3.5" xmlns="http://schemas.microsoft.com/developer/msbuild/2003"> 转载于:https://www.cnblogs...
MSBUildToolsPath is not specified for the ToolsVersion “14.0“ defined at “HKEY_LOCAL_MACHINE\SOFTWAR
weixin_40314351的博客
10-21 1145
MSBUildToolsPath is not specified for the ToolsVersion "14.0" defined at "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\TOolsVersions\14.0", or the value specified evaluates to the empty string
MSBuild version 与 ToolsVersion 的区别
weixin_30952103的博客
10-18 421
MSBuild version 是指MSBuild所在的Framework的版本 ToolsVersion 是指编译当前工程使用的版本，相当于MSBuild的 ToolsVersion 参数。 如果一个MSBuild 脚本中，既含有ToolsVersion为2.0的又含有4.0的工程，可以使用批处理来完成其中的一个特殊需求。 转载于:https://www.cnblogs.com/...
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值