The strange case of no ext_ConnectMode.ext_cm_UISetup phase fired, not even once

Registry path clarification

vlad2135 — Mon, 16 Feb 2009 06:37:38 GMT

I've spent whole day trying to understand why CommandPreload value in "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\Addins\MyAddin.Connect" does not work.

There is another key defining wheither fire ext_cm_UISetup or not! And it's defined for every user on the system:

"HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0\PreloadAddinState"

Either delete value with your plugin name, or set it to 1, and you'll get your UISetup phase!

Visual Studio Links #78

Visual Studio Hacks — Thu, 16 Oct 2008 12:36:19 GMT

My latest in a series of the weekly, or more often, summary of interesting links I come across related to Visual Studio. Channel 9 Stuff: Anders Hejlsberg and Guy Steele- Concurrency and Language Design The Concurrency Runtime- Fine Grained Parallelism

re: The strange case of no ext_ConnectMode.ext_cm_UISetup phase fired, not even once

carlosq — Tue, 14 Oct 2008 20:55:55 GMT

Yes, you can add that XML tag in the .AddIn file without running the add-in wizard to create a new project, I'm sorry if I was not clear about that.

re: The strange case of no ext_ConnectMode.ext_cm_UISetup phase fired, not even once

Utkarsh — Tue, 14 Oct 2008 16:11:52 GMT

One question: Is it not same as specifying <CommandPreload>1</CommandPreload> in .AddIn file? I guess, even if you forget to check the check box, you can specify 1 here (in .AddIn file). I have not tested though.

Thanks.