You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CustomProjectParserResult.OutputPaths doesn't respect the AppendTargetFrameworkToOutputPath property in csproj files
Expected Behavior
The output path for a project with AppendTargetFrameworkToOutputPath set to false should be, for example, "bin/Debug"
Current Behavior
Independent of what AppendTargetFrameworkToOutputPath is set to, the output path will have the target framework appended, for example, "bin/Debug/net48"
Steps to Reproduce (for bugs)
For this project file: <Project Sdk="Microsoft.NET.Sdk"> <PropertyGroup> <TargetFramework>net48</TargetFramework> <Deterministic>False</Deterministic> <AppendTargetFrameworkToOutputPath>false</AppendTargetFrameworkToOutputPath> <OutputType>Exe</OutputType> </PropertyGroup> </Project>
Use projectFile.ParseProjectFile(configuration: "debug") to parse the file
CustomProjectParserResult.OutputPaths.First() will end in "bin/debug/net48" rather than "bin/debug"
Context
Need to be able to know where the dll will end up for use later in our build pipeline.
Your Environment
Module version used: 6.0.0
Operating System and PowerShell version: Windows 10, PowerShell 7.1.3
The text was updated successfully, but these errors were encountered:
CustomProjectParserResult.OutputPaths doesn't respect the AppendTargetFrameworkToOutputPath property in csproj files
Expected Behavior
The output path for a project with AppendTargetFrameworkToOutputPath set to false should be, for example, "bin/Debug"
Current Behavior
Independent of what AppendTargetFrameworkToOutputPath is set to, the output path will have the target framework appended, for example, "bin/Debug/net48"
Steps to Reproduce (for bugs)
For this project file:
<Project Sdk="Microsoft.NET.Sdk"> <PropertyGroup> <TargetFramework>net48</TargetFramework> <Deterministic>False</Deterministic> <AppendTargetFrameworkToOutputPath>false</AppendTargetFrameworkToOutputPath> <OutputType>Exe</OutputType> </PropertyGroup> </Project>
projectFile.ParseProjectFile(configuration: "debug")
to parse the fileCustomProjectParserResult.OutputPaths.First()
will end in "bin/debug/net48" rather than "bin/debug"Context
Need to be able to know where the dll will end up for use later in our build pipeline.
Your Environment
The text was updated successfully, but these errors were encountered: