For example: Ī project that includes Tag Helpers should use the SDK.
The package moved into the shared framework in ASP.NET Core 3.0 and is therefore no longer published. NET Standard instead, a package reference is required. Run the following command in the integrated terminal (VS Code) or a command shell (.NET CLI): dotnet new razorclasslib -s The template's Support pages and views checkbox should be selected. Use the Razor Class Library project template. Use the following instructions for your editor. The Razor Class Library project template satisfies the preceding requirements for projects targeting. An AddRazorSupportForMvc MSBuild property set to true.Razor views or Razor PagesĪ project that includes Razor views or Razor Pages must use the SDK. For guidance on supporting multiple ASP.NET Core versions, see Support multiple ASP.NET Core versions.
This section doesn't discuss multi-targeting to support multiple versions of MVC. This section outlines recommendations for libraries that include: Only provide a framework reference to ASP.NET Core in the library's project file in addition to any other required MS Build properties: įor more information on libraries containing Razor components, see Consume ASP.NET Core Razor components from a Razor class library (RCL). Specify that the library supports pages and views when the library is created with the Support pages and views checkbox (Visual Studio) or the -s|-support-pages-and-views option with the dotnet new command: dotnet new razorclasslib -s If the class library only requires server-side-specific features, such as access to CircuitHandler or .ProtectedBrowserStorage, or uses ASP.NET Core-specific features, such as middleware, MVC controllers, or Razor Pages, use one of the following approaches: Only support server-side consumptionĬlass libraries are rarely built to only support server-side apps. Provide a semicolon-separated list of Target Framework Monikers (TFMs) in the TargetFrameworks MSBuild property: placeholder represents the semicolon-separated TFMs list. If the library must support features added to Blazor in the current release while also supporting one or more earlier releases, multi-target the library.
Net sdk how to#
For more information, see How to select a version tag of ASP.NET Core source code (dotnet/AspNetCore.Docs #26205). To select a tag for a specific release, use the Switch branches or tags dropdown list. NET reference source usually load the repository's default branch, which represents the current development for the next release of. To support Razor component consumption by server-side and client-side apps from a single library, use the following instructions for your editor.ĭocumentation links to.
To support Razor components in a class library, the class library must use the SDK. To reference ASP.NET Core, add the following element to your project file: īlazor supports creating Razor components class libraries for server-side and client-side apps. Projects using the or SDK must reference ASP.NET Core to use ASP.NET Core APIs in the shared framework. NET Core 3.0, projects using the MSBuild SDK implicitly reference the shared framework. For a list of packages no longer being published, see Remove obsolete package references.Īs of. Instead, the assemblies are included in the shared framework, which is installed with the. NET Core 3.0, many ASP.NET Core assemblies are no longer published to NuGet as packages. Compatibility testing of libraries can be conducted as framework features are being developed.
0 kommentar(er)
