Open
Conversation
- updated "Microsoft.AspNetCore.Mvc" to version 2.3.9 - added System.Text.RegularExpressions in Version 4.3.1 to netstandard2.0, as transitive version 4.3.0 has at least one vulnerability with high severity - Sample: - added net8.0;net9.0;net10.0 as TargetFramework - replaced WebMarkupMin.AspNetCore2 with WebMarkupMin.AspNetCoreLatest - replaced services.AddMvc(); with services.AddMvc(options => options.EnableEndpointRouting = false); - removed "using Microsoft.AspNetCore.Http.Internal;" call as namespace is not found in modern .net versions - removed "app.UseBrowserLink();" as only working until ASP.NET Core 2.2
Author
|
ok, looks like appveyor misses VS2026 / .net10 support so CI fails. |
Author
|
ok, installing .NET10 SDK works and CI is green now. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix for #32 by bumping "Microsoft.AspNetCore.Mvc" to version 2.3.9 and also adding explicit net8.0;net9.0;net10.0 as TargetFramework and other small changes to get it working in modern .net versions.