It is because Assembly.Load is run on the file (the assembly gets loaded
into your appdomain).
You can see this in the Path setter it uses
set
{
if (value == null)
{
this.assembly = null;
}
this.assembly = Assembly.LoadFrom(value);
}
This will hold a lock on the file until the appdomain is killed.
No way to work around this I'm afraid except to wait until the appdomain is
dead to delete the file.
Cheers,
Greg Young
MVP - C#
http://codebetter.com/blogs/gregyoung
> Hi all,
> when I try to use the CheckIfInstallable method of
[quoted text clipped - 4 lines]
>
> Why the file remains locked? Is there a way to avoid it?
Greg Young - 05 Jul 2006 00:26 GMT
I would put this up as a suggestion
Cheers,
Greg Young
MVP - C#
http://codebetter.com/blogs/gregyoung
> It is because Assembly.Load is run on the file (the assembly gets loaded
> into your appdomain).
[quoted text clipped - 28 lines]
>>
>> Why the file remains locked? Is there a way to avoid it?
Damien - 05 Jul 2006 07:51 GMT
> It is because Assembly.Load is run on the file (the assembly gets loaded
> into your appdomain).
[quoted text clipped - 14 lines]
> No way to work around this I'm afraid except to wait until the appdomain is
> dead to delete the file.
So, to help the OP, he could:
1) Create a second AppDomain
2) Load either his existing code assembly or just a simple stub one in
3) Create a class in the second domain
4) Call a method on that class which performs the original
CheckIfInstallable check and returns a boolean
5) Unload the second AppDomain
correct?
Damien
Stefano - 05 Jul 2006 10:09 GMT
Ok, thanks to everybody, I've called the method from a second AppDomain and
everything worked!
>> It is because Assembly.Load is run on the file (the assembly gets loaded
>> into your appdomain).
[quoted text clipped - 27 lines]
>
> Damien