[Mono-dev] Broken Linq to XSD managed provider in .Net 4.

[Atsushi Eno]

Sounds like it's just that those "marked as MonoTODO" members have 
cosmetic reasons for those attributes. You should not expect too much on 
those attributes that they reflect what you think. They are rather used 
wild-guessing guidelines.
There is no toolchain (moma) bug when they are indeed marked. And I 
won't remove those attributes when there are reasons.

Why don't you just *run* it and see if it works or not instead?

Atsushi Eno

(2011/01/20 22:30), Bob "PS" Watson wrote:
> Hi,
>
> I tested the xml.schema.linq which is the managed provider for Linq to XSD,
> has a 3.5 profile dependency. The other dll's pass fine in Moma.
>
> How do I go about fixing. Can you give me a path to follow.
> Is it bug, that Moma is report TODO, when implementation is complete.
> Thanks.
>
> -----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
> 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
>> time frame.
>>
>> Bob.
>>
>> -----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.
>>
>> Hi,
>>
>> To get your patches ready, this page would be a good starter.
>> http://mono-project.com/Contributing
>> 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:
>>> Hello,
>>> 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
>>> serialized.
>>>
>>> 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
>>> not.
>>>
>>> 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
>>> XmlSchemaDatatype.ChangeType().
>>>
>>> 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
>>> assembly.
>>>
>>> How do I go about getting these 3 assemblies full patched, to complete
>>> implementation.
>>> 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.
>>> Bob.
>>>
>>>
>>
>> _______________________________________________
>> Mono-devel-list mailing list
>> Mono-devel-list at lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>>
>
>