Please consider the following scenario.
- Launch Windows Powershell ISE (64 bit)
- Create a new PowerShell Tab
Create a new PS script which loads a custom assembly by invoking [System.Reflection.Assembly]::LoadFrom
Create an instance of an object from your custom assembly by invoking the New-Object command
- Run the script and verify that an instance of your custom object was created.
- Close the PowerShell Tab. But, keep PowerShell ISE running. I would have expected PowerShell ISE to have completely unloaded the assembly.
However, the custom assembly is locked until PowerShell ISE is closed down completely.
I am developing a custom .NET library using Visual Studio .NET and PowerShell is a client application of this library. Since closing the Tab does not unlock the assembly, I have to close and re-start Powershell ISE every time I make a change in Visual Studio. This behaviour of PowerShell ISE is drastically slowing down my development time.
Is there a workaround to this issue?