-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello world targeting .NET 5.0 master nightly fails to build using VS due to strong name validation failure #12082
Comments
Same Problem! |
Same problem here. |
Weird that I'm having the same problem with @pr0vieh, @YeskaNova - do you happen to experience the same problem targeting other framework versions? |
Oops |
@Gnbrkm41 If you have .net sdk 5.xx installed, you have to set in global.json a 3.xx version if you want to build a 3.xx project without having that problem. Otherwise you have to uninstall 5.xx sdk |
Great, thanks for the additional information! |
Take a look at this... |
That doesn't appear to be related with this "strong name validation failure", no? |
Looks like it's fixed in dotnet/runtime#38105. I cannot reproduce this issue on 5 P8.20326.16. |
(Very likely that I'm in the wrong repo, please feel free to move this to the correct repo if that is the case)
Currently I have 5.0.100-preview.7.20315.4 SDK Installed using the installer from the dotnet/installer repo. FWIW, I'm using one of the Windows 10 Pro Insiders (ko-KR, Fast ring, 19645) builds.
Using VS2019 Community 16.7 P2, I am unable to build a hello world project created using the default console app template.
ConsoleApp35.csproj
Program.cs:
Build log:
The build process seemingly does nothing for about a minute... then it just fails with the error above.
Funnily enough... if I attempt this using
dotnet build
from CLI it seems to run just fine. This also happens with an other project of mine that also targets net5.0.Attaching the binary log file from VS and CLI for comparison purposes. (Please remove the trailing
.log
extension, I had to change its extension because GitHub won't allow binlog files by default)cli.binlog.log
vs.binlog.log
Any clues on troubleshooting would be appreciated.
The text was updated successfully, but these errors were encountered: