Sunday, August 2, 2009

Could not load file or assembly 'dll' or one of its dependencies.?

Hi,


I am using VS 2005 and XP Professional. My application was running successfully. suddenly one file got currpted. I replaced with back up that file after that i getting this error though Build is successfull but when login page should display in that place following exception occured..


I have gone through many fourams and tried all stuffs but not able to solve problem am in tooo hurry because task had been assigned..


This is the error....


=== Pre-bind state information ===


LOG: User = CLIENT07\ASPNET


LOG: DisplayName = Interop.ADSSECURITYLib


(Partial)


LOG: Appbase = file:///C:/Develop/


LOG: Initial PrivatePath = C:\Develop\bin


Calling assembly : (Unknown).


===


LOG: This bind starts in default load context.


LOG: Using application configuration file: C:\Develop\web.config


LOG: Using host configuration file: c:\windows\microsoft.net\framework\v2.0....

Could not load file or assembly 'dll' or one of its dependencies.?
When you replace your files with the backup, (do it offline) go to windows explorer, since IE isn't working, click View then click folder options then Show Hidden files and folders. Then overwrite the corrupted directory with the backup. Then go back to the same place on the toolbar and de-select that option.





Windows has a security feature of hiding system folders and system files, even from itself. If you install any software you should do that.





That's the most common problem I have when fixing Windows. Or used to have, since I started doing it as a discipline every time.





If all of explorer isn't functioning, Windows won't load. You have to use the DOS command line function attrib -rash *.* from the c:\ prompt


That clears all the hidden, archive system and read-only attributes from all the files. Then do your repair. Then start Windows and before going online undo all that.


Those files are hidden or made non-executable for a very good reason. You wouldn't want to delete Command.com or himem.sys or win.sys or anything like that.


No comments:

Post a Comment