On Wed, 2009-03-04 at 01:26 +0000, Jonathan Pryor wrote: > Move on to Test_NUnit_MsSql.dll, and see more fail: > > Test_NUnit_MsSql.WriteTestSetup (TestFixtureSetUp): > System.Data.SqlClient.SqlException : A network-related or > instance-specific error occurred while establishing a > connection to SQL Server. The server was not found or was not > accessible. Verify that the instance name is correct and that > SQL Server is configured to allow remote connections. > (provider: SQL Network Interfaces, error: 26 - Error Locating > Server/Instance Specified)
I've been exploring this some more, and it looks like it requires an actual SQL server; SQL Server Compact Edition (as bundled with Visual Studio) will not work. Specifically, to use SQL Server Compact Edition, the unit tests would need to either (1) use the Northwind type directly, or (2) use SqlCeConnection instead of SqlConnection within the TestBase.Conn property. (This could be done by introducing a new #elif block for MSSQLCE.) Thus, at present I'm only able to run the DbLinq unit tests for Sqlite (which is better than nothing). - 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 -~----------~----~----~----~------~----~------~--~---
