Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
OutputPath vs OutDir #87
I'm pulling my hair out trying to get Visual Studio and MSBuild to agree on where build output should be stored, using any combination of
Edit: turns out that there is a third property that controls the build output:
I realize that this is not a help forum. I briefly considered asking a question about it on StackOverflow, but 72 others have done so before me, leaving empty-handed most of the time.
There is a huge number of scenarios that require relocating the build output, but there is no reliable way to do that. For example: IIS Express stops working when you change the
Someone even got mad enough over
Please explain how
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
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.
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