Application made with Mono 2.0, compatible with .Net Framework 2.0. It allows to load and modify xml, xsd and xsl docs and perform theirs validation, also using an embedded browser. Also, it allows to apply xsl to xml and to validate xml with xsd.

Project Samples

Project Activity

See All Activity >

Follow XmlValidator

XmlValidator Web Site

Other Useful Business Software

Communicate & Connect with Ring Central's VoIP Solution Communicate & Connect with Ring Central's VoIP Solution Icon
Communicate & Connect with Ring Central's VoIP Solution Icon

Cloud Powered Business Phone System

  • Unrivaled value & reliability in one solution
  • Unlimited Calls/SMS/Conferencing/Fax
  • Trusted by 350,000+ Businesses

Rate This Project

Login To Rate This Project

User Ratings

★★★★★
★★★★
★★★
★★
4
0
0
1
2
ease 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 4 / 5
features 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 2 / 5
design 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 4 / 5
support 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 4 / 5

User Reviews

  • @oscarand: I like your tool. It's easy to use and serves its purpose well. Anyway, I found that it doesn't support some xpath expressions. Given this xml input: <root> <test><id>3000</id></test> <test><id>3000</id></test> <test><id>3000</id></test> <test><id>3002</id></test> <test><id>3002</id></test> <test><id>3005</id></test> </root> And the following xpath: (/root/test[id=3002]/id)[1] The tool doesn't return any result. (It should return '3002'). Do you plan to support this kind of xpath expressions in a future release? Thanks!

  • This would be a good tool, however, when validating xml against an xsd, I get a message: "Error - The element cannot contain text. Content model is empty". But it does not tell me anywhere what Node or Element has the error. I finally found which node by manually figuring it out. This tool should always show what node/element the error occurred on, but it doesn't. I forced other errors too, and many errors do not tell you what node the error occurred on. For example, add any attribute to an element, that isn't allowed in the xsd, and you get an error, but it does not tell you what Node/Element the error is in. Otherwise, this looks like it would be a good tool.

  • Limited to 64 KB

  • Bad handling. Limited to 64 KB. Cannot be used when XSD > 64 KB

  • Great app, precisely what I needed without the extra fat! Thanks

Read more reviews >

Additional Project Details

Languages

English

Intended Audience

Information Technology, Developers

User Interface

.NET/Mono

Programming Language

C#

Registered

2009-09-17