Skip to main content
BuyLog In
WinForms Controls
Search in…
Docs > .NET/.NET Core Support
A newer version of this page is available. .
All docs
V22.2
WinForms Controls
.NET/.NET Core Support
Prerequisites
What's Installed
Build an Application
Controls and Libraries
Common Features
UI Templates
Get More Help
API Reference
Download CHM

.NET Support

  • 4 minutes to read

.NET is an open-source development platform with high-performance runtime. It is maintained by Microsoft and the .NET community on GitHub.

Prerequisites

The table below shows the versions of DevExpress WinForms Controls that support .NET.

DevExpress Version .NET Core 3.0 .NET Core 3.1 (LTS) .NET 5.0 .NET 6 (LTS) .NET 7 (Latest)
v22.2 (current) no no no yes yes
v21.2-v22.1 yes yes yes yes no
v20.1-v21.1 yes yes yes no no

Prerequisites to build .NET applications:

Create .NET Applications

Use the DevExpress Project Template Gallery to create projects with DevExpress UI controls (v22.2+) that target .NET 6+.

Template Gallery - .NET Core Templates

Version 22.2+ installs local DevExpress NuGet packages on your machine. You can add these packages to your existing .NET projects from the NuGet Package Manager:

  1. In the Solution Explorer, right-click the project and select Manage NuGet Packages from the drop-down menu.

  2. Select the DevExpress Local package source.

    NuGet Package Manager - Local Package Source

  3. Install the DevExpress.Win.Design NuGet package. See How to Install NuGet Packages (NuGet Package Manager).

  4. Open the project properties. Ensure that the Target OS setting is set to Windows.

    WinForms .NET 7 Application - Project Settings

    <Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <OutputType>WinExe</OutputType>
    <TargetFramework>net7.0-windows</TargetFramework> <!-- CHECK THIS LINE -->
    <Nullable>enable</Nullable>
    <UseWindowsForms>true</UseWindowsForms>
    <ImplicitUsings>enable</ImplicitUsings>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="DevExpress.Win.Design" Version="22.2.3" />
  </ItemGroup>
</Project>
  5. Build the project.

You can also add DevExpress NuGet packages to an existing project from a remote feed:

  1. Obtain your NuGet Feed URL. You need to be logged in as a registered DevExpress customer and have an active WinForms/DXperience/Universal subscription.
  2. Register the NuGet Feed.
  3. Install the DevExpress.Win.Design NuGet package.
  4. Build the project.

Note

Install the DevExpress.Win package if you do not need design-time features.

Read the following article for detailed information and frequently asked questions: Design-Time Support for DevExpress WinForms Controls for .NET.

Upgrade .NET Framework Applications

To convert a .NET Framework project to .NET, launch the converter tool from the Visual Studio menu.

converter menu

Select the .NET version and click “Convert”.

converter dialog

This converter uses the .NET try-convert tool to upgrade your project, and replaces DevExpress assembly references with NuGet package references. After the conversion completes, the .NET Core Migration tool displays the output of the try-convert tool.

Note

The converter tool requires the .NET 5.0 SDK.

Note

.NET introduced a new default font for Windows Forms controls. As a side effect, upgrading an application to .NET 5+ may break layouts of standard Forms and UserControls with the AutoScaleMode property set to Font. To overcome this issue, replace standard Forms and UserControls with their DevExpress counterparts, or set their AutoScaleMode property to DPI.

See also: How to port desktop applications from .NET Framework to .NET

Deploy .NET Applications

Self-Contained Deployment

Your applications can be deployed in two different ways:

  • Framework-dependent deployment - the application does not include .NET. The application may not work on a client machine if the correct .NET version is not installed.

  • Self-contained deployment - .NET is a part of the application package. The disadvantages of this technique are that you must select target platforms in advance, and distribute larger deployment packages.

You can deploy self-contained applications in Visual Studio or call the following command in the command-line interface:

dotnet publish -c Release -r win10-x64 --self-contained true

See the following topic for more information: .NET application publishing overview.

Single-File Applications

You can publish .NET applications as one executable file. To do this, run the command prompt, navigate to the application folder, and call the following command:

dotnet publish -r win10-x64 -c Release -p:PublishSingleFile=true

See the following blog post for more information: WinForms - Single-File Applications With .NET Core 3.

Limitations

  • Global .NET platform limitations, not specific to DevExpress controls.
  • Reports - .NET Limitations
  • The Layout Assistant Extension is not available.
  • You cannot filter properties by name in the Visual Studio’s Properties window. This feature is available in DevExpress Designers.
  • You cannot use the Image Picker dialog to select images from project resources.
  • You cannot use the Splash Screen Manager‘s smart-tag to add a Splash Screen or a Wait Form to your project. Use the DevExpress Template Gallery to add these UI components.
  • The data source dropdown with existing data sources is not available for Repository Items in the Grid Control’s Designer. Use the Properties window to bind a repository item to a data source at design time.
  • DevExpress WinForms MVVM Templates are not available in .NET 6+ applications.
  • Design-Time Layout Templates are not available.
  • It is not possible to apply a custom skin at design-time. The Project Settings page does not load custom skins.
See Also