Would be very helpful if C# expanded macros used in the "Output path" setting for a project (VC++ does)
See the following forum thread for details:
Thanks for taking the time to share this suggestion. This item has been around for a couple of versions of Visual Studio and we haven’t acted on it. Looking at the VS “15” plans, we’re not going to take action on this item, so we’re going to close it. If the suggestion is still relevant, please either take a look to see if there’s another suggestion that’s similar that you can vote on, or open a new suggestion.
- The Visual Studio Team
It's really surprising this not working in VS 2017 since it works as expected (not having to go through text editor to use VS macros) when using VC++. Why on earth aren't VS macros respected in output path in C#?
now we have VS 17 and this essential function is still missing. Quite disappointing :-(.
Peter Pressacco commented
**BE ADVISED** If you use a text editor set the set the <OutputPath> to $(SolutionDir)\bin\Debug it will appear as ..\..\..\bin\Debug in Visual Studio 2013. The good news is, the macro will remain intact and everything will work as expected. If you make any changes to the `Output Path:` in Visual Studio... then the macro will be deleted.
Since both languages use MSBuild for both languages environment variables (macros) can be used in output pathes.
It's the C# project editor which converts non alphanumeric characters. If you enter the path with an environment variable by editing the C# project with notepad everything (seems) to work fine.