Re: [sqlite] [SQLite.ADO.Net] Upgrading XP to SQLite version?

2013-03-01 Thread Gilles Ganault 
On Fri, 01 Mar 2013 18:08:43 +0100, Bernd Lehmkuhl
 wrote:
>I asked Joe Mistachkin a while back the same. Here's what he replied:
>
>Am 21.09.2012 00:35, schrieb Joe Mistachkin:
>> Bernd wrote:
>>>
>>> Could you elaborate on why I should avoid doing as I do at the moment?
>>>
>>
>> The mixed-mode assembly contains native code for one platform as well as
>> the managed code.  This prevents the same application from being easily
>> deployed on both x86 and x64.
>>
>> I suppose if you only ever deal with one processor architecture on all the
>> target machines, it's just fine to use the bundled packages.
>>
>> Also, mixed-mode assemblies are not supported by Mono or the .NET Compact
>> Framework.

Vielen Dank! Good to finally know what the difference is.

So it looks like the no-bundle is the better option.

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] [SQLite.ADO.Net] Upgrading XP to SQLite version?

2013-03-01 Thread Bernd Lehmkuhl 

Am 27.02.2013 15:28, schrieb Gilles Ganault:

On Tue, 26 Feb 2013 19:45:27 -0500, Kevin Benson
 wrote:

Right, but while the first DLL will be found since it's now part of
the project (Project > Add Reference), the wiki doesn't say that this
doesn't take care of the other DLL.



http://www.mail-archive.com/sqlite-users@sqlite.org/msg73039.html


Good to know, although creating an .\x86 or .\x64 doesn't seem to add
anything as compared to simply putting the two DLLs in the
application's directory.


Speaking of which, why is the no-bundle version (two DLLs) to be
prefered to the bundle version (single DLL)? It solves this issue.


I still didn't find any info on the web about what the difference is.

The wiki says: "All the "bundle" packages contain the
"System.Data.SQLite.dll" mixed-mode assembly. These packages should
only be used in cases where the assembly binary must be deployed to
the Global Assembly Cache for some reason (e.g. to support some legacy
application on customer machines). "

Anyone knows more?

Thank you.


I asked Joe Mistachkin a while back the same. Here's what he replied:

Am 21.09.2012 00:35, schrieb Joe Mistachkin:

Bernd wrote:


Could you elaborate on why I should avoid doing as I do at the moment?



The mixed-mode assembly contains native code for one platform as well as
the managed code.  This prevents the same application from being easily
deployed on both x86 and x64.

I suppose if you only ever deal with one processor architecture on all the
target machines, it's just fine to use the bundled packages.

Also, mixed-mode assemblies are not supported by Mono or the .NET Compact
Framework.

--
Joe Mistachkin

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users




___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] [SQLite.ADO.Net] Upgrading XP to SQLite version?

2013-02-27 Thread Gilles Ganault 
On Tue, 26 Feb 2013 19:45:27 -0500, Kevin Benson
 wrote:
>> Right, but while the first DLL will be found since it's now part of
>> the project (Project > Add Reference), the wiki doesn't say that this
>> doesn't take care of the other DLL.

>http://www.mail-archive.com/sqlite-users@sqlite.org/msg73039.html

Good to know, although creating an .\x86 or .\x64 doesn't seem to add
anything as compared to simply putting the two DLLs in the
application's directory.

>> Speaking of which, why is the no-bundle version (two DLLs) to be
>> prefered to the bundle version (single DLL)? It solves this issue.

I still didn't find any info on the web about what the difference is.

The wiki says: "All the "bundle" packages contain the
"System.Data.SQLite.dll" mixed-mode assembly. These packages should
only be used in cases where the assembly binary must be deployed to
the Global Assembly Cache for some reason (e.g. to support some legacy
application on customer machines). "

Anyone knows more?

Thank you.

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] [SQLite.ADO.Net] Upgrading XP to SQLite version?

2013-02-26 Thread Gilles Ganault 
On Tue, 26 Feb 2013 18:44:28 -0500, Kevin Benson
 wrote:
>The directory doesn't *HAVE* to be called ...\Externals. You pick the name,
>any name, and then tell Visual Studio, that is all ;-)

Right, but while the first DLL will be found since it's now part of
the project (Project > Add Reference), the wiki doesn't say that this
doesn't take care of the other DLL.

Speaking of which, why is the no-bundle version (two DLLs) to be
prefered to the bundle version (single DLL)? It solves this issue.

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] [SQLite.ADO.Net] Upgrading XP to SQLite version?

2013-02-26 Thread Kevin Benson 
On Tue, Feb 26, 2013 at 5:37 PM, Gilles Ganault wrote:

> On Tue, 26 Feb 2013 13:09:10 -0500, Kevin Benson
> < kevin.m.ben...@gmail.com> wrote:
> > Because there are actually a number of different ways the (CLR)untime
> > locates assemblies, I ~believe~ the FAQ only attempts to offer a general
> > advisement about the "Externals" folder as a *HINT*. The rest is up to
> the
> > programmer.
>
> Thanks for the link to MSDN, but it doesn't mention \Externals, so the
> application won't find the other DLL since it's neither in the
> application directory nor in the PATH.
>


The directory doesn't *HAVE* to be called ...\Externals. You pick the name,
any name, and then tell Visual Studio, that is all ;-)
The FAQ is just illustrating with a "semantic" name example ...that the
folder(s) would represent "where you store" any/all external files
associated with your project/solution. I ~believe~ the histrionics of
Visual Studio C++ discussions reference /Externals, so that example
name likely originates somewhere back in time and actual usage.
--
   --
  --
 --Ô¿Ô--
K e V i N
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] [SQLite.ADO.Net] Upgrading XP to SQLite version?

2013-02-26 Thread Gilles Ganault 
On Tue, 26 Feb 2013 13:09:10 -0500, Kevin Benson
 wrote:
>Because there are actually a number of different ways the (CLR)untime
>locates assemblies, I ~believe~ the FAQ only attempts to offer a general
>advisement about the "Externals" folder as a *HINT*. The rest is up to the
>programmer.

Thanks for the link to MSDN, but it doesn't mention \Externals, so the
application won't find the other DLL since it's neither in the
application directory nor in the PATH.

Unless there's a better way to install the contents of the non-bundle
ZIP, I think the wiki should simply say that 1) it  contains two DLLs
(the non-managed SQLite DLL, and a managed .Net wrapper), and the
non-managed DLL must be located in a directory that the application
can find.

http://msdn.microsoft.com/en-us/library/823z9h8w.aspx
>in your app.config file in the 

I'll check it out.

Thank you.

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] [SQLite.ADO.Net] Upgrading XP to SQLite version?

2013-02-26 Thread Kevin Benson 
On Tue, Feb 26, 2013 at 11:34 AM, Gilles Ganault wrote:

> Next, just to check, I reinstalled a fresh Windows7 + VS Express 201
> to try the "Precompiled binaries no bundle" this time.
>
> Even with the VC++ 2012 runtime, it still complained about
> "SQLite.Interop.dll : The specified module could not be found".
>
> Turns out the wiki is half-wrong: When using the "no bundle" package,
> instead of using some "Externals" sub-directory,  it must be unpacked
> in either the Debug\Release directory or some location that's part of
> the PATH.


Because there are actually a number of different ways the (CLR)untime
locates assemblies, I ~believe~ the FAQ only attempts to offer a general
advisement about the "Externals" folder as a *HINT*. The rest is up to the
programmer.

http://msdn.microsoft.com/en-us/library/yx7xezcf(v=vs.110).aspx

You most likely would be fine with using the privatePath attribute of the
  element:

http://msdn.microsoft.com/en-us/library/823z9h8w.aspx

in your app.config file in the 


Cheers,
--
   --
  --
 --Ô¿Ô--
K e V i N
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] [SQLite.ADO.Net] Upgrading XP to SQLite version?

2013-02-26 Thread Gilles Ganault 
Next, just to check, I reinstalled a fresh Windows7 + VS Express 201
to try the "Precompiled binaries no bundle" this time.

Even with the VC++ 2012 runtime, it still complained about
"SQLite.Interop.dll : The specified module could not be found".

Turns out the wiki is half-wrong: When using the "no bundle" package,
instead of using some "Externals" sub-directory,  it must be unpacked
in either the Debug\Release directory or some location that's part of
the PATH.

http://system.data.sqlite.org/index.html/doc/trunk/www/faq.wiki#q8

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] [SQLite.ADO.Net] Upgrading XP to SQLite version?

2013-02-26 Thread Gilles Ganault 
On Tue, 26 Feb 2013 15:28:13 +0100, Gilles Ganault
 wrote:
>but it fails on the second line with "Type SQLiteCommand is not
>defined". Is there another component I need to install?

Got it: It just needs the following line at the top of the file:

Imports System.Data.SQLite

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] [SQLite.ADO.Net] Upgrading XP to SQLite version?

2013-02-26 Thread Gilles Ganault 
After installing "Visual Studio Express 2012 for Windows Desktop", I
downloaded and ran "Setups for 32-bit Windows (.Net Framework 4.5)
bundle 1.0.84.0".

I left the default option checked "Generate native images for the
assemblies and install the images in the native image cache", and
didn't check the other option ("Install the assemblied into the global
assembly cache" + "Install the designer components for Visual Studio
2012") since the design-time component is no longer supported for
Express editions.

Next, I created a new Windows Forms project, and tried adding a
reference to SQLite, but it wasn't listed in Assemblies >
Framework/Extension. So I tried running SQLite's installer.exe:
"Cannot continue, the "confirm" option is not enabled"

So, I used Project > Add Reference, hit "Browse", and pointed to
"System.Data.SQLite.DLL". Seemed OK.

Next, I ran the the following code, which worked OK:
=
Dim SQLconnect As New SQLite.SQLiteConnection()

SQLconnect.ConnectionString = "Data
Source=c:\users\joe\test.sqlite;"
SQLconnect.Open()
SQLconnect.Close()
=

Finally, I tried this code:
=
Dim SQLconnect As New SQLite.SQLiteConnection()
Dim SQLcommand As SQLiteCommand

SQLconnect.ConnectionString = "Data
Source=c:\users\fred\test.sqlite;"
SQLconnect.Open()
SQLcommand = SQLconnect.CreateCommand
SQLcommand.CommandText = "INSERT INTO Item (type) VALUES
('something')"
SQLcommand.ExecuteNonQuery()
SQLcommand.Dispose()
SQLconnect.Close()
=

but it fails on the second line with "Type SQLiteCommand is not
defined". Is there another component I need to install?

Thank you.

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] [SQLite.ADO.Net] Upgrading XP to SQLite version?

2013-02-26 Thread Gilles Ganault 
On Tue, 26 Feb 2013 04:08:26 -0500, Kevin Benson
 wrote:
>*(8) How do I install System.Data.SQLite on a development machine?*

Thanks, but I still want to understand what the difference is between
all the options in the Downloads page

>Strictly speaking, there is no need to install System.Data.SQLite on any
>development machine (e.g. via the setup).

Is "the setup" =  sqlite-netFx40-setup-??-x86-2010-1.0.84.0.exe?

If so, what is the Setup file for, then? Only if we want the
design-time components?

Also, the Bundle packages contain the "System.Data.SQLite.dll
mixed-mode assembly", which is the SQLite C code + the .Net wrapper
built into a single file, to be copied into the GAC.
The wiki says that this is needed "to support some legacy application
on customer machines". Why/when should I worry about other
applications?

>   - Add a reference to the "System.Data.SQLite" assembly from the
>   "Externals" directory.

Should I run the installer.exe that the ZIP contains, so that SQLite
is  registered and available from VB.Net Express?

>*(9) How do I install System.Data.SQLite on end-user machines?*
>
>[...] Installing the assemblies into the Global Assembly Cache
> is not recommended as it may cause conflicts with other
>applications installed on the machine.

Because those other applications might still depend on the Phoenix
version, which is incompatible with the new SQLite version?

Thank you.

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] [SQLite.ADO.Net] Upgrading XP to SQLite version?

2013-02-26 Thread Kevin Benson 
On Tue, Feb 26, 2013 at 3:43 AM, Gilles Ganault wrote:

> I'll uninstall the one from Phoenix Software Solutions, but I'm
> puzzled at which package to install from here:
>
> http://system.data.sqlite.org/index.html/doc/trunk/www/downloads.wiki
>

http://system.data.sqlite.org/index.html/doc/trunk/www/faq.wiki


>
> Which package should I use for...
> - a development host
>

*(8) How do I install System.Data.SQLite on a development machine?*

Strictly speaking, there is no need to install System.Data.SQLite on any
development machine (e.g. via the setup). The recommended way to use the
assemblies is:


   - Download the precompiled binary package for your target framework and
   processor architecture (e.g. 32-bit x86, .NET Framework 2.0).


   - Extract the package to a directory named "Externals" inside your
   project directory.


   - Add a reference to the "System.Data.SQLite" assembly from the
   "Externals" directory.


   - If necessary (i.e. you require LINQ support), also add a reference to
   the "System.Data.SQLite.Linq" assembly from the "Externals" directory.

Alternatively, when using Visual Studio 2010 or later, you can simply use
the NuGet package that corresponds to your target processor architecture.
Installing the assemblies into the Global Assembly Cache is not recommended
as it may cause conflicts with other applications installed on the machine.


> - a user host
> ?
>

*(9) How do I install System.Data.SQLite on end-user machines?*

Strictly speaking, there is no need to install System.Data.SQLite on any
end-user machine (e.g. via the setup). The recommended way to deploy the
assemblies is "application local" (i.e. copy them to the directory the
application is installed to). Installing the assemblies into the Global
Assembly Cache is not recommended as it may cause conflicts with other
applications installed on the machine.

--
   --
  --
 --Ô¿Ô--
K e V i N
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] [SQLite.ADO.Net] Upgrading XP to SQLite version?

2013-02-26 Thread Gilles Ganault 
On Mon, 25 Feb 2013 22:32:26 +, Simon Slavin
 wrote:
>There is no particular version of SQLite installed on your computer, and you 
>don't have to worry about downloading the latest version of SQLite.

I installed it to use SQLite with VB.Net, and would like to upgrade to
the latest version now that SQLite.Ado.Net is handled by the SQLite
team.

I'll uninstall the one from Phoenix Software Solutions, but I'm
puzzled at which package to install from here:

http://system.data.sqlite.org/index.html/doc/trunk/www/downloads.wiki

Which package should I use for...
- a development host
- a user host
?

Thank you.

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] [SQLite.ADO.Net] Upgrading XP to SQLite version?

2013-02-25 Thread Simon Slavin 

On 25 Feb 2013, at 2:18pm, Gilles Ganault  wrote:

>   I'm running the 32-bit version of XPSP3, whose "Add and Remove
> Programs" show that I have "QQLite ADO.NET 2*0/3.5 Provider 1.065.0"
> from Phoenix Software Solutions, LLC (http://sqlite.phxsoftware.com).
> 
> Now that SQLite.Ado.Net is handled by www.slite.org, what is the right
> way to upgrade to the latest and greatest? 

There is no particular version of SQLite installed on your computer, and you 
don't have to worry about downloading the latest version of SQLite.  Each 
program which uses SQLite might be using a different version of SQLite, and 
there is no real problem with this.  The version of SQLite.Ado.Net the program 
uses matters to you only if you are the programmer.  If you are a programmer 
you use whatever library is useful for your development platform when you 
compile your program.

If you are not a programmer then changing something about SQLite will do you no 
good.  If you can use an existing program use it.  If you can't you need a 
whole new program and it will do no good just to download a new SQLite 
component without changing the rest of the program.

So my guess is that at some point you have installed some program which uses 
the version of SQLite.Ado.Net you quote.  That would be the only reason to have 
it.  And the only people who need to worry about it are the programmers who 
wrote that program.

Simon.
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] [SQLite.ADO.Net] Upgrading XP to SQLite version?

2013-02-25 Thread Gilles Ganault 
On Mon, 25 Feb 2013 15:18:17 +0100, Gilles Ganault
 wrote:
>When do we need the design-time components? Which package should I use
>for development + deployment onto users' host?

I'm not clear about which package to install on a development host,
and which to install on a customer's host.

1. Here's what I thought I understood:

- Setups: Includes design-time component for VS 2005, and Visual C++
2005 SP1 runtime
- Precompiled Binaries:  The Visual C++ 2012 RTM runtime is not
included
- Precompiled Statically-Linked: The Visual C++ 2005 SP1 runtime for
x86 is statically linked

Setups should only be installed on developer's host, and only if we
actually need the design-time components.
The Precompiled binaries should be  installed on the customer's host
through xcopy.
Use the static packages if the customer doesn't have admin rights to
install the VC++ runtime

Each package is available in two versions:
- bundle = "mixed-mode assembly + all the binaries"; mixed-mode
assembly only necessary when the binary assembly must be installed in
the GAC
- no-bundle = "all the binaries"

2. And here are the questions:
- What does the design-time component offer?

- What applications rely on the binary assembly in the GAC, and hence,
require installing the bundle packages?

3. Am I correct in understanding that the "no-bundle Precompiled
binaries" are usually the right choice, provided the customer can
install the VC++ runtime?

Thank you.

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] [SQLite.ADO.Net] Upgrading XP to SQLite version?

2013-02-25 Thread Gilles Ganault 
Hello

I'm running the 32-bit version of XPSP3, whose "Add and Remove
Programs" show that I have "QQLite ADO.NET 2*0/3.5 Provider 1.065.0"
from Phoenix Software Solutions, LLC (http://sqlite.phxsoftware.com).

Now that SQLite.Ado.Net is handled by www.slite.org, what is the right
way to upgrade to the latest and greatest? 

The wiki says:

"1. The setup packages are intended to be installed only on developer
machines and then only when the design-time components for Visual
Studio are required. In theory, they can be installed on customer
machines as well; however, this type of deployment is not recommended.

2. The binary packages are intended to be used by developers in order
to obtain the assembly binaries necessary for development and
deployment of their applications onto customer machines via XCOPY
deployment. [...]
Using XCOPY deployment in conjunction with the native library
pre-loading feature, especially for customer machines, is highly
recommended."
http://system.data.sqlite.org/index.html/doc/trunk/www/downloads.wiki

When do we need the design-time components? Which package should I use
for development + deployment onto users' host?

Thank you.

___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users