Skip to content

Conversation

DavidTCarpenters
Copy link

Add a package reference to NetFrabric.CodeAnalysis - Gets the dll into the build.

Include PackDependencies target - Adds the reference to the lib and analyzer.

Add all output dlls as analyzer references.

Add a package reference to NetFrabric.CodeAnalysis - Gets the dll into the build
Include PackDependencies target - Adds the reference to the lib and analyzer
Add all output dlls as analyzer references
@DavidTCarpenters
Copy link
Author

Here's a screenshot of this build referenced in another project producing analyzer warnings

image

@DavidTCarpenters
Copy link
Author

And the structure of the produced package as seen in dotpeek the analyzer required the dll to be in both the lib folder and the analyzers folder

image

@aalmada
Copy link
Member

aalmada commented Oct 19, 2023

@DavidTCarpenters Thank you so much for this PR

If my understanding is correct, it duplicates the NetFabric.CodeAnalysis assembly into the analyzers\dotnet\cs directory. This is a positive approach, but what if another analyzer places an older version there? It's regrettable that .NET no longer relies on the "Global Assembly Cache" (GAC).

I believe I'll continue with the assembly merge solution, even though it encounters issues with GitHub actions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants