-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hardware Station extension with IController fails to ping #91
Comments
Seems like the assembly Microsoft.CodeAnalysis could not be loaded, can you check if it is present in the Hardware Station's web site and if so what exactly version of the assembly is deployed in your environment? If the assembly is not there - can you manually place it there and see if the issue will go away? |
Yes, that worked. Am I doing something wrong with my extension, or is this something that needs to be addressed on Microsoft's side in the sealed HWS? I will assume for the time being that integrators will, at least for the time being, need to manually copy these files. I am working on a OneBox VM downloaded from LCS and after copying both...
...to the sealed HWS' ...\Webroot\bin directory I was able to ping with a custom device extension installed and referenced. I was also able to copy from the .NET Framework directory and successfully ping the HWS.
I also tried adding CodeAnalysis to my HWS extension project via nuget, and then removed it. Using the downloaded files also worked.
|
>... Am I doing something wrong with my extension, or is this something that needs to be addressed on Microsoft's side in the sealed HWS? ... @rphillips-newestech that is the bug, while it is still not fixed please keep copying the DLLs manually. |
Hi, thank you for reporting this issue. We have fixed the issue in hardware station build 9.35.22042.19. Please uptake that version or later to apply the fix. |
Thank you! |
Adding a custom device, IController, to the HWS sample causes the installed HWS to no longer ping.
The vanilla HWS sample works fine. As soon as I add to or replace the payment device, INamedRequestHandler, with a custom device and redeploy the ping fails. I have tried several permutations with the payment device and custom device, but always as soon as I reference the custom device in the extensions config the ping fails.
I am building my extension using the release/9.33 branch and installing over the base "10.0.23 - Hardware Station (SEALED)" package that was created in LCS on 12/17/2021.
Basic custom device
Event viewer warning
The text was updated successfully, but these errors were encountered: