CODEWITHSUNDEEP
visual-studio-2013visual-studio-extensions
Number8
Number8

Reputation: 12870

Converting Visual Studio Add-in to Extension package

I have an Add-in that runs in VisStudio 2012 and VisStudio 2013.
It does not have any UI; it monitors and responds to focus events.

When I converted the add-in to an Extension package (starting with the template provided by the VS2013 SDK), it works as expected when I have a menu item.
However, until the menu command is used, the package doesn't seem to get fully initialized.

How can I force the full initialization of the extension package when is has no UI?

Upvotes: 0

Views: 513

Answers (1)

Jason Malinowski
Jason Malinowski

Reputation: 18976

So if you truely need to be done on first load, then the proper way to do it is to register your package as an AutoLoad package like is documented here. There are a number of "contexts" you register for, so you can register for "solution exists" and "no solution" if you need it always.

Upvotes: 1

Related Questions