I think it's the right time to upgrade to .NET 6 :)

[ghost]

Mads, please, do you have this in plan ?

[dynamoRando]

Just an FYI - I tried upgrading to .NET6 locally and ran into the following error on startup:

TypeLoadException: Could not load type 'Microsoft.AspNetCore.Http.Features.IHttpBufferingFeature' from assembly 'Microsoft.AspNetCore.Http.Features, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'.

WebMarkupMin.AspNetCore2.WebMarkupMinMiddleware.ProcessAsync(HttpContext context, bool useMinification, bool useCompression)
System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start<TStateMachine>(ref TStateMachine stateMachine)
System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start<TStateMachine>(ref TStateMachine stateMachine)
WebMarkupMin.AspNetCore2.WebMarkupMinMiddleware.ProcessAsync(HttpContext context, bool useMinification, bool useCompression)
WebMarkupMin.AspNetCore2.WebMarkupMinMiddlewareBase.Invoke(HttpContext context)
WebEssentials.AspNetCore.OutputCaching.OutputCacheMiddleware.ServeFromMvcAndCacheAsync(HttpContext context)
WebEssentials.AspNetCore.OutputCaching.OutputCacheMiddleware.InvokeAsync(HttpContext context)
Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
WilderMinds.MetaWeblog.MetaWeblogMiddleware.Invoke(HttpContext context, MetaWeblogService service)
Microsoft.AspNetCore.Diagnostics.StatusCodePagesMiddleware.Invoke(HttpContext context)
Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)

To fix:

• Remove the reference to WebMarkupMin.AspNetCore2 in the NuGet dependencies
• Update to WebMarkupMin.AspNetCore6
• Update the reference from WebmarkupMin.AspNetCore2 in Startup.cs to WebMarupMin.AspNetCore6

That should be it; as far as I can tell.

[dynamoRando]

Created PR #171 for this

[ghost]

Great, but it would also use the latest features that .NET 6 allows. Do you want to do that ? :)

[xaberue]

Seems that the project already has this upgrade developed and merged, can be closed that issue?