-
-
Notifications
You must be signed in to change notification settings - Fork 65
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
Issue with 6.0.2 SDK update #42
Comments
Set runs on to windows-2019. Set dotnet version trimble-oss#44 trimble-oss#42
Set runs on to windows-2019. Set dotnet version trimble-oss#44 trimble-oss#42
Global.json has been removed #220. Project is still built with 6.0.101 on the github action for wider compatibility. |
It looks like the backward compatibility might be broken now? The action is still targeting 6.0.101 - not sure when/how this got broken. It might be useful to investigate. Maybe just use the latest version now and ensure this is called out in the docs? |
This was first broken in 2.22.9. Most likely it was introduced by this commit to bump the setup-dotnet action. |
Changing actions/setup-dotnet@v3 to actions/setup-dotnet@v2 fixes the issue. It might be time to move to the new version though and run a check in the upgrade script. |
Versions older than 6.0.2 are not supported now (App will fail to run). Prompt user to upgrade. trimble-oss#42
Versions older than 6.0.2 are not supported now (App will fail to run). Prompt user to upgrade. #42
Build with latest version of SDK. Previously this was set to 6.0.101 due to breaking changes. Backward compatibility was broken with update to actions/setup-dotnet@v3. Issue is now documented and latest version is preferred. trimble-oss#42
Build with latest version of SDK. Previously this was set to 6.0.101 due to breaking changes. Backward compatibility was broken with update to actions/setup-dotnet@v3. Issue is now documented and latest version is preferred. #42
GH Actions have now been updated to use the latest version. Backward compatibility issue is documented. |
The issue is described here:
dotnet/winforms#6663
Since upgrading to the latest VS, the application builds with 6.0.2 and will fail to run on a machine without this version installed. The app fails silently and you have to discover the error using event viewer.
Ideally you would at least be prompted to upgrade to the new version.
As a workaround we can use 6.0.101 be specifying this in the Global.json and editing the workflows to use 6.0.101. At some point we might want to revert this change and upgrade to a newer version.
The text was updated successfully, but these errors were encountered: