Sqlite browser erikej code#

The server side of the application is up and running and CRUD operations function with an MVC 6 application using Entity Framework code first with SQLite.Ī simple angular client application has been created to test the CRUD operations. Services.AddMvc().AddJsonOptions(options => The DefaultContractResolver needs to be set if your using Pascal case json. The default IoC from ASP.NET 5 is used to define the dependencies in the startup class. _dataEventRecordRepository.Put(id, value) Public void Put(long id, DataEventRecord value) Return _dataEventRecordRepository.Get(id) Return _dataEventRecordRepository.GetAll() _dataEventRecordRepository = dataEventRecordRepository Public DataEventRecordsController(IDataEventRecordRepository dataEventRecordRepository) Private readonly IDataEventRecordRepository _dataEventRecordRepository Public class DataEventRecordsController : Controller The repository is used in the MVC controller: Public void Put(long id, DataEventRecord dataEventRecord) Public void Post(DataEventRecord dataEventRecord ) _logger.LogCritical('Getting a the existing records')

_logger = loggerFactory.CreateLogger('IDataEventRecordResporitory') Public DataEventRecordRepository(DataEventRecordContext context, ILoggerFactory loggerFactory) Private readonly DataEventRecordContext _context Public class DataEventRecordRepository : IDataEventRecordRepository A simple repository has been created for the CRUD operations. This can be checked using SQLite Manager in Firefox: Run the application and the database will be created. This will create a new Migrations folder with the generated classes. Due to this, you need to use the old project.json file as well as the global.json to do the migrations from the command line using dotnet. Note: At present the EF Core migrations do not work with msbuild. Open the command line and execute the following command in the src directory of the application. Now the database can be created using EF migrations. 'SqliteConnectionString': 'Data Source=C:\git\damienbod\AspNetCoreSQLite\src\AspNetCoreSQLite\dataeventrecords.sqlite' It is important to define the path as shown below ‘C:\…’, otherwise the application will not work. The connection string is defined in the config.json file in this application. Public void ConfigureServices(IServiceCollection services) The SQLite Provider is used and the connection string defines the path to the SQLite file. Protected override void OnModelCreating(ModelBuilder builder)Įntity Framework is then added in the Startup class.

Public DataEventRecordContext(DbContextOptions options) :base(options) Public class DataEventRecordContext : DbContext >dotnet ef migration add testMigration The context is defined with a single DbSet and a key mapping. This is a simple class with a Id of type long. Next step is to create the POCO classes and the Entity Framework context. This is the hardest part, as you have to figure out which packages are required and also if the packages work together. The required dependencies are added to the AspNetCoreSQLite.csproj file. The project was created using Omnisharp generator-aspnet and then upgraded to version dotnet using the command line tools dotnet, and then upgraded to VS2017 csproj. : Updated to VS2017 csproj and ASP.NET Core 1.1 : Updated to VS2017 csproj with EF Core msbuild : Updated to ASP.NET Core 2.0 and EF Core 2.0 EF Core can now create SQLite databases using Entity Framework migrations which was not possible in previous versions.

Sqlite browser erikej how to#

This article shows how to use SQLite with ASP.NET Core 2.0 using Entity Framework Core.