During the original implementation of the PowerShell commands, I thought it necessary to have two AppDomains -- one for heavy processing of the VS object model and another for executing the user's code in a way that did not load their assembly into the main VS AppDomain.
I've recently learned a few things about NuGet and PowerShell that may enable us to get rid of the first AppDomain.
* The Get-Interface cmdlet lets you properly cast COM objects
* ScriptBlocks can be used as delegates
I've recently learned a few things about NuGet and PowerShell that may enable us to get rid of the first AppDomain.
* The Get-Interface cmdlet lets you properly cast COM objects
* ScriptBlocks can be used as delegates