-
Notifications
You must be signed in to change notification settings - Fork 831
Enable Visualizer Support for F# in VS #17239
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
Enable Visualizer Support for F# in VS #17239
Conversation
✅ No release notes required |
KevinRansom
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice,
thank you
|
Even though it may look like a small change, the impact is massive! Thanks so much for this, and maybe you can update the release-notes anyway, so that people are aware this feature is coming their way? (or is there more that needs to be done here?) |
psfinaki
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! @mpeyrotc since you've tested the scenario - if you have a minute - could you maybe record a quick demo of how things look like now? We can then probably promote this feature a bit :)
|
If the test/demo can confirm it works with a related issue: #13482 |
|
Hello psfinaki, and smoothdeveloper! Here is a .gif showcasing the IEnumerable and DataTable Visualizers for a simple F# project. |
|
@mpeyrotc that rocks! |
abelbraaksma
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is awesome!!

Description
This PR addresses bug 361 from the VS Extensibility repo, where a customer is complaining about the lack of support of Custom Visualizers in VS for the F# language. I tested F#'s support of this scenario and did not notice any issues with it, so I feel it can be safely enabled for VS 2022. The only required change is to register the appropriate EE metric that gets consumed by VS to indicate the visualizers are supported.
Checklist