Nope. Once an assembly is loaded you cannot unload it again (unless you use custom AppDomain loading which is a bit more complicated).

Easiest way to do this if you're working on a .NET component is to start the VFP app from the .NET project using the debug settings. That way anytime you compile the Fox app is shut down and restarted when you start debugging again.


+++ Rick ---


>>>
>>>I am not sure why did it try to load the c:\dev version of the dll as I put this in the call:
>>>

>>>if loBridge.LoadAssembly("C:\_Siriusware\Main\Siriusware.Library\Siriusware.Library\bin\Debug\Siriusware.Library.dll")

>>>
>>>e.g. I specified the exact path to the dll (although I also had the dll in the application directory from where I was testing it).
>>>
>>>I am going to re-start VFP to be sure.
>>>
>>>UPDATE. Could not make it to work. VS does not stop on the breakpoints.
>>
>>A few things you can try - don't attach VS to VFP until after you've loaded the assembly. Also do a full rebuild on the debug version to make sure the debug symbols are in sync - from the messages it's not loading the PDB and without those your breakpoints won't be hit.
>
>I noticed another problem. If I run code that created the bridge and loaded the assembly, then I am unable to re-build it until I close VFP. Is there another way to release it?
>
>Thanks.