Vitek Karas

I'm sorry - what I said sounded like I think that the installer doesn't do it correctly. I definitely hope it does it correctly. I just checked on Linux, and...

Actually one other simple thing to try: ``` dotnet new console -f netcoreapp3.1 dotnet build dotnet ./bin/Debug/netcoreapp3.1/app.dll ``` (I'm trying to get a local repro, but no luck so far)

I'm going to play devil's advocate and only provide negative feedback ;-) For the proposal from Jackson - feature name model: * The feature name string is the least visible...

I know the experience has been somewhat lacking in the past, but I think we've made some great improvements recently. For example: https://github.com/dotnet/runtime/pull/78087

> Is there an option to instruct the linker to specifically not trim away constructor parameters? `--keep-metadata parametername` this will avoid removing names from method parameters. It obviously comes with...

Side note about the screenshot from registry. The install locations are actually only used from the 32-bit view of the registry. So on x64 OS you need to look at...

@joeloff do you want to move the bug to the right place then? Since it's really a setup issue, we should not be writing the path there.

@Varorbc yes - that's what added that section to `dotnet --info`, but it's reading the info from registry, which is wrong in this case.

> Ok, yeah it kind of makes sense you can't put ILLink attributes on an enum. This has been discussed several times in the past, but it's difficult. In IL...

Can confirm the same behavior as @stevenwdv - for me this seems to happen often after the computer wakes up from sleep. It is happening so often that I'm hesitant...