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

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

Overview
Comment:Improve section divisions.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: b12794843a33e181ea4fde9678274cf7253164be
User & Date: mistachkin 2013-07-19 21:32:55
Context
2013-07-25
08:23
Enable better integration with external native libraries to be linked with the interop assembly. check-in: 52cb9b7778 user: mistachkin tags: trunk
2013-07-19
21:32
Improve section divisions. check-in: b12794843a user: mistachkin tags: trunk
21:11
Another style fix. check-in: 8a77334646 user: mistachkin tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to www/downloads.wiki.

134
135
136
137
138
139
140
141










142
143
144
145
146
147
148
...
214
215
216
217
218
219
220
221










222
223
224
225
226
227
228
        being targeted by the application.
        In theory, assembly binaries for the
        <a href="http://go.microsoft.com/fwlink/?LinkID=32168">.NET Framework
        2.0</a> will work with the
        <a href="http://go.microsoft.com/fwlink/?LinkID=186913">.NET Framework
        4.0</a>; however, this is not ideal.  Furthermore, assemblies compiled
        for the .NET Framework 4.0 cannot be loaded by the .NET Framework 2.0.
        <br /><br />










        The final step is to identify the target processor architecture on both
        the development and customer machines.  Generally,
        <a href="http://en.wikipedia.org/wiki/X86">x86</a> binaries will work on
        an <a href="http://en.wikipedia.org/wiki/X64">x64</a> machine running
        <a href="http://en.wikipedia.org/wiki/Windows">Windows</a> (using
        <a href="http://en.wikipedia.org/wiki/WoW64">WoW64</a>).  However, there
        is a problem when using managed code.  If the executable that starts the
................................................................................
        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;
      </td>







|
>
>
>
>
>
>
>
>
>
>







 







|
>
>
>
>
>
>
>
>
>
>







134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
...
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
        being targeted by the application.
        In theory, assembly binaries for the
        <a href="http://go.microsoft.com/fwlink/?LinkID=32168">.NET Framework
        2.0</a> will work with the
        <a href="http://go.microsoft.com/fwlink/?LinkID=186913">.NET Framework
        4.0</a>; however, this is not ideal.  Furthermore, assemblies compiled
        for the .NET Framework 4.0 cannot be loaded by the .NET Framework 2.0.
      </td>
    </tr>

    <tr>
      <td colspan="3" class="importantHeader">
        <b>Using Native Library Pre-Loading</b>
      </td>
    </tr>

    <tr>
      <td colspan="3" class="importantNotes">
        The final step is to identify the target processor architecture on both
        the development and customer machines.  Generally,
        <a href="http://en.wikipedia.org/wiki/X86">x86</a> binaries will work on
        an <a href="http://en.wikipedia.org/wiki/X64">x64</a> machine running
        <a href="http://en.wikipedia.org/wiki/Windows">Windows</a> (using
        <a href="http://en.wikipedia.org/wiki/WoW64">WoW64</a>).  However, there
        is a problem when using managed code.  If the executable that starts the
................................................................................
        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>.
      </td>
    </tr>

    <tr>
      <td colspan="3" class="importantHeader">
        <b>Deployment Guidelines</b>
      </td>
    </tr>

    <tr>
      <td colspan="3" class="importantNotes">
        To summarize the above:
      </td>
    </tr>
    <tr>
      <td>
        &nbsp;
      </td>