-
Notifications
You must be signed in to change notification settings - Fork 0
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
[ASCN-413] Upgrade to .NET 8 #22
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking through the code changes everything makes sense to me 👍🏼 Thanks for putting this together. Apps that use OpServer will need to update their refs separately I presume?
What refs do you mean? The one to Exceptional? I've been doing that for all the apps I update to .NET 8/Microsoft.Data.SqlClient. Or are there other refs I'm missing? |
Ah yes, I was thinking of Exceptional. Thanks 👍🏼 |
This PR upgrades OpServer to .NET 8 and all packages to the latest supported version.
This completely removes any reference to System.Data.SqlClient.
Here is a successfull Octopus deploy to https://opserver.ascn-dev.int.gcp.stackoverflow.net/.
I've manually tested the Exceptions and SQL modules in OpServer and everything looks good.