FEAT: Upgrade to .NET 10 #102

matthewtoghill · 2025-12-01T22:56:14Z

Description

Upgrade the solution to .NET 10.

chore: Packages updated
fix: Breaking changes resolved with:
- MockQueryable - API change related to AsQueryable()
- Swashbuckle & Microsoft.OpenApi - API changes related to upgrading the OpenApi version
fix: remove [FromFile] annotation on endpoint IFormFile parameter
feat: make use of new unbound generic type support for nameof
feat: move common MSBuild properties to Directory.Build.props file

Related Issue

Closes #101

How Has This Been Tested?

Tests pass
Test apps created from template created successfully, build and run as expected

Types of changes

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

My code follows the code style of this project.
My change requires a change to the documentation.
I have updated the documentation accordingly.
I have read the CONTRIBUTING document.
I have added tests to cover my changes.
All new and existing tests passed.

socket-security · 2025-12-01T22:57:01Z

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Quality	License
	skiasharp@3.119.0 ⏵ 3.119.1	^-1
	scalar.aspnetcore@2.11.6
	xunit.runner.visualstudio@3.1.4 ⏵ 3.1.5
	skiasharp.nativeassets.linux.nodependencies@3.119.0 ⏵ 3.119.1
	azure.storage.blobs@12.25.0 ⏵ 12.26.0	⁺²
	awesomeassertions@9.1.0 ⏵ 9.3.0
	serilog.sinks.console@6.0.0 ⏵ 6.1.1	^-2
	microsoft.net.test.sdk@17.14.1 ⏵ 18.0.1
	serilog.sinks.applicationinsights@4.0.0 ⏵ 4.1.0
	linqkit.microsoft.entityframeworkcore@9.0.8 ⏵ 10.0.9	⁺³	⁺²
	delegatedecompiler.entityframeworkcore5@0.34.2 ⏵ 0.35.3
	keycloak.net.core@1.0.34 ⏵ 1.0.38
	mockqueryable.moq@7.0.4-beta ⏵ 10.0.1	⁺¹
	polly.extensions@8.6.3 ⏵ 8.6.5
	polly.core@8.6.3 ⏵ 8.6.5
	testcontainers@4.6.0 ⏵ 4.9.0
	testcontainers.mssql@4.6.0 ⏵ 4.9.0
	testcontainers.rabbitmq@4.6.0 ⏵ 4.9.0
	testcontainers.keycloak@4.6.0 ⏵ 4.9.0
	testcontainers.azurite@4.6.0 ⏵ 4.9.0
	serilog.settings.configuration@9.0.0 ⏵ 10.0.0
	serilog.extensions.hosting@9.0.0 ⏵ 10.0.0
	serilog.aspnetcore@9.0.0 ⏵ 10.0.0
	masstransit@8.5.2 ⏵ 8.5.7	⁺¹	⁺²
	masstransit.rabbitmq@8.5.2 ⏵ 8.5.7
	masstransit.azure.servicebus.core@8.5.2 ⏵ 8.5.7	⁺¹	⁺²
	masstransit.entityframeworkcore@8.5.2 ⏵ 8.5.7	⁺¹	⁺²
	fluentvalidation@12.0.0 ⏵ 12.1.1
	fluentvalidation.dependencyinjectionextensions@12.0.0 ⏵ 12.1.1
	microsoft.extensions.diagnostics.healthchecks.entityframeworkcore@9.0.8 ⏵ 10.0.1	⁺¹
	microsoft.aspnetcore.authentication.jwtbearer@9.0.8 ⏵ 10.0.1
	microsoft.extensions.hosting@9.0.8 ⏵ 10.0.1	⁺¹		^-9
See 9 more rows in the dashboard

View full report

…er small refactors to update the current code with the most recent language features.

Added CompatibilityLevel configuration to EF Core configuration for most recent features usages.

matthewtoghill · 2025-12-10T10:17:46Z

src/Content/Backend/Solution/Monaco.Template.Backend.sln

Now that we've upgraded to .NET10 in this PR, we need to decide if we want to continue to keep a .sln file for compatibility or if it's possible to remove it and just have the new .slnx file.

Yup, I believe we can get rid of the .sln file for good 🙂

I've removed the .sln file but I think the templating has not fixed the issue with XML conditional processing in .slnx files. We have a solution to that though so it is not a problem.

Sorry, what problem was it?

Within the .slnx file we have the  blocks. These were not being processed in the expected way for this file type when we first added the .slnx file. We have a SpecialCustomOperations item in the template.json file that deals with handling these blocks in the .slnx file.

I've not tested if the templating has been updated more recently to fix the issue on their end that would mean the SpecialCustomOperations item for the .slnx file is no longer needed.

Ok, now I get it... I would have expected that the .slnx would behave like any other XML file and that they would have prepared the templating engine accordingly... Isn't there any information about this for the templating engine?

src/Content/Backend/Solution/Directory.Build.props

CesarD · 2025-12-10T16:18:42Z

@matthewtoghill please check the latest changes out... I've replaced the Swashbuckle implementation for Swagger with Scalar and also included the document and operation transformers for the API security so everything can work pretty similar to how it was with Swashbuckle, but without all the custom code for fixing its issues.
Feel free to give it a try and check out the different scenarios. It should exclude the security transformations if Auth flag is disabled.

… block extension methods.

…auth flag is false as base property is also removed

matthewtoghill · 2025-12-15T18:16:32Z

@matthewtoghill please check the latest changes out... I've replaced the Swashbuckle implementation for Swagger with Scalar and also included the document and operation transformers for the API security so everything can work pretty similar to how it was with Swashbuckle, but without all the custom code for fixing its issues. Feel free to give it a try and check out the different scenarios. It should exclude the security transformations if Auth flag is disabled.

Looks good, there was an old issue related to the auth flag being false that is now fixed, or it can be fixed another way if you prefer. When auth or apiService flags are false then the IntegrationTest base class does not include the RequiresAuthentication property.

EntityTypeConfiguration now uses ValueGeneratedNever for IDs, shifting ID generation from the database to the application (via Guid.NewGuid()). Updated entity constructors, command handlers, and tests to align with this approach. Adjusted EF Core migrations and model snapshots to remove ValueGeneratedOnAdd. Cleaned up related test and factory code for consistency.

matthewtoghill · 2025-12-23T16:35:19Z

...nt/Backend/Solution/Monaco.Template.Backend.Common.Api/OpenApi/OAuth2OperationTransformer.cs

+		}
+
+		var requiredScopes = metadata.OfType<IAuthorizeData>()
+									 .Where(a => !string.IsNullOrEmpty(a.Policy))


Better to use string.IsNullOrWhiteSpace?

Refactored MediatorExtensions to support CancellationToken in all methods, improving async and cancellation handling. Introduced CreatedResponse record for standardized creation responses. Updated Companies, Products, and Files endpoints to use new Mediator methods and return Created<CreatedResponse>. Adjusted integration tests to validate CreatedResponse. Improved code clarity and authorization policy checks.

CesarD · 2025-12-28T21:12:36Z

@matthewtoghill please review the latest changes I introduced.
Basically, I refactored a little bit the MediatR extensions we had to improve a little bit their naming and also to include the CancellationToken in the async calls being made. I also included a couple more methods for simplifying how to return other types of responses from the endpoint in case of success.

Lastly, please be kind to let me know if you find any issue when running the whole tests battery (including the Integration ones in the same process)... I experienced an issue with the CreateProduct one, where the assertion checking if the ProductCreated message has been consumed is failing, but when I run it individually it succeeds, so I'm not sure if it's my crappy laptop or what, so if you could run it and let me know, that would be great!

Thanks! Cheers!

matthewtoghill added 6 commits December 1, 2025 08:22

feat: update target framework on projects to dotnet 10

febce6c

feat: update release pipeline to use dotnet-version 10.x

1d0c713

chore: update readme

04f3827

fix: remove FromForm annotation on endpoint for IFormFile parameter

fb3d167

chore: update packages and resolve breaking changes

3c06631

feat: update use of nameof with support for unbound generic types

ded88d2

CesarD self-requested a review December 2, 2025 02:00

matthewtoghill and others added 6 commits December 3, 2025 11:10

chore: formatting

10ad0c4

Applying C# 14 new features to code, such as extension blocks and oth…

feb2b7f

…er small refactors to update the current code with the most recent language features.

Resolving merge conflicts.

922ee59

Updated dependencies.

2fa537a

Added CompatibilityLevel configuration to EF Core configuration for most recent features usages.

chore: move common MSBuild properties to Directory.Build.props file

e3596dc

chore: update packages

14a8fc7

matthewtoghill commented Dec 10, 2025

View reviewed changes

src/Content/Backend/Solution/Directory.Build.props Show resolved Hide resolved

refactor: Migrate OpenAPI docs from Swagger to Scalar.AspNetCore

1a00035

CesarD and others added 5 commits December 11, 2025 01:53

refactor: finished converting the last missing extension methods into…

3d515d7

… block extension methods.

chore: update packages

226b0e6

chore: remove RequiresAuthentication from integration tests when the …

67f4af3

…auth flag is false as base property is also removed

feat: remove sln file

ba2d991

chore: match condition to base class

dcc6cdb

matthewtoghill commented Dec 23, 2025

View reviewed changes

CesarD added 2 commits December 28, 2025 21:47

Undo accidental cleanup.

fa691aa

FEAT: Upgrade to .NET 10 #102

Are you sure you want to change the base?

FEAT: Upgrade to .NET 10 #102

Uh oh!

Conversation

matthewtoghill commented Dec 1, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Related Issue

How Has This Been Tested?

Types of changes

Checklist:

Uh oh!

socket-security bot commented Dec 1, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

CesarD commented Dec 10, 2025

Uh oh!

matthewtoghill commented Dec 15, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

CesarD commented Dec 28, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

matthewtoghill commented Dec 1, 2025 •

edited

Loading

socket-security bot commented Dec 1, 2025 •

edited

Loading