Vmware-Clarity在VS2017 .NET Core 2.0 Angular项目中的版本适配问询

开发者阿泽

2026-5-27

Answers to Your VMware Clarity & Angular/.NET Core Questions

Let's break down your questions one by one to give you clear, actionable info:

Can VMware Clarity run in a Visual Studio 2017 .NET Core 2.0 + Angular 4.2.5 project?

Short answer: Not directly with the latest Clarity 0.11.6—but it's possible if you use a Clarity version compatible with Angular 4.2.5.

Here's why: Clarity's frontend framework (@clr/angular) is tightly coupled to Angular versions. Clarity 0.10.x is the last major release that supports Angular 4.x. If you want to stick with Angular 4.2.5, you'll need to install Clarity 0.10.x instead of 0.11.6.

That said, your backend stack (.NET Core 2.0) and IDE (VS2017) don't affect Clarity's functionality at all—since Clarity runs entirely in the frontend browser context. IIS with Windows Authentication is also irrelevant to Clarity's runtime, as long as your frontend can communicate with the backend API normally.

Do you need to upgrade Angular to `5.0.0`/`5.2.0`?

If you want to use Clarity 0.11.6, yes—you must upgrade Angular to at least 5.0.0. The @clr/angular package for Clarity 0.11.6 explicitly lists a dependency on ^5.0.0 for Angular, meaning it won't work properly with Angular 4.x.

Upgrading to Angular 5.2.x (the latest stable in the 5.x line) is recommended, as it includes bug fixes and performance improvements that will pair well with Clarity 0.11.6.

What's the correct Angular version for Clarity `0.11.6`?

Clarity 0.11.6 is built to work with Angular 5.x (from 5.0.0 up to 5.2.11, the final release of Angular 5). It does not support Angular 6.0.0—you'd need to use a newer Clarity release (0.12.x or later) if you want to move to Angular 6.