New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XSD Validation Support - Missing? #3633

Closed
NightOwl888 opened this Issue Oct 3, 2015 · 13 comments

Comments

Projects
None yet
@NightOwl888
Copy link

NightOwl888 commented Oct 3, 2015

As I posted earlier on StackOverflow, I am attempting to port some older code to DNX core 5.0, but it seems that XSD validation support is missing from the library. Or if I am wrong, could someone please provide a sample or point me to the correct document that shows how to validate XML against XSD (separate documents).

@akoeplinger

This comment has been minimized.

Copy link
Member

akoeplinger commented Oct 7, 2015

There was a thread in the .NET Foundation forums about XmlSchema which might be related: http://forums.dotnetfoundation.org/t/xmlschema-in-net-core/507

@SariDev

This comment has been minimized.

Copy link

SariDev commented Mar 24, 2016

Please add support for XSD's in .NET Core.

I dare to say working with XML files and validating those files in an easy way (through xml schema validation) is a pretty common task for most enterprise applications.
Therefore I would like to see support inside .NET Core to work with XSD's.

If XSD's will be added to .NET Core it would be great if the current XSD 1.1 release could be supported as it offers support for assertions, which improves XSD validation a lot.

@prachi2607

This comment has been minimized.

Copy link

prachi2607 commented Apr 4, 2016

Hi,

We are working with XML schemas and writing a custom validator for each schema is a major overhead.
Is schema validation going to be supported on CoreCLR as it is much needed?
If yes, is there a timeline for the same?

Thanks in advance

@wompeter

This comment has been minimized.

Copy link

wompeter commented Apr 8, 2016

Would also love to see support for this. XML won't be going away anytime soon and every enterprise app I've ever touched has validation routines in it :(

@fubar-coder

This comment has been minimized.

Copy link
Contributor

fubar-coder commented May 11, 2016

Related to #2342?

@DevilfishSoftware

This comment has been minimized.

Copy link

DevilfishSoftware commented Aug 26, 2016

Has there been any progress with XSD support in .NET Core?

@danmosemsft

This comment has been minimized.

Copy link
Member

danmosemsft commented Sep 18, 2016

You can see this in master in corefx\src\System.Private.Xml\src\System\Xml\Core. It's expected in the next major release of .NET Core.

@karelz

This comment has been minimized.

Copy link
Member

karelz commented Sep 23, 2016

@danmosemsft should we just close it as fixed or is there still something left?

@danmosemsft

This comment has been minimized.

Copy link
Member

danmosemsft commented Sep 23, 2016

@sepidehMS I'm closing this against #11888 because #11888 is all that remains for this to be useable. Please correct me if I'm wrong. Also, please help close any other issues about missing XML functionality if #11888 will bring it.

@karelz karelz modified the milestones: 1.2.0, Future Sep 23, 2016

@richieeeeeeee

This comment has been minimized.

Copy link

richieeeeeeee commented Nov 17, 2016

Why is it closed? It still does not exist in .NET Core 1.1!

@karelz

This comment has been minimized.

Copy link
Member

karelz commented Nov 17, 2016

Both issues were closed with milestone=1.2, which means they will be fixed in the release after 1.1.
The whole .NET Standard 2.0 push for 1.2 is LOTS of APIs and it takes significant time to port them all even for large team.

@GurmeetMunshi

This comment has been minimized.

Copy link

GurmeetMunshi commented May 31, 2018

How to generate a Class from xsd in dot net core 2.0

@krwq

This comment has been minimized.

Copy link
Member

krwq commented Jun 5, 2018

@GurmeetMunshi, currently it is not supported - you can generate really close to working class using full framework though (might even work without changes). We have a separate issue tracking it: #8647

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment