Andy De George
99e90fa162
* Add conceptual topic type for framework * Add NET WPF article topic types * Framework winforms overview topic types * Update metadata * Update walkthrough-my-first-wpf-desktop-application.md
4.1 KiB
title, description, author, ms.date, ms.author, ms.topic
| title | description | author | ms.date | ms.author | ms.topic |
|---|---|---|---|---|---|
| Differences between .NET Framework and .NET Core | Describes the differences between the .NET Framework implementation of Windows Presentation Foundation (WPF) and .NET Core WPF. When migrating your app, you should consider these incompatibilities. | adegeo | 09/21/2019 | adegeo | conceptual |
Differences in 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.
[!INCLUDE desktop guide under construction]
SDK-style projects
.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 apps to .NET Core, you must convert your projects. For more information, see Migrate 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 <PackageReference> format:
- In Visual Studio, open the Solution Explorer pane.
- In 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. Select 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
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.
Publicly defined CAS-related types were moved out of the WPF assemblies and into the Core .NET library assemblies. The WPF assemblies have type-forwarding set to the new location of the moved types.
| Source assembly | Target assembly | Type |
|---|---|---|
| WindowsBase.dll | System.Security.Permissions.dll | xref:System.Security.Permissions.MediaPermission xref:System.Security.Permissions.MediaPermissionAttribute xref:System.Security.Permissions.MediaPermissionAudio xref:System.Security.Permissions.MediaPermissionImage xref:System.Security.Permissions.MediaPermissionVideo xref:System.Security.Permissions.WebBrowserPermission xref:System.Security.Permissions.WebBrowserPermissionAttribute xref:System.Security.Permissions.WebBrowserPermissionLevel |
| System.Xaml.dll | System.Security.Permissions.dll | xref:System.Xaml.Permissions.XamlLoadPermission |
| System.Xaml.dll | System.Windows.Extension.dll | xref:System.Xaml.Permissions.XamlAccessLevel |
Note
In order to minimize porting friction, the functionality for storing and retrieving information related to the following properties was retained in the
XamlAccessLeveltype.
PrivateAccessToTypeNameAssemblyNameString