DEV Community: Kibria

Handling nopCommerce Plugin Dependencies: A Quick Naming Catch Fix

Kibria — Sat, 29 Aug 2026 11:42:00 +0000

TL;DR: If a bundled nopStation plugin throws a missing dependency error for NopStation.Core, the file is already on your server. The admin dashboard is simply hiding it because the backend system name doesn't match the frontend display name.

When installing a new plugin in nopCommerce, missing dependency alerts can sometimes pull you into an unexpected troubleshooting loop.

Recently, I was setting up the SSLCommerz payment plugin. The installation halted with a bright red warning banner:

Error Message:

The "SSLCommerz" plugin depends on the following plugins which must be installed beforehand: "NopStation.Core"

Naturally, I immediately went to the Local Plugins search bar and typed in the exact system name provided by the error message: NopStation.Core.

Zero results.

Investigating the Server Folders

Knowing that the main NopStation.Plugin.Payments.SSLCommerz-4.90.zip package comes bundled with both plugins inside, I didn't actually have to upload them separately.

To make sure nothing went wrong during the unpack process, I checked my server's remote Plugins directory. Sure enough, both folders were unpacked and sitting right next to each other on the filesystem.

If the files were successfully on the server, why wasn't the local plugin list showing it?

The Display Name Catch 🔍

The issue comes down to how nopCommerce filters its plugin list, combined with how nopStation structures their extensions. This brings us to the main architectural learning here: the mismatch between backend system names and frontend display names.

System Name: Used in folder paths, code references, and dependency error strings (NopStation.Core).
Display Name: The friendly text rendered in the admin panel UI.

Instead of looking for the system name NopStation.Core which was given in the SSLCommerz's plugin dependency error message, I went back to the Local Plugins dashboard, cleared the query, and searched for a broader keyword: "Nop".

Boom. It appeared immediately under its actual UI naming convention:

Display Name: Nop-Station Core
Description: This plugin is used to manage Nop-Station plugins.

Because the dashboard search bar filters strictly by the friendly UI display name rather than the backend system string, searching for the exact error message text hid it from view.

🚀 Key Takeaways for Developers

If you find yourself stuck on a similar dependency block while using third-party extensions like those from nopStation, bypass the error string and try these steps:

Verify the Directory: Check your filesystem's Plugins folder first to ensure the dependency directory actually extracted.
Search by Fragment: Do not paste the full system name from the error banner into the admin search bar. Search for a core fragment like "Nop" or "Core".
Install the Core First: Once found, hit Install on the core management plugin, click Restart application to apply changes, and then proceed to install your primary payment plugin.

Keeping this display-versus-system name behavior in mind will save you plenty of time when working inside the nopCommerce ecosystem!

VS2022's Angular and ASP.NET Core Template Is Stuck on Angular 19 — Here's the Workaround

Kibria — Tue, 24 Mar 2026 19:24:34 +0000

If you recently updated your Angular CLI and then tried to create a new project using Visual Studio 2022's "Angular and ASP.NET Core" template, you may have hit a wall. The project creation fails, and the error points at ng — even if Angular CLI is clearly installed on your machine.

After getting the error, my first instinct was to update Angular CLI to the latest. That brought it to CLI 21.2.3 at the time. Went back to Visual Studio, tried again — still the same error. Updating hadn't helped. A bit of searching later, it pointed to the template itself being the problem.

What's happening

The VS2022 Angular and ASP.NET Core template depends on Angular CLI 19 to scaffold the project. It has not been updated to work with Angular 20 or later.

So if your machine has Angular CLI 20, 21, or newer globally installed — which is likely if you've been keeping up — the template simply can't do its job. It's not a bug in your setup. The template itself is behind.

Microsoft's own documentation acknowledges this:

"There is a compatibility issue with Angular 20.x.x and the Angular and ASP.NET Core template in Visual Studio 2022."
— learn.microsoft.com

The workaround

The approach is two steps: satisfy the template first, then bring your app up to date.

Step 1 — Temporarily install Angular CLI 19 globally

Check your current global CLI version:

ng version

If it's 20 or above, swap it out:

npm uninstall -g @angular/cli
npm install -g @angular/cli@19

Now go back to Visual Studio 2022 and create the project using the "Angular and ASP.NET Core" template. It should work. You may see a warning about your Node version not being officially supported by Angular 19 — that's expected and fine for this step.

Step 2 — Upgrade the Angular app to the current version

The generated project will be on Angular 19.x. Since you're probably running a newer Node version and want to stay current, upgrade the Angular version inside the project — step by step, as Angular's migration guide recommends:

# From the Angular project folder

# 19 → 20
ng update @angular/core@20 @angular/cli@20

# 20 → 21
ng update @angular/core@21 @angular/cli@21

Don't skip versions. Angular's incremental update process handles breaking changes and schematic migrations properly when you go one major at a time.

After both upgrades, the project is on Angular 21 — the current version at the time of writing — and the local toolchain is consistent again.

After you're done

Once the project is created and upgraded, you can restore your global CLI to the latest:

npm install -g @angular/cli@latest

Your new project now has its own local CLI version locked in package.json, so the global version won't interfere with it going forward.

TL;DR

The Angular and ASP.NET Core template of Visual Studio 2022 hasn't caught up with Angular 20+
Downgrade your global CLI to 19 temporarily to unblock project creation
Then upgrade the project's Angular version to where you actually want to be
Restore your global CLI afterward

The template is the bottleneck here, not your machine. Work around it, then move on.