Sündmused
31. märts, 23 - 2. apr, 23
Microsoft Fabrici, Power BI, SQL-i ja TEI kogukonna juhitud üritus. 31. märts kuni 2. aprill 2025.
Registreeruge juba tänaSeda brauserit enam ei toetata.
Uusimate funktsioonide, turbevärskenduste ja tehnilise toe kasutamiseks võtke kasutusele Microsoft Edge.
This article provides an introduction to Commerce Scale Unit (CSU) Core in Microsoft Dynamics 365 Commerce.
CSU Core is the next-generation, high-performance platform that Dynamics 365 Commerce offers to host the headless commerce engine. CSU Core provides the same functionality as the existing CSU, but it's highly optimized and performant because it uses ASP.NET Core and .NET Core.
CSU Core is built by using ASP.NET Core, which is a cross-platform, high-performance framework.
CSU Core provides the following benefits:
CSU Core is available for new deployments as of the Dynamics 365 Commerce version 10.0.22 release. As of the Commerce version 10.0.22 release, all new deployments use it by default. On-premises or CSU self-hosted installers use the same CSU Core platform that is built by using ASP.NET core and that runs on .NET Core.
CSU Core offers highly performant headless commerce APIs and the benefits of .NET Core.
Hoiatus
Using or relying on outbound Internet Protocol (IP) addresses for cloud-hosted CSUs isn't supported. IP addresses can change at any time and shouldn't be used as a stable identifier of network traffic. Dependence on any IP value for cloud-hosted CSUs might negatively impact your environment.
The following instructions describe how to switch an existing CSU deployment from the legacy .NET Framework to .NET Core.
Oluline
You can only migrate to CSU Core if your extensions are compatible with the Commerce SDK, or .NET Standard 2.0/.NET 6.
To migrate your existing Microsoft-hosted CSU to CSU Core, follow these steps.
Märkus
If you plan to create extensions for headless commerce, it must be built by using .NET Standard 2.0 as the target framework.
You can validate that your extensions are compatible with CSU core by running an extension test. To run a test, append the query parameter healthcheck?testname=extensions
to your Retail Server URL, as shown in the following example that uses <MyRetailServerURL> to represent the Retail Server URL.
https://<MyRetailServerURL>/healthcheck?testname=extensions
The test results contain a table that shows the status of compatible and incompatible extensions.
Extension component | Extension project target framework | Commerce SDK |
---|---|---|
Headless commerce APIs | .NET Standard 2.0 | Version 10.0.23 or later |
Commerce runtime (CRT) | .NET Standard 2.0 | Version 10.0.23 or later |
To run in CSU Core, extensions that were built by using the Retail SDK must be built using .NET Standard 2.0 as the target framework. The CSU Core runtime is built by using the ASP.NET Core and .NET Core. Therefore, extensions that were created by using the legacy .NET framework and Retail SDK packages don't run in CSU Core. If you're using the Retail SDK, Microsoft highly recommends that you Migrate the Retail SDK extensions to Commerce SDK. Commerce SDK supports CSU core out of the box.
Sündmused
31. märts, 23 - 2. apr, 23
Microsoft Fabrici, Power BI, SQL-i ja TEI kogukonna juhitud üritus. 31. märts kuni 2. aprill 2025.
Registreeruge juba täna