Comments by InvisibleMedia (Top 3 by date)

Thanks for your comment. Is this problem remain unsolved ?

If so, there is a little information to know about compiling on the fly;
I explain it myself : depends to switches (Boolean values) in CompileParameters, if the compiled DLL is loaded immediately into the current execution, the DLL remains loaded until the executable quits. In Windows, you cannot easily unload a DLL.
To unload a DLL, there is a workaround : compiles and loads the DLL in a new AppDomain instance.

To do so, AppDomain.CreateDomain() is the main function to create a new domain. You need to create a new evidence and defines in it a new Zone; the zone computer is available; use this zone to address all security limits to the computer (other zones are intranet or internet). After the new domain is created, you can load your compilation process and loads the resulting the DLL. As you are finished, you can call the method Unload() associated with your AppDomain instance. And then, your DLL is then completely unloaded and delete can occur.
But, carefull : communications between two differents domains cannot be synchrone; it's asynchronous and you can transmit some information with and then by Marshalling. Methods in an AppDomain instance GetData() and SetData() are possible; but, in a limited manner, as such a Distributed COM marshal process.