Thanks for your reply.
I agree, seeing something like makes me wary of getting to fancy with the
still relatively young ASP.NET. Soon after i wrote my message i fixed my
problem: .Net keeps referenced DLLs and contros in the applications bin
directory. If you remove the DLL/control from the references, .NET does not
remove it from that directory. My problem went away once i removed the DLL
from which i was receiving the Access Violation. Knowing that, the highlited
line in the machine.config made sense: <add assembly="*"> is telling .NET
to bind all the reference assemblies in the bin directory. I still don't
know why i got an Access Violation to that DLL, but i can worry about that
later.
Think this makes any sense? Does MS read these newsgroups? Think I should
send this to them?
"Ken Cox [Microsoft MVP]" <BA************@sympatico.ca> wrote in message
news:Oa**************@tk2msftngp13.phx.gbl...
I had one of those the other day and it was really annoying. You may have
to reboot.
The first thing to try is from the Run box:
net stop iisadmin /y
iisreset
In my case, it took a reboot. I wish I could produce a repro scenario for
MS 'cause it is dangerous to have a DLL go bad and lock up like that on a
production machine. I didn't think it was supposed to happen at all in
..NET.
Ken
"Randy Paez" <ra********@concentra.com> wrote in message
news:OU**************@TK2MSFTNGP11.phx.gbl... I installed a control that i got rid of. Now when i try and run another
project i get an Access is Denied {to that control}. It highlites <add
assembly="*"> from the machine.config file. How can i get asp.net to not
look for that control anymore? Please help!