We have a product based on VS 2010 SP1 Isolated Shell, and are currently migrated it to VS 2013 Isolated Shell.
We had to disable a lot of packages in the Vs2013 shell compare to the Vs2010 one. For example, in our pkgundef:
// Visual C# Project
System
[$RootKey$\Packages\{FAE04EC1-301F-11D3-BF4B-00C04F79EFBC}]
// Visual
C++ Package
[$RootKey$\Packages\{1B027A40-8F43-11D0-8D11-00A0C91BC942}]
// Visual
C++ Language Manager Package
[$RootKey$\Packages\{8C2EA640-ABC1-11D0-9D62-00C04FD9DFD9}]
// Text Management Package. Note: If uncomented, this make the output window unusable,
// but by leaving it commented it makes our appl crash when a breakpoint is hit on Vs BraceCompletion (???)
// [$RootKey$\Packages\{F5E7E720-1401-11d1-883B-0000F87579D2}]
// CssPackage
[$RootKey$\Packages\{5330c67f-305c-4b17-a3dc-fbb7aee69c09}]
Because we have some weird exception on package load. These tend to appear out of nowhere from random manipulation and show the usual error: "The 'CassPackage' did not load correctly".
We can't fill a Ms Connect thanks to the randomness of this issue, so any suggestion would be greatly appreciated.