Incorrect Ambiguous and Unresolved References in a Custom WebViewPage

Build 241.0.20240623.154825 built on 2024-06-23

VS 2022 (17.10.3)

Application is .NET Framework 4.8.1, and is consuming packages we wrote in .NET Standard 2.0 (multi-targeting .NET 6 during the transition).

When R# is enabled, it reports ambiguous references that VS itself does not.

With R# disabled, it reads clean and only notices System.Web.Mvc.

This results in an inordinate number of errors reported in the solution, but it compiles and runs fine, both in a debugger, and deployed to a production environment.

It has also been mis-identifying unresolvable references from the custom WebViewPage<TModel>:

IsAdmin most definitely exists on the custom WebViewPage, as shown by clicking F12 through IsAdmin to see this:

…. which is mostly correctly set in web.config:

The “incorrect number of type parameters” error is also coming from R# and goes away when R# is suspended, but comes right back when re-enabled.

Somehow I believe these two things are related.   Where are all these errors coming from, and how can I mitigate them, without having to manually assess each of the 400+ errors and “Ignore” them manually in the Errors/Warnings in Solution?

Thanks!

Jeff Woods

Reading, PA