How to load/unload DLLs in Powershell ?

[Logan.M]

I created a new DLL on my own but when I use [System.Reflection.Assembly]::LoadFile("filename.dll"), everything locks on the DLL file and I had to quit PowerShell to get to normal. This is quiet annoying. So I want a way to just avoid this situation.

Is there anyone who succeeded doing so in PowerShell?

[sergioKomic]

In general, you don't load DLL but instead you load assemblies. Once loaded they can't be unloaded until the life of the application. If you truly want to unload DLLs then you need to do heavy lifting yourself. After you are done with the DLL use FreeLibrary to unload the DLL.

[Archibald]

You may create the new AppDomain, load assembly into it and continue performing your operations. Once you have completed your work, you may unload the AppDomain and move further. But always remember that the assembly can be unloaded only with the parent AppDomain. You couldn't unload single assembly from the AppDomain.

Refer http://msdn.microsoft.com/en-us/libr...appdomain.aspx for further details on AppDomain Class

[arturro]

You can't just unload a dll externally though. You would have to ask a process to do it, which means said software has some way to successfully process such a request either through message or some sort of configuration read on start up.

If I wrote a piece of software that used a dll, I can load it implicitly or explicitly. Usually implicit loads are for mandatory dlls, explicit for optional ones. If I'm loading a dll that means it's in my memory space and therefore should be inviolate, only the software that loaded it can unload it, it's the owner.

[Grohu]

1. Go to Start - Run and type regedit
   
2. Navigate to the following key:
   HKEY_LOCAL_MACHINE - Software - Microsoft - Windows - CurrentVersion - Explorer - AlwaysUnloadDLL
   

   Note: If you do not have one then create a new sub-key named 'AlwaysUnloadDLL'

3. Click on it and set the default value to '1'.
   
4. Click OK and restart your computer