System.Data.SQLite
Check-in [ab0469b468]
Not logged in

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 | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: ab0469b4685eea1d51cadf54dd0335d1817da5b4
User & Date: mistachkin 2012-09-17 04:05:49
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
Hide Diffs Side-by-Side Diffs Ignore Whitespace Patch

Changes to www/downloads.wiki.

   162    162            
   163    163         </td>
   164    164       </tr>
   165    165       <tr>
   166    166         <td colspan="3">
   167    167           With the native library pre-loading feature enabled and the application
   168    168           deployment shown above, the System.Data.SQLite managed-only assembly
   169         -        will automatically detect the processor architecture of the current
   170         -        process and attempt to pre-load the appropriate native library.
          169  +        will attempt to automatically detect the processor architecture of the
          170  +        current process and pre-load the appropriate native library.
   171    171           <br /><br />
   172    172           If this feature does not work properly in your environment, it may be
   173    173           disabled by setting the &quot;No_PreLoadSQLite&quot; environment
   174    174           variable prior to loading and/or using the System.Data.SQLite assembly.
   175    175           <br /><br />
   176    176           To summarize the above:
   177    177         </td>
................................................................................
   206    206               Choosing the package matching the version of the .NET Framework
   207    207               being targeted is highly recommended.
   208    208             </li>
   209    209             <br />
   210    210             <li>
   211    211               Choosing the package matching the target processor architecture (for
   212    212               both development and customer machines) is almost certainly required
   213         -            for proper operation.
          213  +            for proper operation.  Using the native library pre-loading feature
          214  +            should help with this.
   214    215             </li>
   215    216           </ul>
   216    217         </td>
   217    218         <td>
   218    219           &nbsp;
   219    220         </td>
   220    221       </tr>