I took a look at how .NET works when loading assemblies (and couldn't find any precise documentation on this. If someone gets it, please give the link): - assemblies are loaded only when types are used - assemblies do not contain any trace of referenced assemblies - when another assembly is used, it is by the referenced type. - assemblies are searched in GAC and currently directory for type resolution (and some other directories can be specified too).
So I think we can not load extra assemblies to find what's in, because we would need to search the whole application directory, and much worse, the GAC. This leaves to options, and we can use both: - scan the current AppDomain (this is enough for Mono where all vendors are embedded into System.Data.Linq) - for DbLinq in extended mode, as Andrus suggested, we can also use an extra configuration section (or better, a vendor provider that can be changed). This was for vendors. For database drivers, the problem is probably worse. I'd like to find a solution similar to what I wrote in paragraphs above. Anyway, I suggest that we stop changes on this part until we all agree. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
