![\"\"](\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/10\/2019\/09\/winforms-designer-1.png\")
<\/p>\nWe 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!<\/p>\n
<\/p>\n
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 \u201ccommunicates\u201d 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.<\/p>\n
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<\/a>). 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!<\/strong><\/p>\n To enable the designer, download and install the Windows Forms .NET Core Designer VSIX package<\/a>. 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.<\/p>\n 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.<\/p>\n Because many controls aren’t yet supported in Preview 1 of the designer, we don\u2019t recommend porting your Windows Forms applications to .NET Core just yet<\/strong> if you need to use the designer on a regular basis. This Preview 1 is good for \u201cHello World\u201d scenarios of creating new projects with common controls.<\/p>\n Controls included in Preview 1:<\/p>\n What is not supported in Preview 1:<\/p>\n We are putting out our first bits so early to support the culture of developing the product with our users\u2019 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<\/strong> icon in Visual Studio top right corner as it is shown on the picture below.<\/p>\n We appreciate your engagement!<\/p>\n We heard some question related to the Windows Forms Designer not working. Here\u2019s what could have happened:<\/p>\n You might have created a .NET Core Windows Forms project instead of the traditional .NET Framework one without realizing it. If you type \u201cWinForms\u201d or \u201cWindows Forms\u201d 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)<\/strong>. If you want to work with .NET Core project, don\u2019t forget to install the .NET Core Windows Forms Designer, since it isn’t yet shipped inside Visual Studio by default. See the previous \u201cEnabling the designer\u201d section.<\/p>\n<\/li>\n<\/ol>\n 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<\/strong> 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<\/strong> -> Options<\/strong> -> XAML Designer<\/strong> and check Enable XAML Designer<\/strong>.<\/p>\n 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 […]<\/p>\n","protected":false},"author":365,"featured_media":58792,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[685],"tags":[],"class_list":["post-24761","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-dotnet"],"acf":[],"blog_post_summary":" 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 […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/24761","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/users\/365"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/comments?post=24761"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/24761\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media\/58792"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media?parent=24761"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/categories?post=24761"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/tags?post=24761"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Enabling the designer<\/h2>\n
\n
It is early days for the designer, here is what to expect\u2026<\/h2>\n
\n
\n
Give us your feedback!<\/h2>\n
![\"\"](\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/10\/2019\/09\/feedback-300x172.png\")
<\/p>\nAddressing Questions<\/h2>\n
What to do if Windows Forms Designer doesn\u2019t work?<\/h3>\n
\n
![\"\"](\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/10\/2019\/09\/new-project-300x208.png\")
<\/p>\n<\/li>\nDoes .NET Core WPF Designer depend on Windows Forms Designer installation?<\/h3>\n
![\"\"](\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/10\/2019\/09\/enable-wpf-1.png\")
<\/p>\n","protected":false},"excerpt":{"rendered":"