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

Tutorial doesn't work in VS2019 16.7 #19876

Closed
garfbradaz opened this issue Aug 6, 2020 · 3 comments
Closed

Tutorial doesn't work in VS2019 16.7 #19876

garfbradaz opened this issue Aug 6, 2020 · 3 comments

Comments

@garfbradaz
Copy link

[Enter feedback here]

FYI Currently using VS 2019 16.7 (Community) - this tutorial doesnt work.

Logged an issue here if anyone else has problems.

https://developercommunity.visualstudio.com/content/problem/1140324/path-is-not-of-legal-form---creating-roslyn-analyzer.html

Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@Youssef1313
Copy link
Member

@BillWagner @IEvangelist, I think roslyn sdk docs need much improvements. Beside the reported issue, I don't find any intermediate to advanced scenarios that one will face when writing analyzers and code fixers. I tried to write analyzers before in both dotnet/roslyn and dotnet/roslyn-analyzers, and I always came across different problems. No resources are available anywhere online. Neither on docs, blogs, or stackoverflow. I was only able to get help from Roslyn team.

I'm still not experienced enough in this area, so I won't be able to help much unfortunately. However, you can look at my previous PRs related to writing analyzers in roslyn or roslyn-analyzers repos. I faced a problem in almost every PR. I hope these PRs can give you an insight of what mistakes/problems customers may face, and decide what deserves to be documented.

This probably will be hard to be done before .NET 5 and C# 9 waves as I think they're the top priority now.

@BillWagner
Copy link
Member

@Youssef1313 Yes, we know the roslyn analyzer area needs more work. We simply haven't had time. I'm hoping that as we keep improving the other C# content, I can start to prioritize this more.

However, you can look at my previous PRs related to writing analyzers in roslyn or roslyn-analyzers repos. I faced a problem in almost every PR. I hope these PRs can give you an insight of what mistakes/problems customers may face, and decide what deserves to be documented.

These are incredibly helpful. Thank you.

@BillWagner
Copy link
Member

closing as duplicate of #19915

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

No branches or pull requests

4 participants