You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+11-9Lines changed: 11 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -7,17 +7,16 @@ Windows Presentation Foundation (WPF) is a UI framework for building Windows des
7
7
8
8
WPF applications are based on a vector graphics architecture. This enables applications to look great on high DPI monitors, as they can be infinitely scaled. WPF also includes a flexible hosting model, which makes it straightforward to host a video in a button, for example. The visual designer provided in Visual Studio makes it easy to build WPF application, with drag-in-drop and/or direct editing of XAML markup.
9
9
10
-
> Note: The WPF visual designer is not yet available and will be part of a Visual Studio 2019 update.
11
-
12
10
See the [WPF Roadmap](roadmap.md) to learn about project priorities, status and ship dates.
13
11
14
-
[WinForms](https://github.com/dotnet/winforms) is another UI framework for building Windows desktop applications that is supported on .NET Core. WPF and WinForms applications only run on Windows. They are part of the `Microsoft.NET.Sdk.WindowsDesktop` SDK. You are recommended to use [Visual Studio 2019 Preview](https://visualstudio.microsoft.com/vs/preview/) to use WPF and WinForms with .NET Core.
12
+
[WinForms](https://github.com/dotnet/winforms) is another UI framework for building Windows desktop applications that is supported on .NET Core. WPF and WinForms applications only run on Windows. They are part of the `Microsoft.NET.Sdk.WindowsDesktop` SDK. You are recommended to use [Visual Studio 2019](https://visualstudio.microsoft.com/vs/) to use WPF and WinForms with .NET Core.
*[Migrating .NET Framework WPF Apps to .NET Core](https://docs.microsoft.com/en-us/dotnet/desktop-wpf/migration/convert-project-from-net-framework)
21
20
22
21
## Status
23
22
@@ -28,15 +27,15 @@ We are in the process of doing four projects with WPF:
28
27
* Publish (and in some cases write) tests to GitHub and enable automated testing infrastructure.
29
28
* Enable the Visual Studio WPF designer to work with WPF running on .NET Core.
30
29
31
-
We are part-away through porting WPF to .NET Core, and will complete that for .NET Core 3.0. We intend to bring the codebase up to functionality and performance parity with .NET Framework.
30
+
We have completed porting WPF to .NET Core as part of .NET Core 3.0, you can learn more about what was done [here](https://github.com/dotnet/wpf/issues/1936).
32
31
33
-
We have published only a small part of the WPF source. We will continue to publish WPF components as part of the .NET Core 3 project. We will publish source and tests at the same time for each component.
32
+
We have published the vast majority of the WPF source. We will continue to publish WPF components through the rest of 2019.
34
33
35
34
See the [WPF roadmap](roadmap.md) to learn about the schedule for specific WPF components.
36
35
37
-
We have published very few tests and have very limited coverage for PRs at this time as a result. We will add more tests in 2019, however, it will be a progressive process. We welcome test contributions to increase coverage and help us validate PRs more easily.
36
+
We have published few tests and have limited coverage for PRs at this time as a result. We will add more tests in 2019 and 2020, however, it will be a progressive process.
38
37
39
-
The Visual Studio WPF designer is not yet available. In short, we need to move to an out-of-proc model (relative to Visual Studio) with the designer. This work will be part of Visual Studio 2019.
38
+
The Visual Studio WPF designer is now available as part of Visual Studio 2019.
40
39
41
40
## How to Engage, Contribute and Provide Feedback
42
41
@@ -54,10 +53,13 @@ They should not be filed on this repo.
54
53
55
54
## Relationship to .NET Framework
56
55
57
-
This code base is a fork of the WPF code in the .NET Framework. We intend to release .NET Core 3.0 with WPF having parity with the .NET Framework version. Over time, the two implementations may diverge.
56
+
This code base is a fork of the WPF code in the .NET Framework. .NET Core 3.0 was released with a goal of WPF having parity with the .NET Framework version. Over time, the two implementations may diverge.
58
57
59
58
The [Update on .NET Core 3.0 and .NET Framework 4.8](https://blogs.msdn.microsoft.com/dotnet/2018/10/04/update-on-net-core-3-0-and-net-framework-4-8/) provides a good description of the forward-looking differences between .NET Core and .NET Framework.
60
59
60
+
This [update](https://devblogs.microsoft.com/dotnet/net-core-is-the-future-of-net/) states how going forward .NET Core is the future of .NET. and .NET Framework 4.8 will be the last major version of .NET Framework.
61
+
62
+
61
63
## Code of Conduct
62
64
63
65
This project uses the [.NET Foundation Code of Conduct](https://dotnetfoundation.org/code-of-conduct) to define expected conduct in our community. Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting a project maintainer at conduct@dotnetfoundation.org.
0 commit comments