title: What will happen to the Microsoft.AspNetCore.* namespace in ASP.NET 5.0?
body: <p><a href="https://devblogs.microsoft.com/dotnet/introducing-net-5/" rel="nofollow noreferrer">.NET 5.0</a> will replace .NET Core 3.x when it is released in November—and, thus, <a href="https://devblogs.microsoft.com/aspnet/asp-net-core-updates-in-net-5-preview-8/" rel="nofollow noreferrer">ASP.NET 5.0</a> will replace ASP.NET Core 3.x.</p>
  <blockquote>
  <p><strong><em>Edit:</em></strong> This question is based on a fundamentally incorrect assumption. While the next version of .NET Core will, in fact, be .NET 5.0, the next version of ASP.NET Core will be ASP.NET Core 5.0. See the answers from <a href="https://stackoverflow.com/a/63745817/3025856">@Camilo-Terevinto</a> and <a href="https://stackoverflow.com/a/63746519/3025856">@omajid</a> for details.</p>
  </blockquote>
  <p>Despite this, as of <a href="https://devblogs.microsoft.com/dotnet/announcing-net-5-0-preview-8/" rel="nofollow noreferrer">Preview 8</a> (8.20414.8), packages, assemblies, and namespaces still contain <code>AspNetCore</code> in their names. For example, see the following NuGet packages:</p>
  <ul>
  <li><a href="https://www.nuget.org/packages/Microsoft.AspNetCore.Http.Features/5.0.0-preview.8.20414.8" rel="nofollow noreferrer"><code>Microsoft.AspNetCore.Http.Features</code></a></li>
  <li><a href="https://www.nuget.org/packages/Microsoft.AspNetCore.Authorization/5.0.0-preview.8.20414.8" rel="nofollow noreferrer"><code>Microsoft.AspNetCore.Authorization</code></a></li>
  <li><a href="https://www.nuget.org/packages/Microsoft.AspNetCore.DataProtection/5.0.0-preview.8.20414.8" rel="nofollow noreferrer"><code>Microsoft.AspNetCore.DataProtection</code></a></li>
  <li><a href="https://www.nuget.org/packages/Microsoft.AspNetCore.Razor.Language/5.0.0-preview.8.20414.8" rel="nofollow noreferrer"><code>Microsoft.AspNetCore.Razor.Language</code></a></li>
  </ul>
  <p>If you go to the documentation for e.g. the <a href="https://docs.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.http.features?view=aspnetcore-3.1&amp;viewFallbackFrom=aspnetcore-5.0" rel="nofollow noreferrer"><code>Microsoft.AspNetCore.Http.Features</code> namespace</a> on docs.microsoft.com, however, you'll be redirected back to the ASP.NET Core 3.1 documentation with the warning:</p>
  <blockquote>
  <p>The requested page is not available for ASP.NET Core 5.0 Preview. You have been redirected to the newest product version this page is available for.</p>
  </blockquote>
  <p><strong><em>Question:</em></strong> <em>Do we have any evidence of what these packages, assemblies, and namespaces will be named in the .NET 5.0 release?</em> Will they remain <code>Microsoft.AspNetCore</code> for backward compatibility, as the current <em>namespaces</em> suggest? Will they become <code>Microsoft.AspNet</code> for consistency with the product name, as the <em>documentation</em> suggests? Or does this remain TBD?</p>
  <hr />
  <p><em>Background:</em> Like other developers, I am working on the .NET 5.0 version of an open source library, and we aim to follow the same naming conventions as the underlying framework for the sake of familiarity, discovery, and consistency.</p>