[Mono-dev] Broken Linq to XSD managed provider in .Net 4.
Bob "PS" Watson
scope_creep at hotmail.com
Wed Jan 19 21:28:39 EST 2011
Thanks for the help. Much appreciated dude.
I checked the true, all these calls are surrounded by #if .NET2 conditional.
I suspect when the trunk was being coded up to .NET 2 from 1.1 needed it for some reason?;
But has been forgotten about from the update to 3.5.
See of I raised bug report, to remove the conditionals in .NET 4. Would it sit in
Devlopment hell for donkey, or is their any good chance it would get done in a reasonable
From: Atsushi Eno [mailto:atsushieno at veritas-vos-liberabit.com]
Sent: 19 January 2011 20:17
To: Bob Watson
Cc: mono-devel-list at lists.ximian.com
Subject: Re: [Mono-dev] Broken Linq to XSD managed provider in .Net 4.
To get your patches ready, this page would be a good starter.
I'm not sure what you meant on XmlSchemaType.BaseXmlSchemaType, but
those 3 members are implemented AFAIK.
(2011/01/20 3:05), Bob Watson wrote:
> I’m developing a multithreaded crossplatform file reader as part of a log
> management solution. We use linq to XSD to generate IDMEF xml on the fly, as
> it’s perfomant, and allows positional updates to schema before its
> Programing away for 2+ months ran Mona and found these 3 calls which break
> the provider. I know you probably get a bundle of missing method call emails
> every day but…..
> I checked the status page for .Net 4 and they look fairly simple but perhaps
> XmlSchemaType.GetBuiltInSimpleType() in System.Xml.Schema has not been
> coded and has been flagged as TODO.
> Also in .NET 2 implemented XmlSchemaType.BaseXmlSchemaType () still not
> coded for .Mono 4.0 which also Linq to XSD. Same with
> I’m also getting this message “We should parse basetype from right to left
> in 2.0 profile.” Applied on the CodeTypeReference .ctor in System.CodeDom
> How do I go about getting these 3 assemblies full patched, to complete
> Is there a well defined process for doing it. I just need to get the process
> to get these calls created.
> Thanks for the help.
More information about the Mono-devel-list