Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drop the VSIX project #429

Closed
manfred-brands opened this issue Feb 28, 2022 · 4 comments · Fixed by #646
Closed

Drop the VSIX project #429

manfred-brands opened this issue Feb 28, 2022 · 4 comments · Fixed by #646
Assignees

Comments

@manfred-brands
Copy link
Member

The VSIX project only allows the analyzers to run in Visual Studio, which means that CLI build would not use them.

They have been removed from the VS extension marketplace for the roslyn analyzers.

NuGet package allows different rules/versions for different projects and can be used in CI processes.

@manfred-brands manfred-brands changed the title Can we drop the VSIX project Drop the VSIX project Feb 28, 2022
@JohanLarsson
Copy link
Contributor

A VSIX can still be useful for debugging.

@manfred-brands
Copy link
Member Author

I don't seem to be able to even find the nunit.analyzers.vsix on VS marketplace
So I can't check how many downloads there are.

I haven't compiled it for ages. not sure if @mikkelbu uploaded newer versions somewhere.

@OsirisTerje
Copy link
Member

Debugging using the vsix is not trivial either. The easiest way to debug is to actually use the code itself, clone the repo and add it to your project. The next fastest way is to create a local version of the package, in debug mode, and add that package to your project.

The VSIX project is 5 years old. I don't think it ever was realized. And if it is not present on the marketplace (I can't find it either), it probably never was there.

Suggest we just remove the remains of the vsix code.

@mikkelbu
Copy link
Member

I've never uploaded the VSIX anywhere. Prior people used them for debugging - i.e. running the VSIX project from within VS would spin up a new instance of VS with the analyzers and codefixes, but I've personally not used the VSIX in many years. I think it is fine to remove the project.

@mikkelbu mikkelbu self-assigned this Nov 17, 2023
mikkelbu added a commit that referenced this issue Nov 18, 2023
@mikkelbu mikkelbu added this to the Release 3.10 / 2.10 milestone Nov 18, 2023
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 a pull request may close this issue.

4 participants