aspnetcore/includes/not-latest-version.md
:::moniker range="< aspnetcore-10.0"
[!NOTE] This isn't the latest version of this article. For the current release, see the .NET 10 version of this article. :::moniker-end
:::moniker range="= aspnetcore-7.0 || = aspnetcore-5.0 || = aspnetcore-3.0 || = aspnetcore-3.1 || = aspnetcore-2.0" [!INCLUDE] :::moniker-end
<!-- Exclude until .NET 11 preview is added to the version selector collection (add triple colon here) moniker range="> aspnetcore-10.0" > [!IMPORTANT] > This information relates to a pre-release product that may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here. > > For the current release, see the [.NET 10 version of this article](?view=aspnetcore-10.0&preserve-view=true). (add triple colon here) moniker-end --> <!-- Include either this file or 'not-latest-version-without-not-supported-content.md' at the top of articles. 'not-latest-version.md' (this file): Includes not-supported content. 'not-latest-version-without-not-supported-content.md': Doesn't include not-supported content. Use this file in articles that target >=7.0. For articles that target >=8.0 prior to 10.0 reaching EOL, 'not-latest-version-without-not-supported-content.md' must be used to avoid a zone/file moniker range mismatch error. When a new version is released, it might be necessary to temporarily comment out the current version moniker range section until the new moniker is created. Markdown to include this file: [!INCLUDE[](~/includes/not-latest-version.md)] -->