ColumnĬount – The number of referenced Commerce assemblies that aren't part of the Commerce SDK.įailed – Extensions or their dependencies reference Commerce assemblies that aren't part of the Commerce SDK.Įxtension export tests validate types that are exported by extension assemblies. Results are shown only if the test fails. The following table summarizes the results that are the output of the unsupported dependencies test. The unsupported dependencies test validates whether the assemblies in an extension or their dependencies reference Commerce assemblies that aren't part of the Commerce software development kit (SDK). Succeeded – The target framework is supported.įailed – The target framework isn't supported or couldn't be retrieved. Not specified – The assembly isn't marked with TargetFrameworkAttribute, or the value is blank.Īssembly not found – The assembly file wasn't found.įailed to load assembly – The assembly failed to load, possibly because of incompatibility. Target framework name – The name of the target framework of the validated assemblies. Target framework (others) – This test validates all unused assemblies in the extension folders.Ĭount – The number of assemblies that have the same target framework (as specified by the target framework name in the Result Text column).Īssembly names – If is enabled, a comma-separated list of assembly names is shown. Target framework (dependencies) – This test validates assemblies that the extension depends on, both directly and indirectly. Target framework (extensions) – This test validates the top-level extension assemblies. The following table summarizes the results that are the output of the target framework tests. Target framework tests validate the target framework of the assemblies to ensure that it's supported. If you require that tests show assembly names in the results, you can implement the following app setting. Assembly tests don't validate System and Microsoft.Dynamics assemblies.īy default, the tests don't show assembly names in the results, to help preserve security. Finally, all unused assemblies in the extension folders are validated. Next, all dependent assemblies are validated recursively, until the whole dependency tree is traversed. The top-level assemblies of an extension are validated first. Assembly testsĪssembly tests validate assemblies in an extension to ensure that they meet current requirements. The rest of this article provides details about these categories and the tests that they include. The CSU extensions health check includes the following tests in two main categories: Replace CommerceScaleUnitURL with the URL of your CSU instance. The CSU extensions health check feature can be accessed by using the following URL format. Microsoft highly recommends that developers use the health check feature to ensure that their CSU extensions are compliant. This article explains how to use the Commerce Scale Unit (CSU) extensions health check feature in Microsoft Dynamics 365 Commerce.ĭevelopers who build CSU extensions can use the Commerce health check feature to run tests that are built into the framework and validate that their extensions meet current requirements.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |