Other possibility may be to use app.config /web.config / maschine.config file entries like ADO .NET standard Dataprovider factory or separate config file like NHibernate
Andrus. ----- Original Message ----- From: Pascal Craponne To: [email protected] Sent: Friday, October 24, 2008 4:57 PM Subject: Re: Tasks Argh, you're right. This prooves that this complicated problem should have been discussed first :) Anyway the vendor still must not provide, in any way (by reference or type name), a method to indicate a required driver, since we can not stick to a driver implementation or version. Ideally, all drivers should be in the AppDomain, so we just would need to identify them and use them. The problem here, is that even if an assembly is referenced in a project, it is not loaded until the application uses some of its classes. The missing link (ah ah ah) is just here. So if we find a way to ensure that a referenced assembly is loaded even if not used by code, then we probably win the game. On Fri, Oct 24, 2008 at 15:30, Atsushi Eno <[EMAIL PROTECTED]> wrote: Hello, Regardless of whether current implementation strategy is to change or not, Dynamic type loading will also happen for loading DB provider assemblies (e.g. System.Data.SQLite.dll), like currently DbLinq.Vendor.Implementation.Vendor.CreateDbConnection() does. To not load assembly dynamically, you will have to add dependencies onto all DB providers, which you don't want (unless I miss some other possibilities). Atsushi Eno Pascal Craponne wrote: > Hi guys, > > I took a quick look at the code, and I definitely think that it is not > DbLinq's responsibility to directly load the required assembly. > The application know what vendors it will use, is then its own > responsibility. > To me, identifiers given in the connection string MUST just allow to > find an IVendor implementation that is already loaded. > Maybe, for DbLinq in extended mode, we may consider later to use an > extension to dynamically load the assembly, but this is not the first > priority. > > The code currently in SVN show that dynamically loading assemblies is a > complex task that is far beyond the DataContext's scope. > > Pascal. -- Pascal. jabber/gtalk: [EMAIL PROTECTED] msn: [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
