On Wed, 2009-03-25 at 13:36 +0100, Pascal Craponne wrote: > We have two options: > - The mono guys already wrote the class, so we just need to adapt it > (not sure it is even necessary) and use it.
This should be viable, and it's already within DbLinq: src/DbLinq/System.Data.Linq/System.Data.Linq.Mapping/XmlMappingSource.cs. > - Cry a bit and write the class. Not necessary, as it's already written (though we may want to 'svn mv' it to a more appropriate location). > And maybe a third option, by making our DataContext inheriting > from .NET's DataContext. But this will cause a lot of trouble to the > Mono implementation. Can someone confirm? I don't know if this would cause trouble, but it would cause lots of warnings (due to shadowing inherited members, e.g. the non-virtual DataContext.GetChangeSet() method), which would require lots of #if code to handle...on every public DataContext member. Yech. For Mono, we'd further need to make the base type conditional, leading to even more #if in the code base (something I'd prefer to decrease, not increase). So I'm not fond of this third option... - Jon --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DbLinq" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/dblinq?hl=en -~----------~----~----~----~------~----~------~--~---
