Mason, Philip wrote:
>
> OK ... I've done this and verified that the database file gets released
> appropriately when running my test code with EF5.
>
Thanks. The changes have now been merged to trunk and will appear in the
next
release.
--
Joe Mistachkin
OK ... I've done this and verified that the database file gets released
appropriately when running my test code with EF5.
Thanks,
- - - Philip
From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] on
behalf of Joe Mistachkin
Mason, Philip wrote:
>
> Looks like I have to flip the switch in SQLite.NET.Settings.targets
> and SQLite.Interop.20XX.[vs]props to enable the functionality. Is
> this correct?
>
Yes, the InteropLegacyClose MSBuild property in the
"SQLite.NET.Settings.targets"
file needs to be set to "true" and
Thanks Joe.
I fetched the latest leaf code with INTEROP_LEGACY_CLOSE and am now getting
ready to build it.
Looks like I have to flip the switch in SQLite.NET.Settings.targets and
SQLite.Interop.20XX.[vs]props to enable the functionality. Is this correct?
- - - Philip
Mason, Philip wrote:
>
> What operation(s) are creating these?
>
It looks like pretty much any query against the database.
>
> Are the objects/connections actually orphaned or is there the possibility
> that activity could pop up and cause problems?
>
Yes, I confirmed that the objects
Thanks very much. That solved that problem. I'm seeing a similar issue
when using an EntityFramework open:
using (var testEntities = new
SystemDataSQLiteTest.TestEntities(connectionString))
{
var users = testEntities.Users.ToArray();
Hello all,
We were previously using 1.0.79.0, but in an attempt to move to VS2012 /
.NET 4.5 I started doing some testing with 1.0.83.0. I found that many of
our UnitTests now fail when they try to delete the temporary test database
file they created. This happens with the SQLiteConnection()
7 matches
Mail list logo