Differences in .NET Core WPF
This article describes the differences between Windows Presentation Foundation (WPF) on .NET Core and .NET Framework. WPF for .NET Core is an open-source framework forked from the original WPF for .NET Framework source code.
There are a few features of .NET Framework that .NET Core doesn't support. For more information on unsupported technologies, see .NET Framework technologies unavailable on .NET Core.
The Desktop Guide documentation is under construction.
.NET Core uses SDK-style project files. These project files are different from the traditional .NET Framework project files managed by Visual Studio. To migrate your .NET Framework WPF application to .NET Core, you must convert your projects. For more information, see Migrating WPF Apps to .NET Core 3.0.
NuGet package references
If your .NET Framework app lists its NuGet dependencies in a packages.config file, migrate to the
- In Visual Studio, find the Solution Explorer pane.
- Within your WPF project, right-click packages.config > Migrate packages.config to PackageReference.
A dialog will appear showing calculated top-level NuGet dependencies and asking which other NuGet packages should be promoted to top level. Click Ok and the packages.config file will be removed from the project and
<PackageReference> elements will be added to the project file.
When your project uses
<PackageReference>, packages aren't stored locally in a packages folder, they're stored globally. Open the project file and remove any
<Analyzer> elements that referred to the packages folder. These analyzers are automatically included with the NuGet package references.
Code Access Security (CAS)
Code Access Security (CAS) is not supported by .NET Core or WPF for .NET Core. All CAS-related functionality is treated under the assumption of full-trust. WPF for .NET Core removes CAS-related code. The public API surface of these types still exists to ensure that calls into these types succeed. However, these calls don't actually do anything.
Publicly defined CAS-related types were moved out of the WPF assemblies and into the CoreFX assemblies. The WPF assemblies have type-forwarding set to the new location of the moved types.
|Source Assembly||Target Assembly||Type|
In order to minimize porting friction, the functionality for storing and retrieving information related to the following properties was retained in the