Event banner
Event details
76 Comments
- The WinForms designer for .NET Core+ was added throughout the past point releases of Visual Studio 2019, and this has caused several regressions for the .NET Framework designer, most of which have been fixed. The .NET Core designer, however, is not close to feature parity with the .NET Framework designer. Many of the techniques used to make and reuse custom controls are missing. A promise was made to provide control developers 'new guidance' on GitHub, yet this never materialized. Would it be possible to have the WinForms Designer team publish a roadmap of the various bugs and features that are going to be addressed and the timeline for them to be addressed? The guidance for control developers would be great as well.
- timheuer
Microsoft
Thanks Steven, apologies for the regressions in the Framework experience :-(. The idea of focusing on the roadmap, especially around the control dev guidance. I'll pass this along to the core designer group and see if we can be more transparent here on the fixes/features specifically.- I appreciated that the regressions were handled quickly, which is the best one could hope for. Not so satisfied in the bug reporting process. Seems like you need to collect a video in addition to repro steps and sample source code before it gets through the first layer. As such it is a huge time sink for me to report what I think is an issue but is really a known gap - except no one outside of the team knows what is expected not to work. This is the point of frustration, and getting some transparency here would go a long way!
- Welcome to the Visual Studio Ask Microsoft Anything (AMA)! This live hour gives you the opportunity to ask questions and provide feedback. Please introduce yourself by replying to this thread. Post any questions by typing a brand new comment.
- Andy SterlandHi! I'm Andy and I work on the debugging, profiling, and install experiences in Visual Studio and I'm excited to answer any questions on Visual Studio 2022!
- JonGalloway
Hi, I'm Jon Galloway. I'm a Program Manager on the .NET Community Team, and one of my focus areas is Visual Studio for Mac and .NET on macOS. We've announced our plans for Visual Studio 2022 for Mac and are working hard to release our first preview.
- timheuer👋 Hi everyone, I'm Tim and I work on the .NET and Visual Studio team doing our best to bring you developer experiences and tools for your .NET development!
- Any plans to improve typography options for the Visual Studio (source code) editor? So far, we can change the font (for the whole editor), the colors and the font weight (regular/bold). I'd like to use italics for comments, for instance. And I'd also like to choose a font's stylistic set (example: stylistic set 1 of Segoe UI makes it a programmer's font by adding serifs to the uppercase 'i'). Visual Studio's editor is implemented using WPF, so the features of the System.Windows.Documents.Typography class should make this possible, right? Follow-up question: Is it possible for a Visual Studio extension to set e.g. Typography.StylisticSet1 = true on some root element of the editor?
- mkristensen
I would love to see italic show up as an option for editor fonts as well. There's a suggestion ticket open for it, so please make sure to upvote it.
From a Visual Studio extension, you can actually make text italic + do other manipulations even though there is no UI to control it. So yes, the WPF editor does support it, but we need to expose the UI in Tools -> Options.
There is no support currently for stylistic sets.
Thanks much for all the work you and the team put into Visual Studio! I'm curious: Do you see VS and VSCode staying quite separate, or is their any sharing of logic/functionality/extensions/settings between the two planned for the near future?
- mkristensenThey are staying separate but do share a few components between them. Both the Language Server and Debug Adapter protocols are supported by both, and we're investigating bringing VS Code color themes support to Visual Studio
- Thanks, mkristensen.
- Feel free to post your questions at any time! We'll officially start at 9AM PT (25 minutes from now).
