ASP.Net still sees my old assembly??

J

Jim Bancroft

I'm having trouble using my VB class library in ASP.Net-- the webserver
gives following error when any component is created from my assembly. This
just started today (was fine on Friday):

----Access to the registry key
HKEY_CLASSES_ROOT\ClassLibrary01.TestObject.Test1 is denied.----


I can't figure out what's wrong; I've checked and rechecked the ASPNet user
account's security and group membership, done all manner of things (even
gave that account Admin privileges), but the error still appeared.

So, I removed the "TestObject" namespace and "Test1" class from my library
project and rebuilt it, just to see what would happen. Incredibly, I got
the same error message.

I then removed the assembly from the GAC, using "gacutil /u ClassLibrary01",
and the message said it was removed, but then...even after recompiling once
more ASPNet still gave me the error message at top. Seems it can't stop
thinking of the "TestObject" namespace.

Finally, I rebooted my machine and took my assembly out of the COM+ catalog
(it uses ServicedComponents), and the error still came up. I've of course
long since removed any mention of the TestObject namespace from my ASP.Net
page.

I'm at a loss. Is there a hidden cache ASP.Net uses to hold onto
assemblies? I can use the assembly fine in, say, a console application, but
aspx pages are a no-go. If you have any ideas about what I can try next or
what's going on here, I'd love to hear from you. Thanks for the advice.


-Jim
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

Forum statistics

Threads
473,743
Messages
2,569,478
Members
44,899
Latest member
RodneyMcAu

Latest Threads

Top