Register assemblies for use in offline mode (equivalent to RetailServer controller but for local CommerceRuntime when the client is not connected) (Step # 7)

 7. Register assemblies for use in offline mode (equivalent to RetailServer controller but for local CommerceRuntime when the client is not connected)

    - This sample's Retail Server controller is written using the Microsoft.Dynamics.Commerce.Runtime.Hosting.Contracts, meaning the same controller assembly can be used by Retail Server and the offline runtime

    - Navigate to RetailSDK\Assets folder and open RetailProxy.MPOSOffline.ext.config

    - Under the composition section, register your new proxy library name. (The assembly generated after building your proxy project.

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

    - For manual testing, update the RetailProxy.MPOSOffline.ext.config under the C:\Program Files (x86)\Microsoft Dynamics 365\70\Retail Modern POS\ClientBroker\ext with the custom proxy library name under the composition section.

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

    - Navigate to RetailSDK\Assets folder and open CommerceRuntime.MPOSOffline.ext.config

    - Under the composition section, register your new CRT library name. (The assembly generated after building your proxy project.

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

    - For manual testing, update the CommerceRuntime.MPOSOffline.ext.config under the C:\Program Files (x86)\Microsoft Dynamics 365\70\Retail Modern POS\ClientBroker\ext with the custom proxy library name under the composition section.

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

    - add the proxy extension dll to customization.settings ---> <ISV_RetailProxy_CustomizableFile Include="$(SdkReferencesPath)\Contoso.RetailServer.StoreHoursSample.dll" />

Step 1.

 - This sample's Retail Server controller is written using the Microsoft.Dynamics.Commerce.Runtime.Hosting.Contracts,
meaning the same controller assembly can be used by Retail Server and the offline runtime

Step 2.

    - Navigate to RetailSDK\Assets folder and open RetailProxy.MPOSOffline.ext.config
    - Under the composition section, register your new proxy library name. (The assembly generated after building your proxy project.
 <add source="assembly" value="Contoso.RetailServer.StoreHoursSample" /> 

Path: K:\RetailSDK\Assets

Step 3.

- For manual testing, update the RetailProxy.MPOSOffline.ext.config under the C:\Program Files (x86)\Microsoft Dynamics 365\70\Retail Modern POS\ClientBroker\ext with the custom proxy library name under the composition section.

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

Path: K:\RetailSDK\Assets


Path: C:\Program Files (x86)\Microsoft Dynamics 365\70\Retail Modern POS\ClientBroker\ext


Step 4.

    - Navigate to RetailSDK\Assets folder and open CommerceRuntime.MPOSOffline.ext.config

Path: K:\RetailSDK\Assets\CommerceRuntime.MPOSOffline.Ext.config

Step 5.

    - Under the composition section, register your new CRT library name. (The assembly generated after building your proxy project.

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

Solution path: K:\RetailSDK\SampleExtensions\CommerceRuntime

Build the Project > Right on Project > take Properties.


Step 6.

- For manual testing, update the CommerceRuntime.MPOSOffline.ext.config under the C:\Program Files (x86)\Microsoft Dynamics 365\70\Retail Modern POS\ClientBroker\ext with the custom proxy library name under the composition section.

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

Source Path: K:\RetailSDK\Assets


Destination Path: C:\Program Files (x86)\Microsoft Dynamics 365\70\Retail Modern POS\ClientBroker\ext


Step 7.

     - add the proxy extension dll to customization.settings ---> 

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

Path: K:\RetailSDK\BuildTools  



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