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.

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

ASP.NET Core 2.2.0 Preview 3 known issues #323

Eilon opened this Issue Oct 17, 2018 · 0 comments


None yet
1 participant

Eilon commented Oct 17, 2018

Known issues in ASP.NET / Entity Framework Core 2.2 Preview 3

To see all issues closed in the 2.2.0 Preview 3 milestone, see the results of this query.

Official announcement blog post:

Please see below for a list of known issues in the 2.2.0 Preview 3 release.

Some external CSS styles are failing to load for new Razor and MVC projects:

When running a newly created MVC or Razor Pages project, some styles do not render.

This is caused by an integrity check failure for some of the referenced stylesheets. To fix the issue add a crossorigin="anonymous" attribute to the bootstrap.min.css referencing <link ...> tag in the _Layout.cshtml file, as follows:

<link rel="stylesheet" href="" 
	asp-fallback-test-class="sr-only" asp-fallback-test-property="position" asp-fallback-test-value="absolute" 

URL generation for conventional routes with default values is invalid

In an MVC project using Endpoint Routing, URL generation using IUrlHelper can generate a URL incorrectly when the route template includes default values.


app.UseMvc(routes =>
    routes.MapRoute("default", "{controller=Home}/{action=Index}/{id?}");
Url.Action("Index", "Home", new { id = 17 });

This can result in the following URL being generated /?id=17 - this will work with most uses of MVC but the result of /Home/Index/17 is intended.

NullReferenceException thrown when using IHttpClientFactory

Crashes can occur due to a bug in how cleanup timers are incorrectly started when using IHttpClientFactory. This can be worked around by setting HttpClientFactoryOptions.HandlerLifetime to an extremely long value or Timeout.InfiniteTimespan.


For discussions, please go to aspnet/AspNetCore#3642

@aspnet aspnet locked and limited conversation to collaborators Oct 17, 2018

@Eilon Eilon added the 2.2.0 label Oct 17, 2018

@Eilon Eilon added this to the 2.2.0-preview3 milestone Oct 17, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.