John Korsnes

Re `/fxr`: Re-installing .NET 5 (or even .NET 3.1) fixes the issue, both if I still keep the .NET 6 or if I uninstall .NET 6 folders. So a stable...

I could be wrong, but since deleting all .NET 6 folders does not help, the only thing left I can see as remnants that could be of issue is that...

>install 6.0 then install 3.1 and check the version of the host. If it is 3.1, file a bug Right, I thought this would be the repo for that. If...

Ok, gotcha. Or even breaking 3.1, since I only get the build error for Functions which have a 3.1 requirement.

>dotnet new console -f netcoreapp3.1 ☝️ No, this builds fine. There isn't an a general issue with building netcoreapp3.1 apps. There's only an [issue with building Azure Functions projects using...

As another pointer to the RC1 installer (or the RC1 exe) being the issue. If I install RC1 then RC2, then uninstall RC2 (removing all RC2 folders), the build works....

I also get this odd warning only _once_ (on the first restore) if I try to clear local caches first. >The ExtensionsMetadataGenerator package was not imported correctly. Are you missing...

Ok, great. So RTM also has this issue. > /Users/johnkors/.nuget/packages/microsoft.azure.webjobs.script.extensionsmetadatagenerator/4.0.1/build/Microsoft.Azure.WebJobs.Script.ExtensionsMetadataGenerator.targets(37,5): error : Metadata generation failed. Exit code: '137' Error: 'Failed to initialize CoreCLR, HRESULT: 0x80004005' [/var/folders/27/l893mwzn2611z7x3w_006_wr0000gn/T/erlqzr1n.mqi/WorkerExtensions.csproj] > 1 Warning(s) >...

Re-installing .NET 5 after .NET 6 resolves the issue again: > ➜ strings /usr/local/share/dotnet/dotnet | grep "@(#)" > @(#)Version 6.0.21.52210 @Commit: 4822e3c3aa77eb82b2fb33c9321f923cf11ddde6 [installing .NET 5 after .NET 6] > >...

Ok, I caved and just deleted all earlier SDKs. No idea why this fails, and don't have time to dig further. Installing .NET 6 from a clean slate works.