That cleared it up, thank you for the quick response.
-/renji
On Mon, Jun 30, 2014 at 12:17 AM, Richard Hipp wrote:
> On Sun, Jun 29, 2014 at 11:57 AM, Renji Panicker
> wrote:
>
> If some variable "p" is a pointer to the vfstrace object, then the
>
> The recommended way to handle this is by using the NuGet package, e.g.:
>
> https://www.nuget.org/packages/System.Data.SQLite/
Much appreciated Joe,
jlc
___
sqlite-users mailing list
sqlite-users@sqlite.org
Joseph L. Casale wrote:
>
> I am new to C# and am building an x64 console app, visual studio copies
the
> System.Data.SQLite.dll to the build directory as its added to as a
reference
> so how do people routinely manage the interop dll in projects? Is there an
> automated way to get it copied to
I am new to C# and am building an x64 console app, visual studio copies the
System.Data.SQLite.dll to the build directory as its added to as a reference
so how do people routinely manage the interop dll in projects? Is there an
automated way to get it copied to the build directory when setting up
On Sun, Jun 29, 2014 at 11:57 AM, Renji Panicker
wrote:
> I am developing a shim, and am facing a problem (or it might be a defect in
> the sample shims I have seen so far):
>
(1) test_vfstrace.c is probably a better example of a shim than
test_multiplex.c, at least for
I am developing a shim, and am facing a problem (or it might be a defect in
the sample shims I have seen so far):
- When I receive a call to my xOpen function, the 3rd parameter is a
sqlite3_file* type.
- As per the sqlite3PagerOpen function, the size of the memory allocated to
this pointer is
6 matches
Mail list logo