We are making use of a 3rd party for our credit card processing.
We used to install MPOS but now that Microsoft got the printers working in CPOS, we are switching to CPOS.
This specific 3rd party is using Microsoft.Dynamics.Commerce.Hardwarestation.Peripherals.PaymentDeviceAdapter.
Now all the standard code in the RetailSDK has the above commented out and use Microsoft.Dynamics.Commerce.Hardwarestation.Peripherals.Legacy.PaymentDeviceAdapter.
For MPOS I had to comment out the Peripherals.Legacy.PaymentDeviceAdapter entry and uncomment the Peripherals.PaymentDeviceAdapter file
in the following file: DLLHost.exe. this is in RetailSDK\Assets.
I also had to add some custom to other files like RetailSdk\Assets\HardwareStation.Dedicated and Hardwarestation.Shared. also in "RetailSDK\Packages\HardwareStation.Sdk\Sdk.HardwareStationSetup.csproj"
All the above are in directories like RetailSdk\Assets and RetailSdk\Packages.
And when building a retail deployable package it put the change in DLLHost.exe in the self service package for hardwarestations I assume because we never had problems.
For CPOS however for it to include the change in the hardwarestation self service executable to use the Peripherals.PaymentDeviceAdapter file instead of the Legacy version, the 3rd-party support team indicated that I have to do the same commenting out / uncommenting that I did in the DLLHost.exe, to the following file so that it will use Peripherals.PaymentDeviceAdapter instead of the Legacy one when building the hardwareStation self service executable.
For v10.0.15:
RetailSDK\References\Microsoft.Dynamics.Retail.HardwareStation.WebHost\9.25.21042.3\Pkg\bin\Web.config
For v10.0.17:
RetailSDK\References\Microsoft.Dynamics.Retail.HardwareStation.WebHost\9.27.21090.7\Pkg\Web.config
My problem with this is that the above file is inside a version number directory. so every time I upgrade my development box and thus also upgrade the RetailSDK, that directory number will change and thus the file will not exist anymore.
So is this the correct file to change and if so, will the retail deployable package build of the hardwarestation self-service still work if I put a copy of this file directly in RetailSdk\Reference? Will it pick it up from this location instead?
If I can do it like this, then I can at least check it into source control and when I do upgrade my RetailSDK just compare with the latest version to see if anything changed in the file and add the change.
This way at least I will always have the custom that goes with the 3rd party in source control and not forget to fix the file after every upgrade which will wipe it in its current location.
The 3rd-party custom includes a change Microsoft.Dynamics.Commerce.Runtime.TransactionService.dll and I have to put it directly under RetailSDK\Reference.
The standard file I found for v10.0.17 under "RetailSDK\References\microsoft.dynamics.commerce.runtime.transactionservice\9.27.21089.20\lib\net461\Microsoft.Dynamics.Commerce.Runtime.TransactionService.dll".
So I assume if it works for this file it should work for the Web.Config file for the Microsoft.Dynamics.Retail.HardwareStation.WebHost, or will it not?