Your project should start with a VistaDB database which you can deploy with your application as a starting point for users. You can create this database several ways:
If You... | Start With.. |
---|---|
Have an existing SQL Server, Microsoft Access, or SQL CE Database | Migrate the database schema to VistaDB with the Data Migration Wizard |
Want to do everything within Visual Studio | Use the Visual Studio Server Explorer to create a new VistaDB database and edit the schema |
Want to create your database independently of Visual Studio | Use Data Builder to create a new VistaDB database, edit and test the Schema |
For more information on each of these options, see Getting Started - Creating A Database.
Once you have your initial database its time to connect it to your application:
If You... | Start With... |
---|---|
Have an existing application developed for SQL Server | Converting a SQL Server Application to VistaDB |
Are using .NET 4.0 or later and want to autogenerate your Data Access code | Using VistaDB with Entity Framework |
Want to create your own data access layer | Using VistaDB directly with ADO.NET |
Now that you've tested it locally it's time to deploy your application. To have a successful deployment:
You should also add diagnostic support so you can monitor the performance and use of your application. The VistaDB engine exposes a logging interface which you can use to record information as the engine runs. The easiest way to do this is to take advantage of the free Loupe Agent and the Loupe Agent for VistaDB. This solution gives you a free way to capture diagnostic information about how your entire application runs and performs as well as detailed information on VistaDB.
If you are using VistaDB 5 or earlier, check out Getting Started - Upgrading to VistaDB 6 for a step-by-step approach to upgrading your existing applications.
If you are upgrading Entity Framework along with VistaDB, review Using VistaDB with Entity Framework - Upgrading To Entity Framework 6 for a step-by-step approach.