System.Data.SQLite

Check-in [ab0469b468]
Login

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

Overview
Comment:Tweak information on the native library pre-loading feature.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: ab0469b4685eea1d51cadf54dd0335d1817da5b4
User & Date: mistachkin 2012-09-17 04:05:49.170
Context
2012-09-17
04:13
Allow the setup package for Visual Studio 2008 to install the design-time components for Visual Studio 2005. check-in: 65a35f7847 user: mistachkin tags: trunk
04:05
Tweak information on the native library pre-loading feature. check-in: ab0469b468 user: mistachkin tags: trunk
03:52
Fix timeline links. check-in: 71d7ede107 user: mistachkin tags: trunk
Changes
Side-by-Side Diff Ignore Whitespace Patch
Changes to www/downloads.wiki.
︙
162
163
164
165
166
167
168
169
170


171
172
173
174
175
176
177

162
163
164
165
166
167
168


169
170
171
172
173
174
175
176
177








-
-
+
+








         
      </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 automatically detect the processor architecture of the current
        process and attempt to pre-load the appropriate native library.
        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>
︙
206
207
208
209
210
211
212
213


214
215
216
217
218
219
220

206
207
208
209
210
211
212

213
214
215
216
217
218
219
220
221








-
+
+








            Choosing the package matching the version of the .NET Framework
            being targeted is highly recommended.
          </li>
          <br />
          <li>
            Choosing the package matching the target processor architecture (for
            both development and customer machines) is almost certainly required
            for proper operation.
            for proper operation.  Using the native library pre-loading feature
            should help with this.
          </li>
        </ul>
      </td>
      <td>
        &nbsp;
      </td>
    </tr>
︙