OOP Windows Forms Designer for .NET Applications

[giduac]

Two articles from Klaus Loeffelmann (who is working on this). A must read to become familiar with the matter.

State of the OOP Windows Forms Designer for .NET Applications (OOP == Out Of Process):
https://devblogs.microsoft.com/dotnet/state-of-the-windows-forms-designer-for-net-applications/

Data binding with the OOP Windows Forms Designer:
https://devblogs.microsoft.com/dotnet/databinding-with-the-oop-windows-forms-designer/

The Microsoft WinForms Designer SDK NuGet package:
https://www.nuget.org/packages/Microsoft.WinForms.Designer.SDK

The package will be needed for third party component designers & editors to work with the OOP Designer.

The package/SDK lacks documentation. Which has been announced by Loeffelmann around the end of March 2022.

Discussions on GitHub specific to this topic:
https://github.com/dotnet/winforms/discussions?discussions_q=label%3A%22area%3A+VS+designer%22

Added 12-05-2022
https://devblogs.microsoft.com/dotnet/custom-controls-for-winforms-out-of-process-designer/

Added 10-25-2022
Seems to be some movement going one. This thread could be one to watch.
Thread: Specific: dotnet/winforms#7073
Specific: dotnet/winforms#7073 (comment)
Sample(s): https://github.com/KlausLoeffelmann/NetControlDesigners

Possible and limited work-a-round
As per documentation for net48 the .NET Framework designer is used in Visual Studio.

• Use the <Project Sdk="Microsoft.NET.Sdk"> style project format (.csproj).
• Change the <TargetFramework> element tags to <TargetFrameworks>
• Add the “net48” as first option to the <TargetFrameworks>

<TargetFrameworks>net48;net5.0-windows;net6.0-windows</TargetFrameworks>

This only works as long as the form component(s) used are .NET Framework compatible.

At runtime custom editors can start under the different .NET versions since this condition only exists within Visual Studio.

So even if components can not be edited visually they can programmatically. Also the (custom/third party) Editors work at runtime when launched from a property-grid. Which leaves the option to configure/add components at runtime from code.

Added 3-8-2024
An article on VS Magazine
https://visualstudiomagazine.com/Articles/2024/02/28/winforms-update.aspx

The discussion has been opened to discuss & collect information over time and make it available here in the topic start.

[Tape-Worm]

So even if components can not be edited visually they can programmatically. Also the (custom/third party) Editors work at runtime when launched from a property-grid. Which leaves the option to configure/add components at runtime from code.

The bolded/italicized text is not true in .NET Core/5/6 in the case of the Ribbon (see #262 ).

[giduac]

Hi @Tape-Worm,

I've tried it (see video), but here this works (NET 6).
Is this about the same you've been trying to do?

BCk5LfiaWG.mp4

[giduac]

Hi @Tape-Worm

From the above I can't deduct how this occurs.

Can you post a clear reproduction.
A video that shows the path to and when the error occurs, please.
Maybe add a sample project too.

TY,

[Tape-Worm]

It's not very hard to reproduce this:

• Create an empty .NET 6 Windows Forms application.
• Get krypton ribbon from nuget.
• Add a ribbon.
• Then do exactly what you're trying to do in your video.

[giduac]

Ok, I Had another look.

What my video shows is altering the ribbon via a property-grid at runtime.
If I'm right you are having the error within the Visual Studio WinForms Designer (at design-time).

Quote from the topic start (which you mentioned)
So even if components can not be edited visually they can programmatically. Also the (custom/third party) Editors work at runtime when launched from a property-grid.

[Tape-Worm]

I see. Yes, my issue is at design time. Runtime usage is not going to work for me, but I had missed that part in the description (perhaps you should bold it or italic it so it stands out for dummies like me).

The only reason I'm here on this thread is because I was directed here when I asked if any progress had been made on issue #262 . So, it seems that we're on 2 different wavelengths if you're focusing on using the designers at runtime. Why I was sent to this topic, I have no idea, because it certainly did not answer my query, so I'm guessing no progress has been made on fixing the Ribbon designers at design time yet.

Sorry if I sound frustrated, this has been an ongoing issue for some time and the workarounds are painful to deal with.

[giduac]

No worries :)

The discussion was put up here to gather info on the new WinForms Designer. Since the thing is still not fully ready, as is the documentation for the SDK. As long as this documentation isn't complete the Toolkit can't really be updated.

Like in the topic start.
You can, probably a lot more work, handle the ribbon controls through code. Not ideal but a viable work-a-round.

[PWagner1]

Just putting this here...

[Smurf-IV]

Just putting this here...

Can that go on the Landing page ? as to what "Lite" contains (It will need 4.8 as well ?)

[PWagner1]

@Smurf-IV

Yes, I'll create a nicer layout for it

[Smurf-IV]

dotnet/winforms#7073

[giduac]

There seems to be some kind of movement on this topic:
dotnet/winforms#7073 (reply in thread)

[PWagner1]

Could this be considered for v80?

[giduac]

Looks like a hard nut to speculate about atm...

[giduac]

@Smurf-IV @Wagnerp ,
Seems to be some movement going one. This thread could be one to watch.

Thread: dotnet/winforms#7073
Specific: dotnet/winforms#7073 (comment)
Sample(s): https://github.com/KlausLoeffelmann/NetControlDesigners

[PWagner1]

@giduac So, it seems that they were primarily focused on .NET 7... until now

[giduac]

Looks like a lot of folks are waiting on this. So.. fingers crossed...

[ryantuffney-shell]

Any update on this?

[imerzan]

Trying to use net48 causes the majority of my program to break (it complains I can't use the C#8 and later features). Not sure if this is considered a great workaround.

[Smurf-IV]

Have MS finally enabled Designers ??
https://devblogs.microsoft.com/dotnet/custom-controls-for-winforms-out-of-process-designer/

[imerzan]

Reading this article, and it mentions a Type Editor template. I am confused - does this mean Krypton would need to be re-packaged to be compatible with .NET6 Winforms, or is this something that I would need to run in my coding environment?

[Smurf-IV]

does this mean Krypton would need to be re-packaged to be compatible with .NET6 Winforms

I think it does.

[giduac]

Topic start updated with an article from vs magazine.