roslyn-sdk icon indicating copy to clipboard operation
roslyn-sdk copied to clipboard

Analyzers: dependent projects aren't rebuild automatically when building the .vsix project

Open AdmiralSnyder opened this issue 5 years ago • 4 comments

i have a vs analyzer extension (built 2 or 3 years ago, when they were still portable and not .net standard, so not the most current project template, for sure) that contains different projects (these are the relevant ones): CBmmc.Analyzers.Vsix <-- the .vsix, changed to .net standard CBmmc.Analyzers <-- the analyzers project, chanted to .net standard CBmmc.AnalyzerDependencies <-- the last remnant of portable

the vsix references contains both the analyzers project and the dependencies project (the analyzers project has a reference to the dependencies project, too) but i need to rebuild the analyzers project manually before rebuilding the vsix project to get the changes into the vsix (at least in release configuration)

this is a thing i regularly forget (since i'm not changing the analyzer logic often) which causes tedious debugging and confusion.

It would be nice if this could somehow be done automatically.

AdmiralSnyder avatar Feb 05 '20 14:02 AdmiralSnyder

I would need a sample project to reproduce this, since all the analyzer projects I work on do not exhibit this behavior.

sharwell avatar Feb 06 '20 15:02 sharwell

i asked and am allowed to send a .zip somewhere to provide you with my vsix + dependencies. how would i do that? (i'm not allowed to upload it to a place that's publicly available.

AdmiralSnyder avatar Feb 11 '20 13:02 AdmiralSnyder

@AdmiralSnyder How about a minimal repo instead of the actual one? You can pick the files essential to the vsix project and clone just those files and strip the other files. Then submitting it should be alright i guess?

taori avatar Feb 11 '20 14:02 taori

@AdmiralSnyder you can use the Report a Problem tool in Visual Studio, and add the archive as an attachment to it. It will create a public report, but the attachments will only be visible to Microsoft under terms of the privacy agreement covering feedback submissions. After it's submitted, reply here with a link to the public feedback and a member of the team can find it to review (we normally find it anyway, but the link makes sure it doesn't get lost).

sharwell avatar Feb 11 '20 17:02 sharwell