Hi Dmitry and Paul,

Your wish is the VS teams command. Well, at least in this instance :-)

Introducing the IVsActivityLog (comments gleaned from the vsshell80.idl).

//--------------------------------------------------------------------------
-
// IVsActivityLog
//
// Implemented by the Environment.
// Used by parties that want to add events to the IDE Activity Log. This log
// is active when the shell receives the /log switch, or when an environment
// variable ("VSLogActivity") is set. The log is intended to record high
// level information for the purpose of quickly tracking down and routing
// problems. This is not a tracing tool, and only key events should be
logged.
// When logging is turned on, the implementation will log an event in
response
// to each method on this interface. When logging is not turned on, the
// implementation for each method is a fast no-op.
//--------------------------------------------------------------------------
-

If you add the /log command line switch to devenv.exe, there should be some
info on failed package and addin loading. It probably won't tell you
exactly what went wrong, but it may give you some hints.

I haven't seen this documented yet, aside from the obligatory place holders
in the beta docs,  but I'm thinking that a lot of package and addin
developers may want to consider utilizing this as a way to enable
diagnostics in their test runs, and possibly when their customers run into
problem in the field.

Cheers,
Ed Dore [MSFT]

This post is 'AS IS' with no warranties, and confers no rights.