Actually the mono runtime team at Xamarin seems to be working on it, so
you should ask them, not me.
But anyways current System.Xml code in referencesource is still
incomplete to actually replace things. It will be done only after
Microsoft's open-sourcing process is done.
Atsushi Eno
On
Hello Atsushi Eno,
When will Mono be replacing its library with the MS's contribution?
MarL
--
View this message in context:
http://mono.1490590.n4.nabble.com/Mono-Net-difference-handling-xs-extension-please-help-tp4664552p4664621.html
Sent from the Mono - Dev mailing list archive at
A planning process will take time. Or you can step up and do the work and
contribute it
On Saturday, November 15, 2014, MarLOne infoseeker...@gmail.com wrote:
Hello Atsushi Eno,
When will Mono be replacing its library with the MS's contribution?
MarL
--
View this message in context:
Hello Timotheus,
Thanks and will try. Perhaps you can give me some assistance with
MonoDevelop/Mono.
In MS .Net, I can stay in say XP (even it has reached end of life) and still
can run VS2010 with .Net 4. But in Mint, I seem to be stuck in the version
of Mono I can get, hence that old version
Hello MarL,
Don't worry, no need to install a new OS...
Please have a look on the download page:
http://www.mono-project.com/download/#download-lin
see the link
http://www.mono-project.com/docs/getting-started/install/linux/#debian-ubuntu-and-derivatives
I think that even provides a recent
Hello Timotheus,
I have the answer for you.
I have a VM with Mint17 which has Mono runtime 3.2.8 which is one major
version that I reported earlier. So I build a console application to test
using this schema (embedded resource) with this sample instance document.
This also gives me a good test
Probably is the core System.Xml class library assembly that misses some
functionality. It is kind of lower priority these days as most people is
moving to schema-less serialization with either Xml or JSON.
Surely nobody needed to exercise the extension mechanism before, so that's
is why it is
] Mono .Net difference - handling xs:extension please
help
Probably is the core System.Xml class library assembly that misses some
functionality. It is kind of lower priority these days as most people is moving
to schema-less serialization with either Xml or JSON.Surely nobody needed
Hello,
If you believe xs:complexType/xs:extension is that superficial, could
you explain why the validation result is wrong?
Dealing with xs:complexType is one of the most complicated XML schema
validation technology, which involved handful of ambiguity, which may be
fixed in later
Actually I was wrong, it's already there:
https://github.com/Microsoft/referencesource/tree/master/System.Xml/System/Xml/Schema
Atsushi Eno
On 2014年11月13日 00:05, Atsushi Eno wrote:
And Microsoft has announced open-sourcing .NET! So you don't have to
spread your hate speech on bugs, we will
And Microsoft has announced open-sourcing .NET! So you don't have to
spread your hate speech on bugs, we will take their good code.
https://github.com/dotnet/corefx/tree/master/src
(No XML Schema implementation yet, but I assume that would happen at
some stage.)
Atsushi Eno
On 2014年11月12日
Hello,
Not sure if this issue has been raised as it is driving me nuts as another
Mono/.Net runtime behavior differences.
I have a xml schema called FamilyTree2.xsd FamilyTree2.xsd
http://mono.1490590.n4.nabble.com/file/n4664552/FamilyTree2.xsd . This
has been validate in Eclipse's Xsd Editor.
Hello MarL,
I then use xsd.exe in Mono runtime 2.10.8.1 to generate a C# class from the
schema. I then use the following code to deserialize the instance document
It seems you are using an ancient version of Mono.
Please try with a recent Mono, see
http://www.mono-project.com/download/, we are
13 matches
Mail list logo
