Introducing .NET Core Windows Forms Designer Preview 1

Olia Gavrysh

September 30th, 2019106 0

Introducing .NET Core Windows Forms Designer Preview 1

We just released a GA version of .NET Core 3.0 that includes support for Windows Forms and WPF. And along with that release we’re happy to announce the first preview version of the Windows Forms Designer for .NET Core projects!

For developers the .NET Core Windows Forms Designer (when we will release the GA version) will look and feel the same as the .NET Framework Windows Forms Designer. But for us it is a huge technical challenge to bring the designer to .NET Core because it requires the design surface that hosts the live .NET Core form to run outside the Visual Studio process. That means we need to re-architect the way the designer surface “communicates” with Visual Studio. You can watch these communications in the Output Window, where we track each request sent when the Visual Studio components are accessing properties or executing methods on the live controls in the design surface. The engineering team is still working on this technical challenge, and we will be releasing the Preview versions on regular basis to give you the early glance at the .NET Core Designer. Stay tuned! The next Preview will be coming out in early November.

Because this is the very first preview of the designer, it isn’t yet bundled with Visual Studio and instead is available as a Visual Studio extension (“VSIX”) (download). That means that if you open a Windows Forms project targeting .NET Core in Visual Studio, it won’t have the designer support by default – you need to install the .NET Core Designer first!

Enabling the designer

To enable the designer, download and install the Windows Forms .NET Core Designer VSIX package. You can remove it from Visual Studio at any time. After you install the .NET Core Designer, Visual Studio will automatically pick the right designer (.NET Core or .NET Framework) depending on the target framework of the project you’re working on.

It is early days for the designer, here is what to expect…

Please keep in mind, that this is the first preview, so the experience is limited. We support the most commonly used controls and base operations and will be adding more in each new Preview version. Eventually, we will bring the .NET Core Designer at parity with the Windows Forms Designer for .NET Framework.

Because many controls aren’t yet supported in Preview 1 of the designer, we don’t recommend porting your Windows Forms applications to .NET Core just yet if you need to use the designer on a regular basis. This Preview 1 is good for “Hello World” scenarios of creating new projects with common controls.

Controls included in Preview 1:

  • Pointer
  • Button
  • Checkbox
  • CheckedListBox
  • ComboBox
  • DateTimePicker
  • Label
  • LinkLabel
  • ListBox
  • ListView
  • MaskedTextBox
  • MonthCalendar
  • NumericUpDown
  • PictureBox
  • ProgressBar
  • RadioButton
  • RichTextBox
  • TextBox
  • TreeView

What is not supported in Preview 1:

  • Container
  • Resources
  • Component Tray
  • In-place editing
  • Designer Actions
  • Databinding
  • User Controls/Inherited Controls

Give us your feedback!

We are putting out our first bits so early to support the culture of developing the product with our users’ early feedback in mind. Please do reach out with your suggestions, issues and feature requests via Visual Studio Feedback channel. To do so, click on Send Feedback icon in Visual Studio top right corner as it is shown on the picture below.

We appreciate your engagement!

Addressing Questions

What to do if Windows Forms Designer doesn’t work?

We heard some question related to the Windows Forms Designer not working. Here’s what could have happened:

  1. You might have created a .NET Core Windows Forms project instead of the traditional .NET Framework one without realizing it. If you type “WinForms” or “Windows Forms” in the New Project Dialog, the first option would be a .NET Core Windows Forms project. If your intention is to create a .NET Framework project (with the mature designer support), just find and select Windows Forms App (.NET Framework).

  2. If you want to work with .NET Core project, don’t forget to install the .NET Core Windows Forms Designer, since it isn’t yet shipped inside Visual Studio by default. See the previous “Enabling the designer” section.

Does .NET Core WPF Designer depend on Windows Forms Designer installation?

We also received some questions related to the .NET Core WPF Designer not working and if it requires a separate installation or the Windows Forms Designer installation. No, the WPF Designer is completely independent of the Windows Forms Designer. We released its GA version of the WPF .NET Core Designer at the same time as .NET Core 3.0 and it comes with Visual Studio. In Visual Studio version 16.3.0 we had an issue with the Enable XAML Designer property set to false by default. That means that when you click on .xaml files, the designer doesn’t open automatically. Upgrade to the latest Visual Studio version 16.3.1 where this issue is fixed. Another option to fix it is to go to Tools -> Options -> XAML Designer and check Enable XAML Designer.

Olia Gavrysh Senior Product Manager, .NET

Read next

106 comments

Discussion is closed. Login to edit/delete existing comments.

  • kt ss 0

    Fantastic news.

    How long before we are able to do the exact same development on .Net core as on the .net framework

  • Scott's hotmail account 0

    VS2019 16.3.8 + VSIX update installed
    Winforms Net Core

    The VSIX update doesn’t work, it makes no difference.

    WinForms Net Core – designer view, after the update posted on this page, remains unavailable.

    [EDIT] Correction, the design view does now appear

  • Stefano Cavallaro 0

    WHY?

  • Stefano Cavallaro 0

    Is possible the roolback for use the old desigh editor?

    • Merrie McGawMicrosoft employee 0

      You can continue to use the classic Framework Designer by simply creating or opening a .NET Framework based application. If you were using workaround to get around the fact that the Core Designer isn’t ready yet, you may continue to use them.

  • Varadharaja Perumal 0

    Thank You
    It helped!

  • John McCourt 0

    Hold up. Something aint right here…. As a developer who recently moved from PHP to C# I find it quite funny that Microsoft is using WordPress (PHP) on their .NET blog. At least you guys are diversifying your technologies.

  • John McCourt 0

    I’m oldskool, so I’d like to have a file menu for my winforms. Failing that I could maybe use a ribbon (cringe) for the top of the winform. I’d also like to be able to have a status bar at the bottom of my forms. I suppose it might be possible to compensate for the lack of a status bar by using a label. So far so good. Everything that’s there seems to be working as expected. I’m glad to be one of the early adopters of this development platform.

  • Eng Adnan Turki 0

    When you will add other tools?
    Thank you…

  • Danielle Greenberg 0

    Is TabControl supported ?

Feedback usabilla icon