I have checked in first half of part (2). We now have a DataContext constructor which takes a connection string similar to: "DbLinqProvider=DbLinq.Sqlite.dll; Server=xx; etc.." The connection string gets searched for DbLinqProvider=xyz substring. If it's there, we load a DLL of that name and load up an IVendor class. If DbLinqProvider substring is not there, we load up an MS SqlServerVendor.
What I am going to do next is modify the codegen - anyone who's generating Northwind should now get an additional constructor. Zdravi Jiri --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
