-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
New .NET versions are not recognized (if there is a .NET version already installed) #31
Comments
When you say the app is targeting |
Target is still So, if
|
Are you sure this is not related to this issue? dotnet/core#7176 As far as I know, .NET deployments are minor-agnostic. |
I think indeed it is related to that issue, but I didn't know that, I thought to fix this the latest release needs to be installed.
You're right, so it's not necessarily required to have the latest .NET version installed. |
No worries, I hit the same problem recently too. |
Version
ver 2.2.0
Details
Hi!
I hope you're doing well!
Recently I figured out that if you have
.NET 6.0.1
installed (for example), but your app requires.NET 6.0.2
thenDotnetRuntimeBootstrapper
won't install the new version and the app won't start.I didn't found a solution to change the sub-version in VS, like you can only set
net6.0-windows
and if you install Visual Studio updates it may get increased automatically ...But if you don't have .NET 6.0.x installed, it installs the newest version and everything works fine.
Steps to reproduce
You can test it with the Windows Sandbox (if you have it installed)
.NET 6.0.1
DotnetRuntimeBootstrapper
which is targetting.NET 6.0.2
The text was updated successfully, but these errors were encountered: