Enter the following commands to build all the binaries available for Windows
Embedded Compact 2013:

SET BUILD_FULL=1SET BUILD_DEBUG=1build_ce_2013.bat

This assumes that Visual Studio 2012, "Professional"
edition or "better" and the Windows Embedded Compact 2013 Toolkit
are installed.

Make sure everything succeeds with no errors; the console output may be
checked if any errors should occur.

Test Windows CE Binaries via Automation

Instead of testing the Windows CE binaries
manually as described in the next
section, the following steps may be used.

Open a normal command prompt window with "cmd.exe".

Change the current directory to "<root>\Setup".

Enter the following commands to test all the binaries available for Windows
CE:

SET TEST_DEBUG=1test_ce_200x.bat

Make sure everything succeeds with no errors; the console output may be
checked if any errors should occur.

Test Windows CE Binaries Manually

If the Windows CE binaries were already tested using the
automation described in the previous
section, skip this section.

Launch Visual Studio 2005, "Professional" edition or
"better" with the bundled Pocket PC 2003 SDK. As of this writing,
in January 2012, Visual Studio 2010 and later will not work as they
do not include the necessary built-in support for Windows CE and the .NET
Compact Framework.

Open the "SQLite.NET.2008.sln" solution file in the
"<root>" directory.

Change the active solution configuration to "Debug".

Change the active solution platform to "Pocket PC 2003
(ARMV4)".

Right-click the "testce" project in the Solution Explorer
window and select "Set as StartUp Project".

Select "Start Debugging" from the "Debug"
menu.

If any rebuild prompts appear (e.g. "SQLite.Interop.CE.2008",
"Would you like to build it?"), select "Yes".

When prompted for the device type to deploy the application to, select the
"Pocket PC 2003 SE Emulator" device.

Make sure all that the tests pass (i.e. they emit "SUCCESS").

Build Mono Binaries

Open a normal command prompt window with "cmd.exe".

Change the current directory to "<root>\Setup".

Enter the following commands to build all the binaries available for Mono:

SET BUILD_FULL=SET BUILD_DEBUG=1build_mono.bat

Make sure everything succeeds with no errors; the console output may be
checked if any errors should occur.

Build .NET Standard 2.0 Binaries

Open a normal command prompt window with "cmd.exe".

Change the current directory to "<root>\Setup".

Enter the following commands to build all the binaries available for .NET
Standard 2.0:

SET BUILD_FULL=SET BUILD_DEBUG=1build_net_standard_20.bat

Make sure everything succeeds with no errors; the console output may be
checked if any errors should occur.

Test .NET Standard 2.0 Binaries

Open a normal command prompt window with "cmd.exe".

Change the current directory to "<root>\Setup".

Enter the following commands to test all the binaries available for .NET
Standard 2.0:

SET TEST_DEBUG=1test_net_standard_20.bat

Make sure everything succeeds with no errors; the console output may be
checked if any errors should occur.

Update Documentation

Update the "<root>\readme.htm" file with information about
all the major changes since the last released version.

Copy those changes to the
"<root>\Doc\Extra\Provider\version.html" and
"<root>\www\news.wiki" files, reformatting as necessary
to fit with the existing document conventions.

Change the current directory to "<root>\Doc".

Enter the following command to update all documentation that is
included from upstream (e.g. from the SQLite core library, etc):

This assumes that the Fossil,
Inno Setup Unpacker,
UnRAR, and
UnZip binaries are available in the
locations specified via the "FossilTool",
"InnoUnpackTool", "UnRARTool", and "UnZipTool"
environment variables, respectively.

Make sure everything succeeds with no errors; the console output may be
checked if any errors should occur.

If errors are generated, the file
"<root>\Setup\data\verify.lst" may need to be updated to
account for the files that have been added and/or removed from the release
archives since the previous release.

Update Downloads Page

Open a normal command prompt window with "cmd.exe".

Change the current directory to "<root>\Setup".

Replace the version numbers for the previous release in the local working
copy of the downloads page with the new version numbers
for System.Data.SQLite and the SQLite core.

Enter the following command to update the sizes and hashes on the downloads
page based on all the built release packages:

tclsh.exe updateFileInfo.tcl

This assumes that ActiveTcl
version 8.4 or later has been installed using the default settings and that
the Fossil binary is available somewhere along the
PATH (i.e. for
calculating the SHA1 hashes).

Make sure everything succeeds with no errors; the console output may be
checked if any errors should occur.