Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | More updates to 'the wiki pages. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
0dea92ccd70d027caf0bec4742705e46 |
User & Date: | shaneh 2011-04-12 20:23:24.385 |
Context
2011-04-12
| ||
20:24 | Official 3.7.6 source files. check-in: 8436c6dd92 user: shaneh tags: trunk | |
20:23 | More updates to 'the wiki pages. check-in: 0dea92ccd7 user: shaneh tags: trunk | |
19:55 | Change default build configuration back to VS 2008. Please note that, by default, VC++ 2008 Express (or better) is required to use the build.bat tool. check-in: 7856d2e9ff user: mistachkin tags: trunk | |
Changes
Changes to www/build.wiki.
︙ | ︙ | |||
184 185 186 187 188 189 190 | bake_all.bat </li> <li>Make sure everything succeeds with no errors. InnoSetup should produce "success" messages very similar to the following: | | | 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 | bake_all.bat </li> <li>Make sure everything succeeds with no errors. InnoSetup should produce "success" messages very similar to the following: Successful compile (X.XXX sec). Resulting Setup program filename is: abc </li> </ol> <a name="build.bat"></a> <h3>build.bat Desription</h3> <p> |
︙ | ︙ |
Changes to www/features.wiki.
︙ | ︙ | |||
8 9 10 11 12 13 14 | base classes and features recently introduced in the framework, including automatic transaction enlistment. </li> <li> Supports the Full and Compact .NET Framework, and native C/C++ development. 100% binary | | | 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 | base classes and features recently introduced in the framework, including automatic transaction enlistment. </li> <li> Supports the Full and Compact .NET Framework, and native C/C++ development. 100% binary compatible with the original sqlite3.dll.<br /> <font color="red">Compact framework not currently not included. We hope to have this feature included again soon.</font> </li> <li> Full support for Mono via a "managed only" provider that runs against the official SQLite 3.6.1 or higher library. |
︙ | ︙ | |||
36 37 38 39 40 41 42 | support both binary and cleartext password types. </li> <li> Visual Studio 2005/2008 Design-Time Support, works with all versions of VS2005/2008, including all Express Editions of VS2005. You can add a SQLite database to the Servers list, design queries with the Query Designer, | | | | | 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 | support both binary and cleartext password types. </li> <li> Visual Studio 2005/2008 Design-Time Support, works with all versions of VS2005/2008, including all Express Editions of VS2005. You can add a SQLite database to the Servers list, design queries with the Query Designer, drag-and-drop tables onto a Typed DataSet, etc.<br /> <font color="red">Currently not included. We are still updating the Design-Time support installer.</font> </li> <li> Full SQLite schema editing inside Visual Studio. You can create/edit tables, views, triggers, indexes, check constraints and foreign keys. </li> <li> Single file redistributable (except on Compact Framework). The core sqlite3 codebase and the ADO.NET wrapper are combined into one multi-module assembly.<br /> <font color="red">Currently all versions provided as System.Data.SQLite.dll and SQLite.Interop.dll. This provides consistency across all packages, including Compact and Mono.</font> </li> <li> Binaries included for Itanium, x64, x86 and ARM processors.<br /> <font color="red">Currently only x64 and x86 included. We hope to have more processors included again soon.</font> </li> <li> DbProviderFactory support. </li> |
︙ | ︙ |
Changes to www/index.wiki.
︙ | ︙ | |||
13 14 15 16 17 18 19 | <li>[./release.wiki | Release Procedures]</li> </ul> </td> </tr> </table> <p> | | | 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 | <li>[./release.wiki | Release Procedures]</li> </ul> </td> </tr> </table> <p> This is a fork of the popular ADO.NET 2.0 adaptor for <a href="http://www.sqlite.org">SQLite</a> known as System.Data.SQLite. The originator of System.Data.SQLite, Robert Simpson, is aware of this fork, has expressed his approval, and has commit privileges on the new Fossil repository. The SQLite development team intends to maintain System.Data.SQLite moving forward. </p> <p> Historical versions, as well as the original support forums, may still be found |
︙ | ︙ |
Changes to www/release.wiki.
1 2 | <title>Release Procedures</title> | | | > | > > | < < < < < < < < | | < < | | < < | | < < < > > | > > > | < | | < < < < | > | < | < < < | | > > > > | < < | | | < | > > > > | | | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 | <title>Release Procedures</title> <h2>Release Procedures</h2> <p>Follow these steps to prepare a new release of System.Data.SQLite. Unless otherwise noted, all steps need to be done in the order specified.</p> <ol type="A"> <li> <b>Build Runtime Packages</b> <ul> 1. [./build.wiki | Build] the runtime and design time components, and setup package.<br /> 2. Copy the and rename the resulting setup.exe to sqlite-dotnet-1xxyyzz.exe<br /> </ul> </li> <li> <b>Build Source Package</b> <ul> 1. Get a fresh checkout of the "dotnet" Fossil repository.<br /> 2. Run fossil close to remove the _FOSSIL_ file.<br /> 3. Remove the bin, obj, and Externals directories.<br /> 4. Rename the subdirectory to sqlite-dotnetsrc-1xxyyzz<br /> 5. Package this subdirectory as sqlite-dotnetsrc-1xxyyzz.zip<br /> 6. Move the ZIP archive to the doc/ folder of the build area.<br /> </ul> </li> <li> <b>Update documentation</b> <font color="red">This section needs updating.</font> <ul> 1. Update the readme.htm file with the latest version changes<br /> 2. Copy the version changes from readme.htm into doc\extra\version.html<br /> 3. Update doc\extra\dbfactorysupport.html to reflect the latest version # of the DLL<br /> 4. Copy over doc\extra\dbfactorysupport.html and version.html to my temp ndoc2 location where all my intermediate files are for the CHM<br /> 5. Run HTML Help Workshop on the HHP project to get my CHM<br /> 6. Copy the CHM file over to \doc<br /> </ul> </li> <li> <b>Publish the release</b> <ul> 1. Update the news.wiki page and the downloads.wiki page.<br /> 2. Tag the release in Fossil.<br /> 3. Upload the distributables.<br /> 4. Announce the release on the mailing list.<br /> </ul> </li> </ol> |