Hello guys, I'm thinking about importing DBLinq sources into mcs tree as the System.Data.Linq implementation.
The basic direction in my idea is simple: - Copy dblinq src directory under mcs/class/System.Data.Linq, replacing existing files, and put System.Data.Linq.dll.sources. For now I just did "find src -name *.cs" and removed extra ones. -- I'm not sure if I remove extra sources. Maybe I will. - We (I?) likely do it when there is a new feature in dblinq or a new release when we want sort of stability. -- Pablo should get our svn access and become able to commit the changes in mcs tree as well, of course ;) In case you don't get it, here is what I did: http://veritas-vos-liberabit.com/tmp/2008/System.Data.Linq-20080930.zip (Replace mcs/class/System.Data.Linq with the archive content.) To not introduce extra complication with related to build dependency, I took the way to import the sources on occasion. It would be the easiest way to do it. Better ideas? Tell me :) There are some TODOs: - For now we don't build "DBMetal" but that it should be done at some stage. I'm not sure if it is doable with current design. -- The source tree layout (having them under mcs/class) is not really a problem; our *.dll.sources could point to the sources under mcs/class/*. - We'd like to support other DBs than SQLServer. (Needs some changes in other providers/vendors.) If everything sounds good, I'll start importing the tree next week. Atsushi Eno --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
