Access 也可以做到这一点，大多数企业已经将其作为 Microsoft Office 的一部分安装，尽管您不需要安装它来使用 Odbc 或 OleDb 程序集GAC 的。
I think SQLite could do the trick, as it is a filesystem-based database, so no installation required.
Access could also do the trick, and most of businesses have it already installed as part of Microsoft Office, though you wouldn't need it to be installed in order to use the Odbc or OleDb assemblies that are part of the GAC.
这里的关键是你需要什么样的数据库。该数据库是否要在应用程序的多个用户之间共享？如果是这样，那么 MySQL 就可以了。
但这听起来更像是您打算将此数据库用作私有数据存储，其中每个已安装的应用程序实例都拥有该计算机或配置文件本地的自己的数据。在这种情况下，您需要一个进程内引擎，例如 Sql Server Compact Edition、Sqlite，甚至 Access，而不是像 MySql 或 Sql Server Express Edition 这样的服务器级引擎。
The key here is what kind of database you need. Is this database to be shared among several users of the app? If so, than MySQL would be fine.
But it sounds more like you intend to use this database as a private data store, where each installed instance of the application has it's own data local to that machine or profile. In that case, you want an in-process engine like Sql Server Compact Edition, Sqlite, or even Access rather than a server-class engine like MySql or Sql Server Express Edition.
SQL Server Express 是另一种选择。与 .NET 完美集成，免费安装，每个数据库支持高达 10GB（如果使用 Filestream 功能，则支持更多）。
SQL Server Express is another option. Has excellent integration with .NET, free to install and supports upto 10GB per database (or more if you use the Filestream feature).
发布评论
评论（7）
查看 SQL Server Compact 3.5
Take a look at SQL Server Compact 3.5
Sqlite 非常简单。您只需将 DLL 与您的应用程序一起部署即可。由于缺乏信息，我无法判断它是否适合您的情况。
Sqlite is very simple. You just deploy the DLL with your app. I can't tell how appropriate it is for your situation, given the lack of info.
我认为
SQLite可以做到这一点，因为它是一个基于文件系统的数据库，因此无需安装。Access也可以做到这一点，大多数企业已经将其作为 Microsoft Office 的一部分安装，尽管您不需要安装它来使用 Odbc 或 OleDb 程序集GAC 的。I think
SQLitecould do the trick, as it is a filesystem-based database, so no installation required.Accesscould also do the trick, and most of businesses have it already installed as part of Microsoft Office, though you wouldn't need it to be installed in order to use the Odbc or OleDb assemblies that are part of the GAC.这里的关键是你需要什么样的数据库。该数据库是否要在应用程序的多个用户之间共享？如果是这样，那么 MySQL 就可以了。
但这听起来更像是您打算将此数据库用作私有数据存储，其中每个已安装的应用程序实例都拥有该计算机或配置文件本地的自己的数据。在这种情况下，您需要一个进程内引擎，例如 Sql Server Compact Edition、Sqlite，甚至 Access，而不是像 MySql 或 Sql Server Express Edition 这样的服务器级引擎。
The key here is what kind of database you need. Is this database to be shared among several users of the app? If so, than MySQL would be fine.
But it sounds more like you intend to use this database as a private data store, where each installed instance of the application has it's own data local to that machine or profile. In that case, you want an in-process engine like Sql Server Compact Edition, Sqlite, or even Access rather than a server-class engine like MySql or Sql Server Express Edition.
我认为，嵌入式 DBMS 是最适合您的方法。例如，您可以使用 Firebird 嵌入式
I think, that an embedded DBMS is the best way for yor. For example, you can use Firebird Embedded
SQL Server 2008 Express 可供 ISV 重新分发。您还可以使用 Microsoft Web Platform Installer 进行部署。
SQL Server 2008 Express is available for redistribution by ISVs. You an also deploy this using Microsoft Web Platform Installer.
SQL Server Express 是另一种选择。与 .NET 完美集成，免费安装，每个数据库支持高达 10GB（如果使用 Filestream 功能，则支持更多）。
SQL Server Express is another option. Has excellent integration with .NET, free to install and supports upto 10GB per database (or more if you use the Filestream feature).