-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The project should be database independent #33
Comments
Try the following: yo react-aspnet-boilerplate:empty-template That one does not use a database (or at least doesn't appear to). |
To use a different Entity Framework provider do the following: //"Microsoft.EntityFrameworkCore.SqlServer": "1.1.0",
"Npgsql.EntityFrameworkCore.PostgreSQL": "1.1.0", Startup.cs // Add framework services.
// services.AddDbContext<ApplicationDbContext>(options =>
// options.UseSqlServer(Configuration.GetConnectionString("DefaultConnection")));
services.AddDbContext<ApplicationDbContext>(options =>
options.UseNpgsql(Configuration.GetConnectionString("DefaultConnection"))); Migrations folder |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello.
I wanted to test this generator for .NET core but apparently it's quite hard to use is without SQL Server, event after changing the connection string and adapting the Startup.cs, there are references of SQL Server specifics features in the migrations.
I think it could be interesting to make the boilerplate independent from any database.
Thanks
The text was updated successfully, but these errors were encountered: