Open baronfel opened 7 years ago
Sure; PR for the 'common' properties inside $(...)
and we can have a whitelist that gets interpolated. But remember that MsBuild is rather close to turing complete (or maybe it is; not sure), so it's a fool's errand to support all and every evaluation it's capable of without implementing the engine itself.
I like to consolidate as much as possible the variation points in my project files on the configuration, so I tend to have a project file that looks like this:
When
Project::output_dll
is called, it correctly locates thefallback_output_path
ofbin\$(Configuration)
, but it doesn't apply any existing (or even just a subset of common) MSBuild properties to try and resolve that path. I can see where this might go off the rails, but at the same time I'd like to use well-known properties like Configuration and Platform to make paths and reduce duplication.