Predefined type 'System.Runtime.CompilerServices.IsExternalInit' is not defined or imported about isexternalinit HOT 3 CLOSED

Thanks a lot for the additional details! I think that I am going to close the issue then for the moment. If this does turn out to be a different issue, feel free to reopen it/create a new one!

Just a note: Both this package and the Nullable package seem to have some issues in the latest .NET SDK on newer OSs. Maybe this is also related to the issue you are describing here. In any case, we will have to wait until we find out what the issue is exactly there.

from isexternalinit.

Hey, thanks for reporting the issue! Could you perhaps attach a solution which allows me to reproduce the problem? That (should) make it easier for me to troubleshoot it.

from isexternalinit.

I just experiemented with this a bit.

It's related to this problem: dotnet/sdk#24124 (comment)

When I put the global.json I mention there in the solution folder, it works, presumably because 6.0.103 still works on Windows 7. When I remove it the weird errors occur. This could also explain why it seems to work when the build is started by a legacy csproj-format project, afaik the old csproj-format is using MSBuild and not dotnet.

I think there is an internal failure where the .cs file from the package is not correctly added to the compilation with dotnet >6.0.103 under Windows 7. Probably not something you can do anything about.

The solution for me is to either not use the package, or put a global.json with a version that still works on Windows 7. Referencing a package that comes with its own public IsExternalInit (not .cs file) works too.

from isexternalinit.