We should think about removing our internal uses of netcoreapp. For instance, in property names like $(NetCoreAppCurrent). Now that we are back to using net I bet netcoreapp will be confusing in the future.
/cc @dotnet/runtime-infrastructure
Tagging subscribers to this area: @ViktorHofer
See info in area-owners.md if you want to be subscribed.
Let's rename the shared framework. /sarcasm
And build a shared-framework-forwarded-to feature in the host.
and let's not forget to also forward the .NETCoreApp TFI to .NET.
On a related note, we use the NETCOREAPP define throughout libraries: https://gist.github.com/CoffeeFlux/70d8f08f42402e5b345320a1c0ea23c7
Is this still needed?
netcoreapp is easier to grep for 馃榿
Most helpful comment
And build a shared-framework-forwarded-to feature in the host.