That's good news. In regards to have conditional references in csproj to reference either System.Data.SQLite.DLL x86 vs System.Data.SQLite.DLL x64, you don't need to do it. All you need is to set the platform setting of the Test project to be "x86" (change it from default "Any CPU") you then can reference the x86 version of System.Data.SQLite.DLL on a 64bit OS and compile + run the tests without any problems. See http://www.brianpeek.com/blog/archive/2007/11/13/x64-development-with-net.aspx
Cheers John On Jan 7, 7:59 am, Roelof Blom <[email protected]> wrote: > Latest ARIntegration is building with in-memory tests, no problems at all > there. > > On Wed, Jan 6, 2010 at 9:31 PM, John Simons <[email protected]>wrote: > > > Markus and Roelof, > > > Regarding using sqlite in-memory, have tried it before about 1.5 > > months ago. I actually think that is the way to go, no dependencies on > > a physical database server. > > > I converted AR and NHFaclitity, I didn't actually tried ARFacility, > > anyway, the results were good except for distributed transactions > > across 2 dbs, those tests didn't work. > > I had to use a temp sqllite db to run all the tests, the in-memory one > > has too many limitations. > > The NHFaclitity I got it to run with 2 tests failing, the AR can't > > really remember but pretty much anything to do with distributed > > transactions across 2 dbs failed. > > Didn't tried to run it against linux mono. > > So my conclusion was, it can be done as long we don't run distributed > > transactions unittests. > > > Cheers > > John > > > On Jan 6, 11:31 pm, Roelof Blom <[email protected]> wrote: > > > Mind if I port that new stuff from AR to the facility? > > > > On Wed, Jan 6, 2010 at 1:08 PM, Markus Zywitza <[email protected] > > >wrote: > > > > > 2010/1/6 Roelof Blom <[email protected]>: > > > > > On a different note regarding running database tests: how about > > changing > > > > the > > > > > defaults to run them against an in-memory SQLite database? > > > > > -- Roelof. > > > > > All new tests in AR use InMemoryTesting. But this requires more than > > > > simply setting a new configuration because in this case, the database > > > > is destroyed directly after commiting the DDL. > > > > > A possible solutuion is to use a filebased SQLite DB located in a > > > > temporary directory. I'll have a look at this the next days. > > > > > -Markus > > > > > -- > > > > You received this message because you are subscribed to the Google > > Groups > > > > "Castle Project Development List" group. > > > > To post to this group, send email to > > [email protected] > > > > . > > > > To unsubscribe from this group, send email to > > > > [email protected]<castle-project-devel%[email protected]> > > <castle-project-devel%[email protected]<castle-project-devel%[email protected]> > > > > > . > > > > For more options, visit this group at > > > >http://groups.google.com/group/castle-project-devel?hl=en. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Castle Project Development List" group. > > To post to this group, send email to [email protected] > > . > > To unsubscribe from this group, send email to > > [email protected]<castle-project-devel%[email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/castle-project-devel?hl=en.
-- You received this message because you are subscribed to the Google Groups "Castle Project Development List" 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/castle-project-devel?hl=en.
