There is a way to force a project need to reference the specific analyzer?

[Flithor]

I have a base project (user code) with a abstruct type Xxx that needs to be implemented by projects that inherit from it, and requires to enforce implementation patterns (such as property name format).
Analyzer can do this, but analyzer reference isn't passed down through project reference, I cannot find a way to force the inherte projects to reference the anlayzer.
In other words, projects that reference project X(include Xxx) should also reference the XAnalyzer project as analyzer.

I have an idea to "finish the jigsaw" for derived classes by generating specific code using an incremental code generator. If the project is missing this necessary analyzer reference, the code with the missing "jigsaw piece" will fail when compile.

Is this possible? Or did I take the wrong path?

In short, the ultimate goal is to enforce that specific derived classes have implementations that fit to a contract when coding, rather than checking at runtime.

[huoyaoyuan]

It's a shortcoming of ProjectReference. A direct workaround is to publish the analyzer as a (local) NuGet package and use PackageReference, assuming it's changing infrequently.