You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to have this target use the @(IntermediateAssembly) item instead.
The current behavior can be problematic when you happen to have any custom target adjusting that item. This requires the target to also be aware of ILC targets, as seen here: AvaloniaUI/Avalonia#14966
As far as I can tell, build, standard publish and ILLink all seem to respect changing @(IntermediateAssembly), only ILC doesn't.
Is there any reason for the current behavior? Is it possible to use @(IntermediateAssembly) for consistency?
Thanks!
The text was updated successfully, but these errors were encountered:
Currently, NativeAOT hardcodes its main input to be
$(IntermediateOutputPath)$(TargetName)$(TargetExt)
through theComputeIlcCompileInputs
target:runtime/src/coreclr/nativeaot/BuildIntegration/Microsoft.NETCore.Native.targets
Line 171 in eb864bf
It would be nice to have this target use the
@(IntermediateAssembly)
item instead.The current behavior can be problematic when you happen to have any custom target adjusting that item. This requires the target to also be aware of ILC targets, as seen here: AvaloniaUI/Avalonia#14966
As far as I can tell, build, standard publish and ILLink all seem to respect changing
@(IntermediateAssembly)
, only ILC doesn't.Is there any reason for the current behavior? Is it possible to use
@(IntermediateAssembly)
for consistency?Thanks!
The text was updated successfully, but these errors were encountered: