I have an ASP.NET application that is using a code library our development
team uses. The code library is a few web controls in a Strong Named
assembly. The application is built using that SN assembly. The application's
assembly is not currently given a SN yet.
Developers in the environment are reporting that they are getting "Access is
Denied" sporadically when they make calls to the controls in the SN
assembly. It doesn't happen all the time, but when it does, they have to
kill the asp.net process to get it to stop the error. It then goes back to
working for a while.
We are putting the SN assembly in the /bin folder of the ASP.NET
application. We are not putting it in the GAC because our clients don't do
that.
Anyone have any idea why this would occur? I don't remember this happening
at all before I signed the web controls library assembly, so thats my only
clue.
Thanks
/Chris