changing the native lib package from SQLitePCLRaw.lib.e_sqlite3 to SourceGear.sqlite3

Author: ericsink

README.md

@@ -35,10 +35,11 @@ with technical support questions, I may not respond.
 
 # SQLite Builds
 
-The SQLitePCLRaw.lib.e_sqlite3 package is published publicly on nuget.org 
-as part of this project.  It contains builds of the native SQLite code library
-for server platforms and with the most commonly used features enabled.
-I update this package from time to time.
+For use with SQLitePCLRaw, the nuget package `SourceGear.sqlite3` contains 
+builds of the native SQLite code library for most platforms, and with the 
+most commonly used features enabled.  The version of this package available
+publicly on nuget.org is updated periodically but may not always contain 
+the latest version of SQLite.
 
 SourceGear operates a paid service at nuget.sourcegear.com
 which provides various native SQLite builds which are
@@ -163,7 +164,7 @@ recent builds of Windows.
 instead of DllImport attributes.  This can be used to support
 advanced use cases.
 
-# SQLitePCLRaw.lib.e\_sqlite3
+# SourceGear.sqlite3
 
 A provider is the bridge between the core assembly and the native
 code, but the provider does not contain the native code itself.
@@ -176,7 +177,7 @@ But in cases where the app is going to be bundling the native
 code library, those bits need to make it into your build output
 somehow.
 
-For the convenience of developers using SQLitePCLRaw, the `SQLitePCLRaw.lib.e_sqlite3` 
+For the convenience of developers using SQLitePCLRaw, the `SourceGear.sqlite3` 
 package contains builds of the native SQLite code for several platforms.
 The build configuration is the same for every platform, and includes
 full-text-search.  
@@ -191,7 +192,7 @@ packages:
 
 And in many cases, you also need a package containing the native SQLite library itself.  For example:
 
-- SQLitePCLRaw.lib.e_sqlite3
+- SourceGear.sqlite3
 
 Then, in your platform-specific code, you need to call:
 
@@ -220,13 +221,13 @@ do that, because there are multiple possibilities, and it wants to defer
 the choice until later.
 
 If you want to use a plain SQLite library with the most commonly used
-features, just add the "SQLitePCLRaw.lib.e_sqlite3" package.
+features, just add the "SourceGear.sqlite3" package.
 
 For backward compatibility with previous releases, the SQLitePCLRaw.bundle_e_sqlite3
 package continues to be available, but all it does is bring in two dependencies:
 
 - SQLitePCLRaw.config.e_sqlite3
-- SQLitePCLRaw.lib.e_sqlite
+- SourceGear.sqlite3
 
 ## How do I build SQLitePCLRaw?
 

src/SQLitePCLRaw.bundle_e_sqlite3/SQLitePCLRaw.bundle_e_sqlite3.csproj

@@ -17,7 +17,7 @@
   </ItemGroup>
 
   <ItemGroup>
-	<PackageReference Include="SQLitePCLRaw.lib.e_sqlite3" Version="$(lib_e_sqlite3_package_reference_version)" />
+	<PackageReference Include="SourceGear.sqlite3" Version="$(lib_e_sqlite3_package_reference_version)" />
   </ItemGroup>
 
 </Project>

v3.md

@@ -11,8 +11,9 @@
 
 - Support for classic Xamarin has been removed.
 - A new package called SQLitePCLRaw.config.e_sqlite3 has been added.  This is identical to .bundle_e_sqlite3, except with no dependency on a native SQLite lib package, thus allowing the flexibility to choose a different one.
-- For backward compatibility, .bundle_e_sqlite3 is still supported, and has been redefined to be nothing more than two package dependencies: .config.e_sqlite3 and .lib.e_sqlite3.
-- The version number of the SQLitePCLRaw.lib.e_sqlite3 package now matches the version of SQLite used to build it, not the version of SQLitePCLRaw.  In general, I will no longer increment the version number of SQLitePCLRaw just to incorporate an updated SQLite version.
+- The package containing the native SQLite library is now `SourceGear.sqlite3` instead of `SQLitePCLRaw.lib.e_sqlite3`.
+- For backward compatibility, .bundle_e_sqlite3 is still supported, and has been redefined to be nothing more than two package dependencies: SQLitePCLRaw..config.e_sqlite3 and SourceGear.sqlite3.
+- The version number of SQLite native library packages (such as `SourceGear.sqlite3`) now matches the version of SQLite used to build it, not the version of SQLitePCLRaw.  In general, I will no longer increment the version number of SQLitePCLRaw just to incorporate an updated SQLite version.
 - My recommended solution for SQLite encrypton is now the SQLite Encryption Extension (SEE), available from the SQLite core team.
 - SourceGear (my company) is now offering paid serices around .NET and SQLite, including technical support agreements, maintenance of SQLite builds with a private nuget server, and custom software development.
 - I no longer distribute any no-cost SQLite builds with encryption.  SQLCipher builds are available for purchase from Zetetic, and I will continue to coordinate with them to ensure compatibility.  Builds for SEE and SQLite3 Multiple Ciphers are available as part of SourceGear's SQLite build service.