Version Compatibility of ASP.NET Core Controls
4 Dec 20243 minutes to read
The following table represents the supported .NET and .NET Core versions by different Syncfusion® ASP.NET Core controls releases.
| Version | Syncfusion® ASP.NET Core Controls Version |
|---|---|
| .NET 9.0 | 27.2.2 and above |
| .NET 8.0 | 23.1.36 and above |
| .NET 7.0 | 20.4.0.38 and above |
| .NET 6.0 | 19.3.0.43 and above |
| .NET 5.0 | 18.4.0.30 and above |
| .NET Core 3.1.3 | 18.1.0.52 and above |
| .NET Core 3.1.2 | 18.1.0.42 and above |
| .NET Core 3.1.1 | 17.4.0.46 and above |
| .NET Core 3.1 | 17.4.0.39 and above |
| .NET Core 3.0 | 17.3.0.14 and above |
| .NET Core 2.2 | 16.4.0.42 and above |
| .NET Core 2.1 | 16.2.0.41 and above |
| .NET Core 2.0 | 15.3.0.26 and above |
| .NET Core 1.1 | 14.4.0.15 and above |
| .NET Core 1.0 | 14.2.0.26 and above |
Syncfusion® Version Information
Syncfusion® follows a quarterly release schedule, introducing new volumes every three months. To track these releases and their associated changes, Syncfusion® ASP.NET Core components utilize a sequence-based identifier system, employing the format Major.Minor.Revision. This system enables developers to easily monitor modifications made in each release.
For example, if the release package version is 23.1.36, the version number can be interpreted as follows:
-
23 represents the
major releaseversion. This number changes every three months and encompasses significant updates, new features, as well as bug fixes and breaking changes. -
1 corresponds to the
minor releaseversion. This number signifies releases primarily focused on new features and addressing bugs, without introducing breaking changes. -
36 denotes the
revision number, also referred to as thepatch number. This number increases for weekly patch releases, which predominantly consist of bug fixes and do not introduce new features or breaking changes.