After installing LLBLGen v5.1.0 trial, I found that VSIX extension installed is showing v5.0.0 instead of v5.1.0 in Visual Studio 2015. Opening "Extensions and Updates" from Visual Studio 2015 Tools menu, it shows that current version is 5.0 and it needs to update to 5.1.

You need to update setup of LLBLGen Pro v5.1 because there is no way to update only vsix extension of LLBLGen — neither from within Visual Studio 2015 nor from Visual Studio Marketplace.

Thanks.

The extension is the same for 5.0 and 5.1, hence the version '5.0'. What the extension does is look at a registry key (which is added/removed by the installer) where the designer is located and load that designer. It checks from 5.9 to 5.0 and loads the first designer key found, so always the latest version. If you look at the Help -> About dialog it will show v5.1. The VSIX is more of a wrapper around the designer, as for normal vsix extensions the actual extension has to be placed in the vsix extension folder itself, but as we also offer a standalone installer it would mean we either have to copy the files twice, or use some trick to make the vsix load the installer from the actual installation folder. Which is what we do

The problem is that if we want to version it, we need 2 extensions as building one on the same box for v5.0 and v5.1 doesn't work, or at least it gives a lot of problems (as the extension compiler also installs the one it compiles). As the functionality is exactly the same we keep it as-is.

Does this give problems for you?

OK, I got it. It is working perfectly fine for my evaluation project. No problems yet. Thank you for explaining the issue. I had gotten suspicious when Visual Studio notify me about the update available but I could not be able to update it to 5.1. Now it is clear.

ComputerJin wrote:

OK, I got it. It is working perfectly fine for my evaluation project. No problems yet. Thank you for explaining the issue. I had gotten suspicious when Visual Studio notify me about the update available but I could not be able to update it to 5.1. Now it is clear.

I admit it's not ideal. Let's hope MS has solved some VSIX mess in 2017 so this is more flexible