HighTechTalks DotNet Forums  

Error: could not load file or assembly or one of its dependencies

Dotnet General Discussions microsoft.public.dotnet.general


Discuss Error: could not load file or assembly or one of its dependencies in the Dotnet General Discussions forum.



Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old   
Sheila
 
Posts: n/a

Default Error: could not load file or assembly or one of its dependencies - 01-03-2008 , 03:54 AM






Hi,

Does anybody encounter this error:
Unhandled Exception: System.IO.FileLoadException: could not load file or
assembly or one of its dependencies. Access is denied.

I google the error and found a few resolutions, such as exclude Temporary
ASP.NET Files folder from virus scan, grant full rights to Temporary ASP.NET
Files folder, etc. all doesn't work.

Previously the application works fine if all dlls are deployed in GAC, but
after I move dll to application Bin folder, the problem happens. To make the
website up, I have to clear all content in Temporary ASP.NET Files folder,
but after a few runs, it happenes again. Right now the only soultion works
for me is to set trust level to full in web.config, which I don't want to do
due to security reason.

Does anybody know what could be the cause? thanks in advance.




Reply With Quote
  #2  
Old   
Michael Nemtsev [MVP]
 
Posts: n/a

Default Re: Error: could not load file or assembly or one of its dependencies - 01-03-2008 , 04:19 AM






Hello Sheila,

How do u refer to your dll? could you post the code how u declare and use
your dll?



---
WBR,
Michael Nemtsev [.NET/C# MVP] :: blog: http://spaces.live.com/laflour

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo


S> Previously the application works fine if all dlls are deployed in
S> GAC, but after I move dll to application Bin folder, the problem
S> happens. To make the website up, I have to clear all content in
S> Temporary ASP.NET Files folder, but after a few runs, it happenes
S> again. Right now the only soultion works for me is to set trust level
S> to full in web.config, which I don't want to do due to security
S> reason.
S>



Reply With Quote
Reply




Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.4
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.