OutputPath vs OutDir

[dotnet]

OutputPath vs OutDir

[AndyGerlicher]

Team triage: We also agree that this is unfortunate, but we need to be conservative on this because of legacy issues. This is not something we plan to address at this time.

[JunielKatarn]

OutDir and OutputPath are distinguished for legacy reasons, and OutDir should be used if at all possible.

@rainersigwald Sorry, I didn't really get it. Which one should I use (new project, no legacy dependencies).

[sliekens]

Thanks for taking time to look at this. I really appreciate it.

The way that seems to work best is to keep the OutputPath that is generated by Visual Studio, then set the OutDir as a command argument.

[rainersigwald]

To expand on what @AndyGerlicher said, we can't do what you're asking because we too have lost the reasoning behind this decision. The current team thinks it looks pretty broken.

From comments in the targets

OutDir and OutputPath are distinguished for legacy reasons, and OutDir should be used if at all possible.

It seems like we got stuck in the middle of a transition. However, as you've discovered, there's a ton of MSBuild code out there that exploits the differences between the two variables. That keeps us from completing the transition (or for that matter backing it out), because it would cause a lot of churn in customer projects.

[michael-freidgeim-webjet]

I found that for Asp.Net Core only OutputPath parameter is working, and in mixed .net 4.61/Core solutions OutDir command argument should be avoided. See my post OutDir vs OutputPath for Visual studio 2015 and Asp.Net Core

[arivoir]

<AppendTargetFrameworkToOutputPath>false</AppendTargetFrameworkToOutputPath> Worked for me