Visual Studio 2019 doesn't allow synchronous addins anymore (no idea why, since some tools are so tiny, that it's way faster to execute what they do than to launch the async initialization process, but hey... who am I to talk about this? ... they're the "experts").
So, that's why I tried to convert our tools from sync to async... those addins are written in C++ and work in VS 2017 (sync) ... but when I modify them to load async, the system seems not to find or not to process the VSCT resources (or the resources that have been built by compiling the VSCT file).
The question is why. What process is involved here? I called IVsShell::LoadUILibrary in the IVsPackage::SetSite implementation to load the localized resources. Now in the async world I tried to do this in the
IAsyncLoadablePackageInitialize::Initialize implementation (or, in the task that I'm starting in this function). This doesn't work. That's why I went back and did it again in the IVsPackage::SetSite implementation (which is still called even for async modules... who knows why and what we should do there or return or... well, let's say it like this "the documentation is very detailed in this point"). ... but this still doesn't work.
So, here's the question: What do I have to do/provide that Visual Studio 2017/19/22 is loading and processing the VSCT resources in an async extension?