The testing-no-db branch has been merged to trunk in r1005. The most visible change is where the unit tests are placed: after building the solution, the unit tests are placed into the top-level `build' directory (or the top-level `build.dbg' if you're building the Debug configuration). The test assemblies are now named after the vendor assembly, e.g. the tests for the vendor assembly DbLinq.Sqlite.dll are in DbLinq.Sqlite_test.dll.
- Jon On Thu, 2009-03-05 at 08:07 +0100, Pascal Craponne wrote: > Anything you like. Anyway it's probably time soon to merge to trunk. > > > Pascal. > > jabber/gtalk: [email protected] > msn: [email protected] > > > > > On Thu, Mar 5, 2009 at 01:58, Jonathan Pryor <[email protected]> wrote: > > On Wed, 2009-03-04 at 23:09 +0100, Pascal Craponne wrote: > > > No thought, my head is filled with bone. No brain there. > > > > > You're the most intelligent bone I've ever met. :-) > > > > > > Ideally, the best option would be to have the two drivers, > > and two separate test sets. This way we could ensure that > > both drivers work at their best (since I presume that people > > still use System.Data.SQLite). > > We did the same thing for Oracle: there are two tests sets, > > one for MS driver, the other for Oracle ODP drivers. And > > this is necessary. > > > > > Then we should provide two sets of drivers. > > Should I create a second set of drivers against trunk and send > patches to the list, or within the testing-no-db branch? (I'd > prefer the latter, as it'll also require tests, which differ > between the branch and trunk...). > > > > - 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 -~----------~----~----~----~------~----~------~--~---
