[Mono-dev] Broken Linq to XSD managed provider in .Net 4.
Bob "PS" Watson
scope_creep at hotmail.com
Thu Jan 20 09:36:06 EST 2011
Ah, Moma is always going to be slightly imperfect as it's always running late.
No, I'm ashamed to say I haven't but I will now.
From: Jb Evain [mailto:jbevain at gmail.com]
Sent: 20 January 2011 13:20
To: Bob PS Watson
Cc: Leszek Ciesielski; mono-devel-list
Subject: Re: [Mono-dev] Broken Linq to XSD managed provider in .Net 4.
If you have a look at the source, for BaseXmlSchemaType:
// FIXME:This property works as always returning a
valid schema type.
Whatever that means, it means that part of the property is
implemented, but some cases are still left to handle. Until you've run
your application, you don't know if you'll hit those cases. And this
is the case for all the methods you specified. No one throws directly
a NotImplementedException, and no one is missing from Mono.
So, MoMA is an excellent first try to give, but running the
application itself is the real test. Did you even try to run the
On Thu, Jan 20, 2011 at 2:06 PM, Bob "PS" Watson
<scope_creep at hotmail.com> wrote:
> If the .NET 2 conditional is present, why does Moma report they are TODO,
> and how do I fix it. Is it a case need to move all that code into separate
> and make it .net 2.
> -----Original Message-----
> From: Leszek Ciesielski [mailto:skolima at gmail.com]
> Sent: 20 January 2011 07:34
> To: Bob PS Watson
> Cc: Atsushi Eno; mono-devel-list
> Subject: Re: [Mono-dev] Broken Linq to XSD managed provider in .Net 4.
> The NET2 conditional is defined for all build above 1.1 profile (which
> has now been removed), i.e. 2.0, 3.5 (which is really not a separate
> profile - just additional libraries) and 4.0.
> On Thu, Jan 20, 2011 at 3:28 AM, Bob "PS" Watson
> <scope_creep at hotmail.com> wrote:
>> Hi Atsushi,
>> Thanks for the help. Much appreciated dude.
>> I checked the true, all these calls are surrounded by #if .NET2
>> 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
>> time frame.
>> -----Original Message-----
>> 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.
>> Atsushi Eno
>> (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,
>>> it’s perfomant, and allows positional updates to schema before its
>>> Programing away for 2+ months ran Mona and found these 3 calls which
>>> the provider. I know you probably get a bundle of missing method call
>>> every day but…..
>>> I checked the status page for .Net 4 and they look fairly simple but
>>> 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
>>> 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
>>> to get these calls created.
>>> Thanks for the help.
>> Mono-devel-list mailing list
>> Mono-devel-list at lists.ximian.com
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
More information about the Mono-devel-list