Depending on your setup, it could take a while for this to run so be patient. You’ll receive a message that the drive is locked and the operation will need to be performed on the next restart. It might be wise to attempt Solution 4 first to minimise the chances of any data being overwritten. Solution 3 – CHKDSKĭepending on the particulars of the corruption, trusty old chkdsk might help. No dice for me, this directory was empty for me, on to the next solution. %USERPROFILE%DocumentsVisual Studio Backup Files Anyway it’s still worth checking the backup folder for your project, in: Chances are that Visual Studio would’ve prompted you to restore the corrupted file when launching it after the crash. If you have AutoRecovery enabled, you might be lucky enough to find a backup of the file. If you don’t have any assemblies or you want to try to restore the file to its original awesomeness, continue on. I’m sure you’ll agree it’s better than nothing. Doesn’t really help if the code has been obfuscated.Depending on your build configuration, some optimisation may have taken place.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |