Daylor,
Once an Assembly (DLL) is loaded in an AppDomain, the Assembly is loaded in
that AppDomain.
I understand that you need to create a new AppDomain which you load the
Assembly in, then when you are done delete the new AppDomain. At least this
is the way I understand that NUnit does it. Unfortunately I do not have a
sample of how to do this.
Also I believe you can use the AppDomain.ShadowCopyFiles to cause a copy of
the Assembly to be loaded. At least this is the way I understand that
ASP.NET does it. Again I do not have a sample.
I believe the ShadowCopyFiles may be the easier method.
Hope this helps
Jay
"Daylor" <Da****@012.net.il> wrote in message
news:3f********@news.012.net.il...
hi.
im creating object from assembly dll.
after im finish using the object ,
the process is still using the assembly dll.
what i need to do to the object , so the process will not use the dll ,
and by that , i could compile the dll again (after changing code, while the
win app process is still running ..)
hope im clear.
have a nice day.