Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore(deps): update dependency microsoft.aspnetcore.all to 2.2.8 #175

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update dependency microsoft.aspnetcore.all to 2.2.8 #175

wants to merge 1 commit into from

Conversation

renovate-bot
Copy link

@renovate-bot renovate-bot commented Oct 4, 2021 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
Microsoft.AspNetCore.All (source) 2.0.9 -> 2.2.8 age adoption passing confidence

Release Notes

aspnet/AspNetCore (Microsoft.AspNetCore.All)

v2.2.8: .NET Core 2.2.8

Repos

v2.2.7: .NET Core 2.2.7

Repos

v2.2.6: .NET Core 2.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 called AllowRecompilingViewsOnFileChange has been introduced in RazorViewEngineOptions, which can be used to configure whether the view engine will watch for file changes. The settings is set to false by default for all environments but Development. If you are using Visual Studio to debug, then it will launch the application in the Development environment by default. You can find more details about the change by looking at this PR: https://github.com/aspnet/Mvc/pull/8369/files

In 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.25: .NET Core 2.1.25

Repos

v2.1.24: .NET Core 2.1.24

Repos

v2.1.23: .NET Core 2.1.23

Repos

v2.1.22: .NET Core 2.1.22

Repos

v2.1.20: .NET Core 2.1.20

Repos

v2.1.18: .NET Core 2.1.18

Repos

v2.1.16: .NET Core 2.1.16

Repos

v2.1.15: .NET Core 2.1.15

Repos

v2.1.14: .NET Core 2.1.14

Repos

v2.1.13: .NET Core 2.1.13

Repos

v2.1.12: .NET Core 2.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

Known issues

Razor compilation is slow if you have a space in your username

https://github.com/aspnet/Razor/issues/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:

  1. Add a PackageReference to your project file (.csproj) to update the Razor compiler.
<PackageReference Include="Microsoft.AspNetCore.Razor.Design" Version="2.1.2" />
  1. Change your username to something without spaces.
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.

The EF Core tools version '2.1.1-rtm-30846' is older than that of the runtime '2.1.2-rtm-30921.' Update the tools for the latest features and bug fixes.

Available solutions:

  1. Do nothing. This warning can be ignored for now. We are working on a fix for a future 2.1 update.
  2. Update the version of the Microsoft.AspNetCore.App package.
<PackageReference Include="Microsoft.AspNetCore.App" Version="2.1.3" />

⚠️ This may have unintended consequences on your deployment environment. If the deployment environment does not have the the 2.1.3 runtime, apps will fail to start with an error. In Azure or apps hosted behind IIS, this may appear as HTTP 502.5 error.

It was not possible to find any compatible framework version
The specified framework 'Microsoft.AspNetCore.App', version '2.1.3' was not found.

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 https://github.com/aspnet/Home/issues/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:

    There was a mismatch between the processor architecture of the project being built "x86" and the processor architecture of the reference "c:\Program Files\dotnet\sdk\NuGetFallbackFolder\microsoft.aspnetcore.mvc.razor.viewcompilation\2.1.0-rtm-30796\build\netstandard2.0\Microsoft.AspNetCore.Mvc.Razor.ViewCompilation-x64.exe", "AMD64". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project

    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:

    "windowsAuthentication": true,
"anonymousAuthentication": false,

  • NullReferenceException when using a custom IAuthorizationPolicyProvider and AllowCombiningAuthorizeFilters is set to true
    Using a custom IAuthorizationPolicyProvider and setting AllowCombiningAuthorizeFilters to true causes a NullReferenceException.
    Workaround: Disable AllowCombiningAuthorizeFilters or use a single AuthorizeFilter

  • XmlSerializerOutputFormatter throws InvalidCastException for async action methods
    Invoking an Async action method may result in an InvalidCastException when using the XmlSerializerOutputFormatter.
    Workaround: Wrap the return type in ActionResult<T>. Ex. replace the return type Task<IEnumerable<string>> with Task<ActionResult<IEnumerable<String>>>.

Configuration

📅 Schedule: Branch creation - "before 8am" in timezone Europe/London, Automerge - At any time (no schedule defined).

🚦 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.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@trusted-contributions-gcf trusted-contributions-gcf bot added kokoro:force-run Add this label to force Kokoro to re-run the tests. owlbot:run Add this label to trigger the Owlbot post processor. labels Oct 4, 2021
@google-cla google-cla bot added the cla: yes This human has signed the Contributor License Agreement. label Oct 4, 2021
@kokoro-team kokoro-team removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Oct 4, 2021
@renovate-bot renovate-bot changed the title chore(deps): update dependency microsoft.aspnetcore.all to v2.2.8 chore(deps): update dependency microsoft.aspnetcore.all to 2.2.8 Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@amanda-tarafa amanda-tarafa Awaiting requested review from amanda-tarafa amanda-tarafa is a code owner

@jskeet jskeet Awaiting requested review from jskeet jskeet is a code owner

At least 1 approving review is required to merge this pull request.

Assignees
No one assigned
Labels
cla: yes This human has signed the Contributor License Agreement. owlbot:run Add this label to trigger the Owlbot post processor.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@renovate-bot @kokoro-team