System.Data.SQLite
Check-in [99ce814fe6]
Not logged in

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:More updates to the download page.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: 99ce814fe6f7bc9c8ef6bec3364f591f9dbf40a1
User & Date: mistachkin 2012-09-17 12:46:22
Context
2012-09-18
08:39
Simplify the file/assembly versioning tests and add several more assemblies to be verified. check-in: 8727b0b87e user: mistachkin tags: trunk
2012-09-17
12:46
More updates to the download page. check-in: 99ce814fe6 user: mistachkin tags: trunk
11:32
Add more support notes to the download page. check-in: cd74429503 user: mistachkin tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to www/downloads.wiki.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
..
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
...
130
131
132
133
134
135
136
137
138
139
140
141


142
143
144
145
146
147
148
...
175
176
177
178
179
180
181
182


183
184
185
186
187
188

189
190



191
192
193
194
195
196
197
<title>System.Data.SQLite Download Page</title>
<nowiki>
  <h3>System.Data.SQLite Download Page</h3>

  <table width="100%" cellpadding="5">
    <tr>
      <td colspan="3">
        <b>Support Notes</b>
      </td>
    </tr>

    <tr>
      <td colspan="3" class="importantNotes">
        This page contains all the downloadable packages (e.g. sources,
................................................................................
        question is related to the core SQLite native library itself, one of the
        <a href="http://www.sqlite.org/support.html">SQLite support options</a>
        is probably the best way to get an answer.
      </td>
    </tr>

    <tr>
      <td colspan="3">
        <b>Package Types</b>
      </td>
    </tr>

    <tr>
      <td colspan="3" class="importantNotes">
        There are a wide variety of downloadable packages on this page.
................................................................................
        code compiled for x86 (e.g. the &quot;System.Data.SQLite.dll&quot;
        mixed-mode assembly, the &quot;SQLite.Interop.dll&quot; native interop
        assembly, or the &quot;sqlite3.dll&quot; native library) to fail to
        load, typically resulting in a
        <a href="faq.wiki#q12">BadImageFormatException</a> being thrown.
        <br /><br />
        If the development and customer machines may have different processor
        architectures, more than one binary package may be required.  In this
        case, using the native library pre-loading feature is recommended.  It
        is available as of version 1.0.80.0 and enabled by default.  In order to
        take advantage of this feature, the separate native and managed
        assemblies must be used with XCOPY deployment, resulting in an


        application deployment that looks something like this:
      </td>
    </tr>
    <tr>
      <td>
        &nbsp;
      </td>
................................................................................
        </ul>
      </td>
      <td>
        &nbsp;
      </td>
    </tr>
    <tr>
      <td colspan="3">


        With the native library pre-loading feature enabled and the application
        deployment shown above, the System.Data.SQLite managed-only assembly
        will attempt to automatically detect the processor architecture of the
        current process and pre-load the appropriate native library.
        <br /><br />
        If this feature does not work properly in your environment, it may be

        disabled by setting the &quot;No_PreLoadSQLite&quot; environment
        variable prior to loading and/or using the System.Data.SQLite assembly.



        <br /><br />
        To summarize the above:
      </td>
    </tr>
    <tr>
      <td>
        &nbsp;


|



|







 







|







 







|
|
|
|
|
>
>







 







|
>
>





|
>
|
|
>
>
>







1
2
3
4
5
6
7
8
9
10
11
12
13
14
..
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
...
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
...
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
<title>System.Data.SQLite Download Page</title>
<nowiki>
  <h1>System.Data.SQLite Download Page</h1>

  <table width="100%" cellpadding="5">
    <tr>
      <td colspan="3" class="importantHeader">
        <b>Support Notes</b>
      </td>
    </tr>

    <tr>
      <td colspan="3" class="importantNotes">
        This page contains all the downloadable packages (e.g. sources,
................................................................................
        question is related to the core SQLite native library itself, one of the
        <a href="http://www.sqlite.org/support.html">SQLite support options</a>
        is probably the best way to get an answer.
      </td>
    </tr>

    <tr>
      <td colspan="3" class="importantHeader">
        <b>Package Types</b>
      </td>
    </tr>

    <tr>
      <td colspan="3" class="importantNotes">
        There are a wide variety of downloadable packages on this page.
................................................................................
        code compiled for x86 (e.g. the &quot;System.Data.SQLite.dll&quot;
        mixed-mode assembly, the &quot;SQLite.Interop.dll&quot; native interop
        assembly, or the &quot;sqlite3.dll&quot; native library) to fail to
        load, typically resulting in a
        <a href="faq.wiki#q12">BadImageFormatException</a> being thrown.
        <br /><br />
        If the development and customer machines may have different processor
        architectures, more than one binary package may be required.  For this
        situation, using the <b>native library pre-loading feature</b> is highly
        recommended.  It is available as of version 1.0.80.0 and enabled by
        default.  In order to take advantage of this feature, the separate
        managed and interop assemblies <b>must</b> be used with XCOPY deployment
        (i.e. this feature is not supported by the mixed-mode assembly, nor when
        the assembly is deployed to the global assembly cache), resulting in an
        application deployment that looks something like this:
      </td>
    </tr>
    <tr>
      <td>
        &nbsp;
      </td>
................................................................................
        </ul>
      </td>
      <td>
        &nbsp;
      </td>
    </tr>
    <tr>
      <td colspan="3" class="importantNotes">
        The string &quot;<b>&lt;bin&gt;</b>&quot; above represents the directory
        where the application binaries are to be deployed on the target machine.
        With the native library pre-loading feature enabled and the application
        deployment shown above, the System.Data.SQLite managed-only assembly
        will attempt to automatically detect the processor architecture of the
        current process and pre-load the appropriate native library.
        <br /><br />
        If native library pre-loading feature does not work properly in your
        environment, it can be disabled by setting the
        &quot;No_PreLoadSQLite&quot; environment variable (i.e. to anything)
        prior to loading and/or using the System.Data.SQLite assembly.  There
        are several more environment variables that can be used to influence the
        behavior of the native library pre-loading feature, documented
        <a href="/index.html/artifact?ci=trunk&filename=Doc/Extra/environment.html">here</a>.
        <br /><br />
        To summarize the above:
      </td>
    </tr>
    <tr>
      <td>
        &nbsp;