Open Source Visual Basic .NET Text Processing Software

Visual Basic .NET Text Processing Software

View 91 business solutions

Browse free open source Visual Basic .NET Text Processing Software and projects below. Use the toggles on the left to filter open source Visual Basic .NET Text Processing Software by OS, license, language, programming language, and project status.

  • AI-generated apps that pass security review Icon
    AI-generated apps that pass security review

    Stop waiting on engineering. Build production-ready internal tools with AI—on your company data, in your cloud.

    Retool lets you generate dashboards, admin panels, and workflows directly on your data. Type something like “Build me a revenue dashboard on my Stripe data” and get a working app with security, permissions, and compliance built in from day one. Whether on our cloud or self-hosted, create the internal software your team needs without compromising enterprise standards or control.
    Try Retool free
  • Find Hidden Risks in Windows Task Scheduler Icon
    Find Hidden Risks in Windows Task Scheduler

    Free diagnostic script reveals configuration issues, error patterns, and security risks. Instant HTML report.

    Windows Task Scheduler might be hiding critical failures. Download the free JAMS diagnostic tool to uncover problems before they impact production—get a color-coded risk report with clear remediation steps in minutes.
    Download Free Tool
  • 1
    XML Truncator-Fixer

    XML Truncator-Fixer

    Truncates XML at first error-uses the xmllint to add correct end tags.

    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.
    Downloads: 0 This Week
    Last Update:
    See Project
  • Previous
  • You're on page 1
  • Next