Siegfried Pammer

@weltkante can you please test again with the latest master? If the problem is still there, please clarify. Thanks!

Yes, this was a bug, which is fixed in preview 4. The "Debug" window should only be visible in Debug builds.

You can always use the "reset layout" command from the view menu to "repair" the layout. Yes, this is a known limitation of the docking library we are using.

How many of these are still unsupported (including your PR #2045)?

Deconstruction TODO: - [X] User-defined `Deconstruct` methods - [x] Tuple deconstruction - [ ] Using the return value of the deconstruction (`var a = (b, c) = d;` -- currently...

What exactly would you want to change? Exposing tree nodes is a complex task, which is why we never started doing so, although it is a previously requested change.

As Daniel already mentioned, the currently selected language implementation dictates the text of a node. You could try extending `CSharpLanguage` and providing your custom "C# with malicious code detection" language...

I just tried this with a brand-new Windows Forms project and Visual Studio 2019 is able to open and display the Designer even though the generated code is not separated....

As far as I know, there is no generation at compile-time only at design-time. Is it possible for you to share more information and the assembly? Otherwise, I fear there...

Yeah, I now understand what the problem is: You are trying to decompile a VB.NET application and of course ILSpy only can generate C# code. However, the VB.NET Forms Designer...