Hello.

As I wrote earlier, resolving this will need extensive internal changes (and I am still not sure what else will get affected and how much work in other areas that will trigger). My plan was to include it with 2023.2 release, in November. I have checked the calendar and the other tasks I have, and unfortunately I cannot commit to an earlier date. If thing go very well, I can hope for end of October.

I am not aware of anything really important for our end users in Visual Studio versions past 17.4.0. And the VS installer makes it actually quite easy (though time consuming) to downgrade or upgrade VS versions. So while it is an ugly workaround, the suggestion to use VS 17.4.0 (be it just for using the components from the toolbox) still holds, until we have a true resolution. AFAIK, everything else works in newer versions of VS. So in fact, one can e.g. use VS 17.4.0 on one computer just to drag components from the toolbox - and use newer VS on a second computer for everything else.

Best regards

Hello.

I have investigated deeper. Unfortunately, it seems that in newer Visual Studio builds, Microsoft has made a "slight" change, with profound consequences to us.
I tried some simpler approaches to fix it, but failed. I think I know the proper way to address the problem, but it is going to be demanding and extensive change (it involves splitting the product assemblies), so it cannot be done as a "patch" to an existing version. I will work on it for version 2023.2.

Unfortunately, this means that for users who want to use the QuickOPC items from Visual Studio toolbox with version 2023.1, they have to stay with Visual Studio 17.4.0 or so. I know this is not good, but we could not anticipate the Microsoft change (which is even documented by them as "breaking change" for non-Windows platforms, but they have not realized it might affect Windows projects including Visual Studio extensions as well).

Note that as far as I know, in the runtime (and even in the VS designer, when the components are already there on the form), everything works fine. The only problem is that the items are missing from the toolbox. The components can still be used.

Best regards

Hello.

I could not reproduce the problem with Visual Studio 17.4.0, which is what was used at the time of release.
After upgrading to Visual Studio 17.6.4, I was able to reproduce it.

This will take some time to investigate. I will post here when I have some news.

Regards

Hello.

1. Did the customer run the full installer (Setup), or is just referencing the NuGet packages? (the installer must be used).
2. Please obtain the full Visual Studio version (something like 17.x.y) - from Help -> About.
3. When he does in Visual Studio: Extensions -> Manage Extensions, Installed - is QuickOPC extension listed there?
4. Which .NET runtime is he targeting? (from the Project properties page).

Thanks