Initial dev setup for localdb broken in 10.1.2

[markdav-is]

coworker pulled a fresh clone of my repo today after upgrading to 10.1.2 and they get a provider error when attempting to create the Oqtane DB on a LocalDB. I recreated this in a fresh folder as well.

Oqtane.Infrastructure.DatabaseManager] An Error Occurred Provisioning The Master Database. This Is Usually Related To The Master Database Not Being In A Supported State. System.InvalidOperationException: No database provider has been configured for this DbContext. A provider can be configured by overriding the 'DbContext.OnConfiguring' method or by using 'AddDbContext' on the application service provider. If 'AddDbContext' is used, then also ensure that your DbContext type accepts a DbContextOptions<TContext> object in its constructor and passes it to the base constructor for DbContext.
         at Microsoft.EntityFrameworkCore.Internal.DbContextServices.Initialize(IServiceProvider scopedProvider, DbContextOptions contextOptions, DbContext context) 

settings:

{
  "RenderMode": "Static",
  "Runtime": "Server",
  "Database": {
    "DefaultDBType": ""
  },
  "ConnectionStrings": {
    "DefaultConnection": ""
  },
  "Installation": {
    "DefaultAlias": "",
    "HostPassword": "",
    "HostEmail": "",
    "SiteTemplate": "",
    "DefaultTheme": "",
    "DefaultContainer": ""
  },
  "Localization": {
    "DefaultCulture": "en"
  },
  "AvailableDatabases": [
    {
      "Name": "LocalDB",
      "ControlType": "Oqtane.Installer.Controls.LocalDBConfig, Oqtane.Client",
      "DBType": "Oqtane.Database.SqlServer.SqlServerDatabase, Oqtane.Server"
    },
    {
      "Name": "SQL Server",
      "ControlType": "Oqtane.Installer.Controls.SqlServerConfig, Oqtane.Client",
      "DBType": "Oqtane.Database.SqlServer.SqlServerDatabase, Oqtane.Server"
    },
    {
      "Name": "SQLite",
      "ControlType": "Oqtane.Installer.Controls.SqliteConfig, Oqtane.Client",
      "DBType": "Oqtane.Database.Sqlite.SqliteDatabase, Oqtane.Server"
    },
    {
      "Name": "MySQL",
      "ControlType": "Oqtane.Installer.Controls.MySQLConfig, Oqtane.Client",
      "DBType": "Oqtane.Database.MySQL.MySQLDatabase, Oqtane.Server"
    },
    {
      "Name": "PostgreSQL",
      "ControlType": "Oqtane.Installer.Controls.PostgreSQLConfig, Oqtane.Client",
      "DBType": "Oqtane.Database.PostgreSQL.PostgreSQLDatabase, Oqtane.Server"
    },
    {
      "Name": "Azure SQL",
      "ControlType": "Oqtane.Installer.Controls.AzureSqlConfig, Oqtane.Client",
      "DBType": "Oqtane.Database.SqlServer.SqlServerDatabase, Oqtane.Server"
    }
  ],
  "Logging": {
    "FileLogger": {
      "LogLevel": {
        "Default": "Error"
      }
    },
    "LogLevel": {
      "Default": "Information",
      "Notify": "None"
    }
  },

[sbwalker]

@markdav-is please clarify what you mean by "coworker pulled a fresh clone of my repo today after upgrading to 10.1.2"? I have no idea what code is in your repo and I have no idea what code was used for upgrading to 10.1.2 (ie. the master branch, dev branch, upgrade ZIP, application template, etc...)

[markdav-is]

Sorry I confused the issue with a backstory. It seems to be fixed in the latest app template.

Here are the steps to reproduce:

• install latest oqtane application template 'dotnet new install Oqtane.Application.Template'
• launch visual studio
• new project: oqtane application template
• set server project as the default project
• run the first time and get an error about bad ports
• edit launchsettings.json and change ports from :0 to :5000 and :5001
• relauch to see the oqtane init screen (see below)
• keep the defaults for Database Config
• add required fields to establish the host user
• pick the empty site template
• hit "install now"

previously this would create an error. now it seems to work fine.