EF Core Power Tools

The status bar uses ImageSource objects for icons. You can customize them in three ways:

1. Globally: Override StatusIcons.Default properties. This must be done before any controls or helpers are created to affect all instances.
2. Per Control/Helper: Assign a new StatusIcons instance to the StatusbarControl.Status.StatusIcons or StatusbarHelper.StatusIcons property. It is recommended to create a new instance to avoid modifying the global defaults.
3. Per Call: Pass a specific ImageSource to the imageSource parameter of any ShowStatusXXX() method.

To sign VSIX extensions, you need to extract specific metadata from your certificate:

1. Key container ID (-k) and CSP (-csp): Use certutil to find these values for your certificate: certutil -user -store my "<certificate serial number>"

2. Certificate fingerprint (-cfp):

   • Save your certificate as a binary .cer file.
   • Run the following PowerShell command to get the SHA256 hash:

   Get-FileHash -Algorithm SHA256 <path to .cer file> | Format-Table -AutoSize

certutil -user -store my "<certificate serial number>"

# PowerShell for fingerprint
Get-FileHash -Algorithm SHA256 <path to .cer file> | Format-Table -AutoSize

Add your database connection string to your application's configuration file (such as secrets.json, appsettings.Development.json, or appsettings.json) under the ConnectionStrings section.

{
    "ConnectionStrings": {
        "DefaultConnection": "[ConnectionString]"
    }
}

You can install the library using the dotnet CLI to add status bar functionality to your WPF application.

dotnet add package Westwind.Wpf.Statusbar

By default, EF Core Power Tools may propose a DbContext name based on your database name. You can override this to name the derived DbContext after your specific domain model instead. To change the name, update the ContextClassName property in your efpt.config.json file. Note that changing this value will result in the generated C# file being renamed to match the new class name.

"ContextClassName": "CustomContext"

To use EF Core Power Tools features that require a specific database provider, you must ensure the relevant EF Core provider package is installed in your project. This is suggested when the provider is missing from your project configuration. For example, if you are working with SQL Server, you need to add the Microsoft.EntityFrameworkCore.SqlServer package to your .csproj file.

<ItemGroup>
  <PackageReference Include="Microsoft.EntityFrameworkCore.SqlServer" Version="10.0.5" />
</ItemGroup>

Install the efcpt command-line tool globally using the dotnet tool install command. Choose the version that matches your target EF Core version:

• EF Core 10: Use version 10.*
• EF Core 9: Use version 9.*
• EF Core 8: Use version 8.*

The tool requires the .NET 8.0 or .NET 10.0 runtime to be installed on your operating system.

You can use the OutputPath and ModelNamespace configuration options in efpt.config.json to organize your project folder structure and ensure generated code is separated into a specific directory.

• OutputPath: Specifies the subfolder where generated entity files will be placed (e.g., "Models").
• ModelNamespace: Specifies the additional namespace segment to append to the project's base namespace for the generated entities (e.g., "Entities").

When both are used, the files are moved to the specified folder, and the C# namespace declaration is updated to include the ModelNamespace suffix.

{
   "ModelNamespace": "Entities",
   "OutputPath": "Models"
}