chore(deps): update dependency microsoft.aspnetcore.all to v2.2.8 - autoclosed #152
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.9
->2.2.8
Release Notes
aspnet/AspNetCore
v2.2.8
Repos
v2.2.7
Repos
v2.2.6
Repos
v2.2.3
Repos
v2.2.1
Repos
v2.2.0
ASP.NET Core release notes
We have disabled view recompilation when .cshtml change by default (except for the
Development
environment). A new flag calledAllowRecompilingViewsOnFileChange
has been introduced inRazorViewEngineOptions
, which can be used to configure whether the view engine will watch for file changes. The settings is set tofalse
by default for all environments butDevelopment
. If you are using Visual Studio to debug, then it will launch the application in theDevelopment
environment by default. You can find more details about the change by looking at this PR: https://github.com/aspnet/Mvc/pull/8369/filesIn 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:
Repos
v2.1.25
Repos
v2.1.24
Repos
v2.1.23
Repos
v2.1.22
Repos
v2.1.20
Repos
v2.1.18
Repos
v2.1.16
Repos
v2.1.15
Repos
v2.1.14
Repos
v2.1.13
Repos
v2.1.12
Repos
v2.1.9
Repos
v2.1.7
Repos
v2.1.6
Compare Source
The list of changes in this release is available here:
v2.1.5
Compare Source
Read more about the 2.1.5 update here: https://blogs.msdn.microsoft.com/dotnet/2018/10/02/net-core-october-2018-update/
v2.1.4
Compare Source
ASP.NET Core 2.1.4
For more details, see the blog post here: https://blogs.msdn.microsoft.com/dotnet/2018/09/11/net-core-september-2018-update.
v2.1.3
Compare 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 (Value Conversion of custom struct type throws exception if it doesn't implement == and != operators dotnet/efcore#12290)float?
(SumAsync throw Exception when used over float? dotnet/efcore#12314)ActionResult<T>
([Patch] ProducesResponseType doesn't infer the type from ActionResult<T> aspnet/Mvc#7875)IEnumerable<IFormFile>
ApiController parameters on is incorrectly inferred as FromBody (Port #7770 fix to 2.1.2 or 2.1.3 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:
Version mismatches can cause apps to fail with System.IO.FileLoadException
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 dotnet/aspnetcore#3503
v2.1.2
Compare Source
ASP.NET Core 2.1.2 Release Notes
This update includes two security fixes. Please see the following links for details.
v2.1.1
Compare 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.0
Compare Source
ASP.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.ViewCompilation
package.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
IAuthorizationPolicyProvider
and settingAllowCombiningAuthorizeFilters
totrue
causes aNullReferenceException
.Workaround: Disable
AllowCombiningAuthorizeFilters
or use a singleAuthorizeFilter
XmlSerializerOutputFormatter throws InvalidCastException for async action methods
Invoking an Async action method may result in an
InvalidCastException
when using theXmlSerializerOutputFormatter
.Workaround: Wrap the return type in
ActionResult<T>
. Ex. replace the return typeTask<IEnumerable<string>>
withTask<ActionResult<IEnumerable<String>>>
.Configuration
📅 Schedule: "before 8am" in timezone Europe/London.
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.