Open Source Visual Basic .NET Text Editors

XML was designed from the beginning to be intolerant of errors. This decision adversely affects MS Word's corruption recovery. With one error in the document.xml subfile where all the DOCX file's text is stored, instead of a partial recovery, Word will stop and throw an error. Savvy DOCX Recovery attempts to do precise surgery on corrupt Word documents to reorder or excise bad XML tags. If this doesn't work, it uses the command line app xmllint first to attempt to repair corrupt XML subfiles of the DOCX. If this doesn't work a second attempt is made where the corrupt XML subfiles are truncated at the first error, and the correct ending tags are again added with xmllint. If all else fails, SilverCoder's DocToText is used to extract text. Try also http://wordcorruptdocchecker.codeplex.com/ and https://support.microsoft.com/en-us/kb/2528942 and my other SF projects: Corrupt Extractor for Microsoft Office, Corrupt DOCX Salvager, S2 Recovery Tools for Microsoft Word.

Microsoft recommends methods for recovering corrupt Word files that won't open. This software provides buttons to easily invoke these as well as providing 5 independent methods for recovering and opening corrupt Microsoft Word DOC & DOCX files. Additionally the program provides links to two pieces of freeware not coded by the author, a free service (if you can wait 14 days!) and a featured commercial solution (which is an affiliate of the author's). Also it has its own native previous file version recovery tool which works in any version of Windows, Vista-Windows 10 if System Protection has been turned on in the System App of the Control Panel and a Restore Point made. Another feature is a GUI interface for finding temporary, deleted and lost versions of corrupt files. Future plans are to implement Microsoft's instructions for recovering corrupt Word files that will open. This program was formerly known as Word Recovery and more recently S2 Services Word Recovery

XML is intolerant of errors. This program will automatically salvage XML files by finding the first XML error, then truncating a configurable number of characters before the error and finally using the great xmllint to recover the xml file by automatically adding the correct end tags. The program starts with a default of 50 characters truncation. This truncation value may need to be changed if the truncation happens in the middle of a complex tag as xmllint may not know how to recover the file correctly. Additionally some extra text or data may be recoverable by changing the truncation amount to less than 50 characters.The extra truncation is needed in the first place because the XML validator used is not able to perfectly identify where the XML corruption begins and will often not flag the corruption for several characters after it begins.

Fast algorithm text (string) replace case insensitive writing in .NET. Increase the performance of your application!

Notepad² is a text and source code editor for Windows. Notepad² offers syntax coloration for common langages, customizable interface, auto-completion, macro recording and so much more !