It means the Users group does have Read permission, so it isn't that.
...thinking...
If it were me, I would try a few different things. I would try to run it normally (not debug) and see if it worked, create other projects to see if I could get it to work in anything to see if the issue was a corrupt registration of the third party dll or
something in one of my settings somewhere.
You DID
regsvr32 /u thedll.dll
before you tried to register it again, right?
Please Mark As Answer posts that helped you.
"If we learn from our mistakes, I should be brilliant by now."
MCTS - .NET Framework 2.0: Web Applications
Marked as answer by Bruno Yu - MSFT on Feb 18, 2008 07:20 AM
threeo
Participant
1156 Points
539 Posts
Re: can't fix inherited code
Feb 14, 2008 03:46 PM|LINK
here's what i got in response to the CACLS:
BUILTIN\Users:R
BUILTIN\Power Users:C
BUILTIN\Administrators:F
NT AUTHORITY\SYSTEM:F
but i don't know how to interpret it really
this code ran fine before i created an EXE
nikki_doer_o...
Contributor
6863 Points
1097 Posts
Re: can't fix inherited code
Feb 14, 2008 09:55 PM|LINK
It means the Users group does have Read permission, so it isn't that.
...thinking...
If it were me, I would try a few different things. I would try to run it normally (not debug) and see if it worked, create other projects to see if I could get it to work in anything to see if the issue was a corrupt registration of the third party dll or something in one of my settings somewhere.
You DID
regsvr32 /u thedll.dll
before you tried to register it again, right?
"If we learn from our mistakes, I should be brilliant by now."
MCTS - .NET Framework 2.0: Web Applications