vb.net - Is XSD data validation reliable in .Net 4.0? -


i have written client public soap web service, using wsdl , several xsd files supplied service provider. wanted find easy way validate user data against xsd files, used standard example msdn, using xmlschemaset xsd files, xmlreader , validation routine catch error messages. (the code available @ http://msdn.microsoft.com/en-us/library/as3tta56.aspx) works data elements, others not throw error when invalid. if include "validationflags = validationflags or xmlschemavalidationflags.reportvalidationwarnings", lot of warnings, e.g. "could not find schema information element 'myrequest'", "could not find schema information attribute 'thedate'", etc. can open xsd files in vs2010 ide, , xml schema explorer shows these elements , attributes.

so main question familiar validating xml data in vs2010 in way is, there limits complexity of xsd files xmlreader validation can handle? prefixes target namespaces confuse xmlreader? there thousands of complex types defined in schema, spread across 7 xsd files, why wanted handled automatically, rather me writing validation routine each user input field.

thanks in advance.

the .net validation may not perfect, yet it's among best in industry. 1 issue have sure schema loader (we use our own), gets fooled (i say). beside above, not aware of other limitations, along lines described. routinely use .net xmlschemaset load , validate xsds spread across hundreds of files, in sort of namespace combinations, , thousands of elements, types, etc.


Comments

Popular posts from this blog

monitor web browser programmatically in Android? -

Shrink a YouTube video to responsive width -

wpf - PdfWriter.GetInstance throws System.NullReferenceException -