Hi,
I have recently ported a VS2012 integration package to VS2013. Some GUIDs were regenerated, .rgs files updated appropriately and some minimal code changes were made. Basically same stuff that I did to port 2010 to 2012 some time ago. However, unlike 2012 package, the new 2013 package refuses to load. From what I can see in the registry, the package got installed OK. I can see the package GUID in
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\12.0\Packages
and in
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\12.0_Config\Packages
The Package Control GUID and Tool Window GUID are registered. Menus and InstalledProducts entries of the VS2013 registry are also OK.
When I start VS2013 shell, I can see my package menu. However, when I select any menu option, the package doesn't load. What is more interesting, under a debugger I can see that VS2013 shell retrieves my package GUID when it enumerates the registered package entries, but there are no references to it when I click the menu. VS2012 finds the appropriate GUID during the enumeration and then reads it when I click the menu. VS2013 ignores the installed package completely.
In older days, I would blame it on PLK, but VS shells after 2010 do not use PLK, so I am not sure what is going on. On top of that, VS2013 doesn't generate any errors or log entries neither during the package installation nor at runtime.
My question is: Are there some diagnostic tools or options that would check my package and tell me if there is something wrong with it. Unless the package gets loaded I do not have much debugging options - the trace is lost in the VS code.
My comment is: VS Developers, please be more expressive when it comes to error logging and reporting. I am sure your code had reasons not to load my package, but telling me about these reasons one way or another would really help.
Best regards and thank you in advance.
Victor.