Re: [sqlite] System.Data.SQLite: Commit and Rollback set Connection tonull

> The Connection property is not guaranteed by the MSDN documentation to > remain valid after a call to Commit or Rollback. It's really an internal > implementation detail. > > > http://msdn.microsoft.com/en-us/library/system.data.idbtransaction.connection.aspx > Indeed, I already checked MSDN

[sqlite] System.Data.SQLite: Commit and Rollback set Connection to null

Hi, I don't know if it's the right mailing list to talk about System.Data.SQLite.dll. DbTransaction has a property Connection that corresponds to the connection used by the transaction. I don't understand why calling Commit or Rollback on the transaction automatically sets that property to null.

Re: [sqlite] issue loading SQLite.Interop.dll in different folder

> Unfortunately, the PrivateBinPath only applies to managed assemblies, not > to > native DLLs. The native DLL search mechanism built into Windows uses > completely > different search semantics. See: > > http://msdn.microsoft.com/en-us/library/ms684179%28v=VS.85%29.aspx > Thanks, now I understand

[sqlite] issue loading SQLite.Interop.dll in different folder

Hi, I'm using System.Data.SQLite in my C# application which can run on x86 and x64. All my assemblies are in a main folder or its subfolders. I set the private bin path so that all assemblies will be automatically found by .Net. Assemblies that are specific to x86 or x64 are in folders with 32