Hello.

I think I found the problem. It is due to an undocumented quirk in Visual Studio designer (for record: it only loads project-specific assemblies from the main thread).
I made a workaround that should fix it. It is in version 5.80.255 and newer. This is now on our company Web site, and on NuGet; and I will send you a link for the branded installer.

Best regards

Hello.

please bear with, I need to test on more computers.

Regards

Hello.

I will try to . However, since it does not quite depend on what *we* do, but rather on what Visual Studio internally does, it might be impossible to resolve.

Best regards

Hello.
Given that there is this workaround, which is not that bad, and that finding the real cause would be really difficult, can we agree to leaving it is as it is for now?>

Regards

Thank you.

I was finally able to reproduce the issue, on a different computer (with the precise Visual Studio version). But, it behaves weirdly. I only get the problem sometimes. There are limited ways to debug this inside Visual Studio; so far I could not make sense of it.

However, what I noticed is that this only ever happens to me on a new project, where the QuickOPC packages have just been introduced. I can "resolve" the issue by closing the Visual Studio, starting it again, and reopening the solution. It always worked for me then.

Can you/your customer try this too?

Regards