I apologize if you already received this but I tried "quick reply" and it looked like it did not submit anything so I am sending it again trough regular reply.

Below are the answers to your questions from the customers perspective:

1. Yes, VS 2019 version 16.5.4

2. When I start, the build is OK. I know this because I’ve set the logging level to ‘diagnostic’ and it spews out lots of data and at the end it says no errors or warnings. The next step is to kick off the debugger – this is where it hangs.

3. There is no UI form and Alt+Tab shows nothing.

4. I can’t do anything once it hangs. All the vs controls are unresponsive. I have to shutdown the development studio (devenv.exe) with task manager.


Additional information:

*when you start a program in VS19, you have 2 options. ‘Start Debugging’ and ‘Start without debugging’. When I choose the ‘Start without Debugging’ the program waited (sort of hanging) for a couple of minutes, then started. When I choose the ‘Start Debugging’ option, it hangs. Once it hangs, my only option is to kill devenv.


Please let me know if you do have any other ideas on how to troubleshoot this issue or if you have any questions. Thank you in advance.

Hello Z,

I am currently working with a customer that is experiencing a VS 2019 hang whenever he adds the easyUAClient .net control to his form and he tries to run in debug mode. The strange thing is the following:

*Customer is able to Compile, Run and debug the EasyUADemo project that it's included with the Data CLient toolkit
*I am not able to replicate the behavior on my end with his test applications nor my own test application. I tried to see if I could replicate the issue so I tested it using two virtual machines and my workstation and the toolkit worked as expected.
*It appears that the issue only occurs during debugging

I know there is not much to go with but I have exhausted all my ideas and I was wondering if you have seen this behavior before or if you have any other suggestions for me to look at.

The customer performed the test below:

from the customer:
1. If I start your EasyOPCUADemo test program, all works OK. If I keep your basic OPC controls and modify the program by adding SQL and other windows controls needed for our application, it works normal. Your demo program uses 3 OPC controls: uaDataDialog, uaHostandEndpointDialog, and easyUAClient.
2. Next, I build a new program from scratch, initially with no OPC controls, everything works normally. I just put Inputboxes when I needed OPC inputs.
3. Next, I verified that there were no OPC references in the Project. There were no references.
4. Next, I added the uaDataDialog control. I verified that references were added to the project. All were version 5.58.146.1. I made no code changes, I just added the uaDataDialog control.
5. I tested my program and it ran normally.
6. Next, I added the uaHostandEndpointDialog control to the Project, verified the references were still version 5.58.146.1. Again, no code changes. I tested the program and it ran normally.
7. Next, I added the UAClient cotrol and verified the references. Again, no code changes were made. I tried to run my program, and it hung, just as it had before.
8. The program works perfectly outside the development environment (VS19). The issue is when it tries to run in the debug mode. It builds and publishes with no errors or warnings.
9. I’ve updated VS19 and Windows 10 to the latest revs and still no improvement.


Environment:

Windows 10 - Up to date
VS2019 - Up to date
OPC Data Client 2020.2 - 5.58
.NET framework 4.7

Please let me know if you have any suggestions or any questions. Thank you in advance.