How Do I Repair Corrupt Bin Dll In Visual Studio

Question

1.00/5 (1 vote)

See more:

hello house,

I realize some DLLs in my application have been marked corrupt by the application in visual studio,

i am using visual studio 2013 working on a web application project, i have closed and restarted the application yet the issue still persist, the application still builds and runs but throw some errors, but upon uploading to server using filezilla ftpclient, the corrupt files doesnt show on ftpclient, i have deleted the bin folder and add a new one from my back, but it still shows corrupt whenever those DLLs comes to visual studio environment.

Posted 12-Dec-15 11:25am

Uwakpeter

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Answer 1 · 2015-12-12T14:28:00

Solution 2

Visual Studio never "marks a .DLL corrupt". We have no idea what you're talking about.

Generally, there is no way to "repair" a corrupt .DLL or .EXE. You have to replace it from a known good copy.

But, in your case, you simply rebuild the project from your source files and a new build is placed in the bin folders.

Posted 12-Dec-15 14:28pm

Dave Kreskowiak

Comments

Sergey Alexandrovich Kryukov 12-Dec-15 22:03pm

Agree, a 5.
—SA

Uwakpeter 13-Dec-15 1:28am

@Dave, you are right i was also wondering what could have caused it, but i just found out that marked corrupt files are always shown whenever i clean solution, my question now is, can i build and deploy a project without cleaning solution? thanks

Dave Kreskowiak 13-Dec-15 10:57am

Caused what? Again, Visual Studio does NOT mark anything "corrupt" so we have no idea what you're talking about.

Also, cleaning a solution has nothing to do with deploying it. It removes build artifact files from the target build folders.

User 10668410 · Answer 2 · 2015-12-12T12:42:00

Solution 1

Your program throwing exceptions isn't an indication that your DLL is "corrupt" please be more specific and provide some actual details of the errors you are experiencing, including the error codes, inner exception etc.

Posted 12-Dec-15 12:42pm

User 10668410

Comments

Uwakpeter 13-Dec-15 1:34am

@Samuel Christison, it is a bit difficult to explain more than this, i have screen captured my solution explorer with the marked corrupt files in bin folder, just that i do not know how to attach an image here. The exception it throws was simple enough for me to fix, that was why i didnt bother to include it. but it turns out that marked corrupt files are always shown whenever i clean solution, my question now is, can i build and deploy a project without cleaning solution? refer http://stackoverflow.com/questions/34245692/repair-corrupt-bin-dll-in-visual-studio

[no name] 14-Dec-15 19:46pm

That looks like a "Not Found" icon to me, are you sure they exist in the location you're referencing? There is no such thing as "VS marked my dll as corrupt"

Uwakpeter 15-Dec-15 3:52am

The DLLs are there, i added it myself, it is shown as corrupt whenever i clean the project, so i have stopped cleaning project for now, i dont know what effect that will have on the application. I also realize that the project was created using Iron speed 8.0.2 tool with visual studio 2010, now i am running the project on visual studio 2013, i dont also know whether that could cause this. Thanks