-
Notifications
You must be signed in to change notification settings - Fork 2
.NET 10 Update #16
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
.NET 10 Update #16
Conversation
- FluentAssertions went commercial this year and AwesomeAssertions is a drop-in replacement fork
41d3118 to
e36fd9f
Compare
| @@ -1,4 +1,4 @@ | |||
| Copyright 2023 Lukas Angerer | |||
| Copyright 2025 Lukas Angerer & Dominic Ullmann | |||
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.
😂 Not sure why I was alone in that note. Probably copy-pasta from the very early stages.
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.
Thanks for updating it 👍
| </PropertyGroup> | ||
|
|
||
| <ItemGroup> | ||
| <PackageReference Include="AwesomeAssertions" Version="9.3.0" /> |
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.
Yes, I also updated to AwesomeAssertions because of the whole going commercial bit.
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.
Nice, that it just worked without any relevant code changes.
DominicUllmann
left a comment
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.
Looks good, thanks for the update.
Simple update to support .NET 10 while also updating to the latest Ninject version 3.3.6. Also updates all other dependencies to their latest version.
The build now has 4 warnings due to the fact that with .NET 10 the
WebHostBuilderandIWebHosthave been deprecated. Due to the heavy customization of the configuration process this is not going to be a simple change and is probably going to be a breaking change. Since that requires some more thought, I'll create a separate issue for that topic and we'll see when I get to that.