So, after struggling to get DNN installed on Windows 7, I started developing a module.  I wanted to use the Ajax Control Toolkit (specifically the calendar extender), so I copied the DLL into my bin folder and was off to the races.  Except not at all.  I spent half a day debugging this fricken' permissions error - mind you I'm running under full trust, so this shouldn't be a problem.

Here's a tip for anyone developing under full trust, wanting to use external or third-party DLL's (like Ajax Control Toolkit):  right click on the DLL, go to properties and unblock the DLL.

Got news for ya, that's an old thing I've had on my workstation since upgrading to XP pro sp-2.  I've always had to do that with any downloads, not just DNN or MS stuff.  Could be a default security setting somewhere to turn it off, but I've just lived with it so long, hadn't given much thought to it.

Cheers

Yes, it's strange, but kinda par for the course with MS, and those pesky updates that do things in the background without really saying.  I did see this interesting bit on it, which is related to something introduced in sp2.  Most likely, there's a IE setting somewhere to deal with it.  Here's a tidbit, below, and you can read the whole thing here.

"This article discusses the Attachment Manager that is included in Microsoft Windows XP Service Pack 2 (SP2). This article also discusses how the Attachment Manager handles different file types. "

It's a security feature that was introduced.  Don't mind it so much, but sometimes, I foget to unblock before I install, and that does 'fudge' things up nicely, like you said.