![]() For more information, see Standard and custom Toolset configurations. You can modify the value of MSBuildToolsPath by defining a custom Toolset. ![]() In the following example, MSBuild finds the file by using the MSBuildToolsPath reserved property. ![]() For more information, see Override ToolsVersion settings. This behavior can be overridden by using the -ToolsVersion flag. MSBuild defaults to this Toolset within Visual Studio and on the command line, regardless of the Toolset version specified in the project file. Starting in Visual Studio 2013, the MSBuild Toolset version is the same as the Visual Studio version number. Only that Toolset property (or $(MSBuildBinPath)), is required. One Toolset property is $(MSBuildToolsPath), which specifies the path of the. When a ToolsVersion value is defined in a project file, MSBuild uses that value to determine the values of the Toolset properties that are available to the project. For more information, see Framework targeting overview. When you create a project in Visual Studio, or upgrade an existing project, an attribute named ToolsVersion is automatically included in the project file and its value corresponds to the version of MSBuild that is included in the Visual Studio edition. For more information, see Additions to the csproj format for. Some project types use the sdk attribute instead of ToolsVersion.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |