Update ASP.NET Core packages #801
Closed
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.
This PR contains the following updates:
2.0.0->2.2.02.0.0->2.2.52.0.0->2.2.02.0.0->2.2.0Release Notes
aspnet/Hosting
v2.2.0Compare Source
v2.1.1Compare Source
v2.1.0Compare Source
v2.0.3Compare Source
v2.0.2Compare Source
v2.0.1Bugs Fixed
aspnet/AspNetCore
v2.2.5Compare Source
v2.2.2Compare Source
v2.2.0Compare Source
ASP.NET Core release notes
We have disabled view recompilation when .cshtml change by default (except for the
Developmentenvironment). A new flag calledAllowRecompilingViewsOnFileChangehas been introduced inRazorViewEngineOptions, which can be used to configure whether the view engine will watch for file changes. The settings is set tofalseby default for all environments butDevelopment. If you are using Visual Studio to debug, then it will launch the application in theDevelopmentenvironment by default. You can find more details about the change by looking at this PR: aspnet/Mvc#8369In case you would like to keep the view recompilation enabled for your project, you can choose so by configure Razor options in Startup.ConfigureService method using the following code block:
services.AddMvc() .SetCompatibilityVersion(CompatibilityVersion.Version_2_2) .AddRazorOptions(options => options.AllowRecompilingViewsOnFileChange = true);Repos
v2.1.11Compare Source
v2.1.3Compare Source
ASP.NET Core 2.1.3
We are pleased to announce the release of ASP.NET Core 2.1.3.
Bugs Fixed
==and!=operators (aspnet/EntityFrameworkCore#12290)float?(aspnet/EntityFrameworkCore#12314)ActionResult<T>(aspnet/Mvc#7875)IEnumerable<IFormFile>ApiController parameters on is incorrectly inferred as FromBody (aspnet/Mvc#7970)Known issues
Razor compilation is slow if you have a space in your username
aspnet/Razor#2406 - when building an ASP.NET Core app as a user with a space in username, build times may be a few minutes more than it takes when building as a different user.
Solutions:
EntityFrameworkCore commands in the Visual Studio Package Manager Console issue a warning
When using EntityFrameworkCore commands in the Package Manager Console, you may see a warning with this text.
Available solutions:
Some ASP.NET Core 2.1 applications will be affected by a bug in the .NET Core host (see dotnet/core-setup#4512) which can cause apps to fail with System.IO.FileLoadException. The issue may also be present in your app, even if the app does not fail with System.IO.FileLoadException.
This issue and workarounds are described in greater detail in aspnet/Home#3503
v2.1.2Compare Source
ASP.NET Core 2.1.2 Release Notes
This update includes two security fixes. Please see the following links for details.
v2.1.1Compare Source
ASP.NET Core 2.1.1 Release Notes
We are pleased to announce the release of ASP.NET Core 2.1.1.
v2.1.0ASP.NET Core 2.1.0 Release Notes
We are pleased to announce the release of ASP.NET Core 2.1.0.
Known Issues
Warning when building new ASP.NET Core project that targets .NET Framework
Building a new ASP.NET Core project that targets net461 produces the following warning:
Workaround: Remove the reference to the
Microsoft.AspNetCore.Mvc.Razor.ViewCompilationpackage.Windows authentication is not enabled after creating project with the Windows authentication option selected
When creating a template with Windows authentication, the settings to enable Windows authentication in launchSettings.json are not applied.
Workaround: Modify launchSettings.json as follows:
NullReferenceException when using a custom IAuthorizationPolicyProvider and AllowCombiningAuthorizeFilters is set to true
Using a custom
IAuthorizationPolicyProviderand settingAllowCombiningAuthorizeFilterstotruecauses aNullReferenceException.Workaround: Disable
AllowCombiningAuthorizeFiltersor use a singleAuthorizeFilterXmlSerializerOutputFormatter throws InvalidCastException for async action methods
Invoking an Async action method may result in an
InvalidCastExceptionwhen using theXmlSerializerOutputFormatter.Workaround: Wrap the return type in
ActionResult<T>. Ex. replace the return typeTask<IEnumerable<string>>withTask<ActionResult<IEnumerable<String>>>.v2.0.3Compare Source
ASP.NET Core 2.0.3 Release Notes
We are pleased to announce the release of ASP.NET Core 2.0.3!
You can find details on the issues fixed in this release for the following components on their corresponding release pages:
Breaking Changes
There are no breaking changes in this release.
Known Issues
There are no known issues with this release.
v2.0.2Compare Source
v2.0.1Compare Source
aspnet/Mvc
v2.2.0Compare Source
v2.1.3Compare Source
v2.1.2Compare Source
v2.1.1Compare Source
v2.1.0Compare Source
v2.0.4Compare Source
v2.0.3Compare Source
v2.0.2Compare Source
v2.0.1Bugs Fixed
aspnet/StaticFiles
v2.2.0Compare Source
v2.1.1Compare Source
v2.1.0Compare Source
v2.0.3Compare Source
v2.0.2Compare Source
Renovate configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻️ Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "
rebase!".👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot. View repository job log here.