Enable and test Retail Server sample code (Step # 6)

 Step # 6

Enable and test Retail Server sample code:

    - Open the project at RetailSdk\SampleExtensions\RetailServer\Extensions.StoreHoursSample\RetailServer.Extensions.StoreHoursSample.csproj and compile it.

    - Use inetmgr to find the location of the local Retail Server folder.

    - Register the new Retail Server assembly in web.config file under <extensionComposition> (Note: If there is an assembly registered from a previous sample, then remove it.): 

        <add source="assembly" value="Contoso.RetailServer.StoreHoursSample" />

    - Register the new Retail Server assembly in RetailSdk\BuildTools\customization.settings:

        <ISV_RetailServer_CustomizableFile Include="$(SdkReferencesPath)\Contoso.RetailServer.StoreHoursSample.dll" />

    - Copy the changes you made to RetailSdk\Assets\commerceruntime.ext.config to the local Retail Server's commerceruntime.ext.config in its bin\ext folder.

          <add source="assembly" value="Contoso.Commerce.Runtime.StoreHoursSample" />

    - Drop both the new CRT and Retail Server assemblies into the local Retail Server bin\ext\ folder. Alternatively, use the Retail SDK's AfterBuildDropBinariesToRetailServer target for rapid development (Note: If you use the AfterBuildDropBinariesToRetailServer target, then you have to rebuild the 2 assemblies at least once in order to binplace them automatically).

    - Use inetmgr to browse to the Retail Server's $metadata and verify that the StoreHours entity is exposed (i.e. open https://usnconeboxax1ret.cloud.onebox.dynamics.com/Commerce/$metadata and search for "StoreHours" in the XML).


Step 1. 

 - Open the project at 
RetailSdk\SampleExtensions\RetailServer\Extensions.StoreHoursSample\RetailServer.Extensions.StoreHoursSample.csproj and compile it.

Step 2.
- Use inetmgr to find the location of the local Retail Server folder.

Search IIS in PC Go to Sites > RetailServer > Explore


Step 3.

 - Register the new Retail Server assembly in web.config file under <extensionComposition> (Note: If there is an assembly registered from a previous sample, then remove it.): 

        <add source="assembly" value="Contoso.RetailServer.StoreHoursSample" />

Step 4.
 - Register the new Retail Server assembly in RetailSdk\BuildTools\customization.settings:
        <ISV_RetailServer_CustomizableFile Include="$(SdkReferencesPath)\Contoso.RetailServer.StoreHoursSample.dll" />


Step 5.
 - Copy the changes you made to RetailSdk\Assets\commerceruntime.ext.config to the local Retail Server's commerceruntime.ext.config in its bin\ext folder.
          <add source="assembly" value="Contoso.Commerce.Runtime.StoreHoursSample" />


Step 6.
- Drop both the new CRT and Retail Server assemblies into the local Retail Server bin\ext\ folder. Alternatively, use the Retail SDK's AfterBuildDropBinariesToRetailServer target for rapid development (Note: If you use the AfterBuildDropBinariesToRetailServer target, then you have to rebuild the 2 assemblies at least once in order to bin place them automatically).

solution:
    You have to go to the Project root folder copy CRT and Retail Server DLLs and paste them into the Retail server.
 
Steps 1.
    Right-click on the project and go to the Open folder in File Explorer.

Path: K:\RetailSDK\SampleExtensions\RetailServer\Extensions.StoreHoursSample\bin\Debug\netstandard2.0




copy Contoso.Commerce.Runtime.StoreHoursSample.dll and Contoso.RetailServer.StoreHoursSample
and drop both in Retail server.
Path: K:\RetailServer\WebRoot\bin\Ext




Step 7.
    - Use inetmgr to browse to the Retail Server's $metadata and verify that the StoreHours entity is exposed (i.e. open https://usnconeboxax1ret.cloud.onebox.dynamics.com/Commerce/$metadata and search for "Store hours" in the XML).

url: https://demo-envd4a8206ce8b671d0ret.axcloud.dynamics.com/Commerce/$metadata


Comments

Post a Comment

Popular posts from this blog

Update Deployment Failed due to Missing MpProvider Module

 While upgrading a Tier-1 development environment, the deployment failed with the following error: The specified module 'C:\Program Files\Microsoft Security Client\MpProvider' was not loaded because no valid module file was found in any module directory. Cause: This error indicates that Visual Studio cannot locate the MpProvider module, which may be due to outdated or incomplete installations of Visual Studio. Resolution: Upgrade both Visual Studio 2019 and Visual Studio 2022 to their latest versions. This ensures all required modules are installed correctly. 🔧 Steps to Upgrade Visual Studio For Visual Studio 2019: Open Visual Studio Installer from the Start menu. Locate the Visual Studio 2019 entry. Click Update (if available). Follow the installation prompts. Restart your machine after installation. Launch Visual Studio 2019 to confirm the error is resolved. For Visual Studio 2022: Open Visual Studio Installer . Locate the Visual S...
Read more

How to Resolve DVT Script Issues When Applying Quality Updates in LCS for D365FO

Image
 Recently, while applying Quality updates 39, I encountered an error stating  " DVT script for service mode: AOSService on machine. " Upon examining the error logs, I found the description: "ERROR: System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel." After some research, I discovered a solution: First: Abort the current process in the Lifecycle Services (LCS) as this option is only available for environments in the Deployed state.  Second: Then, navigate to the Environment details page, click Maintain, and select Rotate secrets. Choose Rotate the SSL certificates and confirm the action.  This simple solution resolved my problem.
Read more

how to connect Just in time DB in D365F&O / Connect UAT Database with Dev machine in D365 F&O

Image
 Connect UAT with the Dev Environment Step 1: Go to LCS and select your UAT/ Tier 2 Environment  Path: Click on your Project Name from the Top of the LCS screen. Select your Environment full detail page Step 2: you should have to enable access for you VM to connect UAT DB. Click on Maintain -> Enable access Now Modify firewall rules form is open. Click on Plus button to add your VM ip address. Now go to your VM and find your ip address by just checking on chrome with "what is my ip" put your ipv4 ip address in the last open form " Add an Inbound Allow rule " in LCS put anything in the Name field and select Confirm. Now, you will get a popup from LCS. Step 3: Go to Database accounts table  field : Reason for access select Performance tuning for AX (Write to AX) field : Details put any comment Click on Request Access Refresh your page and you can see the DB detail on the " DATABASE ACCOUNTS" Tab copy all 4 keys to any notepad++ for clear readability. How...
Read more