Create cross platform dotnet global tool

Why? EF Core Power Tools reverse engineering at this point includes an abundance of features that are unavailable or hard to achieve with the default command line tooling, and providing these features on other platforms is requested by a number of users.

Additional features include:

• stored procedure and functions mapping (for Azure SQL / SQL Server)
• advanced stored procedure result set discovery options
• use EF 6 classic pluralizer
• customize Humanizer pluralizer (exclude words)
• drop T4 templates
• warn if t4 templates are old
• remove obsolete files
• treat bool default values more like users expect
• split DbContext into EntityConfiguration classes
• enable type mappings (spatial, hierarchyid, DateOnly, TimeOnly, NodaTime)
• rename table and column names
• provide instructions on packages to install and DI configuration

Syntax

efcpt "<connection string/.dacpac path>" <provider name/abbreviation>

Examples

efcpt "server=.;database=Chinook" Microsoft.EntityFrameworkCore.SqlServer

efcpt "server=.;database=Chinook" mssql

efcpt "/mydatabase.dacpac" mssql

Must haves

• Create initial net6.0 tool project supporting EF Core 7
• package name: ErikEJ.EFCorePowerTools.Cli, tool name; efcpt
• Use https://www.nuget.org/packages/CommandLineParser/
• use new config file format, create class and serialization (see below) in RevEng.Common
• add mapping of provider names and aliases
• add mapper to internal options format - also merge with existing epft.renaming.json file in RevEng.Common
• Auto create config file on first run with good defaults if it does not exist
• propose useful default DbContext name
• help with samples (using command line help features)
• Improve output (Spectre.Console)
• versioning and publishing to NuGet (will do manually initially)
• Update objects list on each run (and preserve “exclude” and sproc options)
• Show instructions for DI config and package install after running
• compose and drop “readme”
• add package readme
• Use json schema for config file - located in repo
• include and drop t4 templates if opted in
• obsolete template warning

After preview 1 (to be ported/refactored from VS extension)

• Support EF Core 6/8 - explicit older/newer version of tool

TBD

• banner? (Using Figgle perhaps?)
• enable wildcard object filtering

Unsupported features (currently)

• navigation renaming
• column exclusions
• schema filter
• merging of .dacpacs
• default .dacpac schema
• postrun.cmd

@bricelam @ajcvickers FYI

[ErikEJ]

Preview 1 of the CLI tool is now available

[ErikEJ]

@antonio1612 no. Why do you need it? Just use dotnet ef