Can the extension start in a "Paused" state?

[rkhoury]

I have a potentially unique dev environment that means I have many solutions sharing the same large codebase, and starting multiple VS instances thrashes filesystem-related activity to produce the same multi-gigabyte database. I often limit one VS instance to be "active" to limit this redundancy, but it annoys me that I can't load VS with the extension "paused" by default and I have to quickly load the Code Search tab to manually pause.

What's required to get this extension paused by default? I get quite overwhelmed with the structure of everything that I'm not sure of exactly where this change should go.

And on a slightly separate note, I'm also really curious of how you efficiently navigate the codebase with all the interface abstractions? Are all these interfaces necessary when there's only one concrete class available? (I'm not a C# programmer so I could be missing something about best practices and such - I only know it makes click-navigation in the code really challenging).

Many thanks,
Richard.