resolve refuses a project that writes <AssemblyName>$(Something)</AssemblyName> with the output path cannot be composed from it. That was true when the path was composed. After #31 it is not: MSBuild is asked for TargetPath, and it names the file whatever the property expands to.
The refusal now stops a project the debugger could launch, for a reason the code no longer relies on.
Scope
Let a project with an unevaluated AssemblyName through to the TargetPath query, and refuse only if that query has no answer — which is also what happens today on an SDK older than 8, where the composed path really is the only one available and really cannot be composed.
OutputType written as a property stays refused: that one decides whether to launch at all, and a guess there points the debugger at something with no entry point.
Not for 0.2.0
Post-tag, with #33: it widens what d accepts rather than fixing something shipped.
resolverefuses a project that writes<AssemblyName>$(Something)</AssemblyName>with the output path cannot be composed from it. That was true when the path was composed. After #31 it is not: MSBuild is asked forTargetPath, and it names the file whatever the property expands to.The refusal now stops a project the debugger could launch, for a reason the code no longer relies on.
Scope
Let a project with an unevaluated
AssemblyNamethrough to theTargetPathquery, and refuse only if that query has no answer — which is also what happens today on an SDK older than 8, where the composed path really is the only one available and really cannot be composed.OutputTypewritten as a property stays refused: that one decides whether to launch at all, and a guess there points the debugger at something with no entry point.Not for 0.2.0
Post-tag, with #33: it widens what
daccepts rather than fixing something shipped.