NuGet Feed Setup — Blazor Power Tools

Package Sources

Blazor Power Tools is distributed via NuGet. Depending on your license type, you'll either use the public NuGet.org feed or a private organizational feed.

Option A: Public NuGet.org Feed

The standard Blazor Power Tools package is available on NuGet.org. Install directly with the CLI:

dotnet add package BlazorPowerTools

Or via the Visual Studio NuGet Package Manager by searching for "BlazorPowerTools".

Option B: Private / Organizational NuGet Feed

If your organization hosts BPT on a private feed (Azure Artifacts, GitHub Packages, ProGet, etc.), you need to register the feed source before installing.

1. Add the feed source

Create or edit a nuget.config file in your solution root:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>
    <clear />
    <add key="nuget.org" value="https://api.nuget.org/v3/index.json" />
    <add key="BptFeed" value="https://pkgs.your-org.com/nuget/v3/index.json" />
  </packageSources>
  <packageSourceCredentials>
    <BptFeed>
      <add key="Username" value="your-username" />
      <add key="ClearTextPassword" value="%BPT_FEED_TOKEN%" />
    </BptFeed>
  </packageSourceCredentials>
</configuration>

Security Never commit credentials in plain text. Use environment variables (as shown with %BPT_FEED_TOKEN%) or a credential provider. On CI/CD, inject the token as a secret.

2. Alternatively, add via CLI

dotnet nuget add source "https://pkgs.your-org.com/nuget/v3/index.json" \
    --name BptFeed \
    --username your-username \
    --password "$BPT_FEED_TOKEN" \
    --store-password-in-clear-text

3. Install the package

Once the feed is configured, install as usual:

dotnet add package BlazorPowerTools

Version Management

Pin to a specific version to avoid unexpected breaking changes in production:

<PackageReference Include="BlazorPowerTools" Version="1.5.0" />

Or use a version range to accept patches:

<PackageReference Include="BlazorPowerTools" Version="[1.5.0, 1.6.0)" />

To check for updates:

dotnet list package --outdated

Tip Use Directory.Packages.props for centralized package version management across multi-project solutions. This ensures all projects reference the same BPT version.

Common Feed Providers

Azure Artifacts

Use the Azure Artifacts Credential Provider for seamless auth. Install with dotnet tool install --global artifacts-credprovider and set the VSS_NUGET_EXTERNAL_FEED_ENDPOINTS environment variable.

GitHub Packages

Generate a Personal Access Token (PAT) with read:packages scope. Use the PAT as the password in your nuget.config. The feed URL follows the pattern https://nuget.pkg.github.com/OWNER/index.json.

IDE-Specific Configuration

The sections below show how to configure the BlazorPowerTools NuGet source in popular development environments. These instructions apply to both the public NuGet.org feed and private organizational feeds.

Visual Studio 2022 / 2026

Visual Studio has a built-in GUI for managing NuGet package sources.

Open Package Source Settings

Go to Tools → NuGet Package Manager → Package Manager Settings.

In the left pane, select Package Sources.

Add a New Source

Click the + (green plus) button in the upper-right corner to add a new source. Fill in the fields:

Name: BlazorPowerTools
Source: http://nuget.blazorpowertools.com/

Click Update, then OK to save.

Install the Package

Right-click your project in Solution Explorer → Manage NuGet Packages. Select the BlazorPowerTools source from the Package source dropdown in the upper-right corner of the NuGet Package Manager window, then search for BlazorPowerTools and click Install.

Tip If your feed requires authentication, Visual Studio will prompt for credentials automatically. For Azure Artifacts or GitHub Packages, install the corresponding credential provider for a seamless experience.

Visual Studio Code

VS Code does not have a built-in NuGet source GUI. You manage package sources through nuget.config files and the .NET CLI.

Option 1: nuget.config file (recommended)

Create a nuget.config file in your solution root:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>
    <clear />
    <add key="nuget.org" value="https://api.nuget.org/v3/index.json" />
    <add key="BlazorPowerTools" value="http://nuget.blazorpowertools.com/" />
  </packageSources>
</configuration>

Note The nuget.config file is automatically detected by both dotnet CLI commands and the C# Dev Kit extension for VS Code.

Option 2: .NET CLI commands

Add the source directly from the terminal:

dotnet nuget add source "http://nuget.blazorpowertools.com/" \
    --name BlazorPowerTools

Then install the package:

dotnet add package BlazorPowerTools

To verify your configured sources:

dotnet nuget list source

Option 3: C# Dev Kit Extension

If you have the C# Dev Kit extension installed, it provides a NuGet Package Manager view in the Explorer sidebar. To use it:

Open the Command Palette (Ctrl+Shift+P / Cmd+Shift+P)
Search for "NuGet: Open NuGet Gallery"
The gallery reads package sources from your nuget.config — make sure the BlazorPowerTools source is configured as shown above
Search for BlazorPowerTools and install

C# Dev Kit requirement The NuGet gallery view requires the C# Dev Kit extension (not just the base C# extension). If you only have the base C# extension, use the CLI or nuget.config approach.

Back to Getting Started

Continue with the full setup guide.

License Key Setup

Activate your license after installing the package.

Set Up the BlazorPowerTools NuGet Feed

Package Sources

Option A: Public NuGet.org Feed

Option B: Private / Organizational NuGet Feed

1. Add the feed source

2. Alternatively, add via CLI

3. Install the package

Version Management

Common Feed Providers

Azure Artifacts

GitHub Packages

IDE-Specific Configuration

Visual Studio 2022 / 2026

Open Package Source Settings

Add a New Source

Install the Package

Visual Studio Code

Option 1: nuget.config file (recommended)

Option 2: .NET CLI commands

Option 3: C# Dev Kit Extension

Back to Getting Started

License Key Setup