RE: ASP.Net 1.1 shadow copy + reflection problem
From: icesoftware (icesoftware_at_discussions.microsoft.com)
Date: 11/29/04
- Next message: Jon Skeet [C# MVP]: "Re: Copy protection for a .NET application"
- Previous message: Robby: "Re: Copy protection for a .NET application"
- In reply to: Joco: "RE: ASP.Net 1.1 shadow copy + reflection problem"
- Next in thread: Joco: "RE: ASP.Net 1.1 shadow copy + reflection problem"
- Reply: Joco: "RE: ASP.Net 1.1 shadow copy + reflection problem"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 29 Nov 2004 04:11:02 -0800
> What I would like to know is why do you use SC? .NET by itself does not lock
> dll's so you should be free to change/delete/add them even when the
> application is running.
First of all thanks a lot for the hint.
To answer your question, I use SC explicitly since I need to load libraries
(assemblies) from other directories that are not the bin. If I was using just
the bin then SC would be on by default and the binaries would not be locked.
In my case, instead, through reflection I can load the assembly but it's
locked. I needed to be able to update the binaries and so I activated the SC
on the directories I need to load from.
Now I am experimenting strong naming the assemblies since I read that if you
do so the LoadFrom should be able to differenciate between two different
versions of the assembly loaded from the same dir. So far I'm not getting any
good response.
Anyone has some other hint?
Thanks in advance for any help.
ACL
- Next message: Jon Skeet [C# MVP]: "Re: Copy protection for a .NET application"
- Previous message: Robby: "Re: Copy protection for a .NET application"
- In reply to: Joco: "RE: ASP.Net 1.1 shadow copy + reflection problem"
- Next in thread: Joco: "RE: ASP.Net 1.1 shadow copy + reflection problem"
- Reply: Joco: "RE: ASP.Net 1.1 shadow copy + reflection problem"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|