.Net 8 compatibility

[Lenny]

I noticed that if I attempt to add the .net core nuget package to a .net 8 project with entity framework core design package installed the add will fail as the Telerik package requires older libraries that the newer entity framework is not compatible with. The Telerik blog page indicates that the latest Telerik package is fully compatible with .net 8 and I dont believe that is accurate. Any idea when this will be fixed.

[JG]

We're also getting a similar issue using the Microsoft code analysis package; 

NU1107  Version conflict detected for Microsoft.CodeAnalysis.CSharp.Workspaces.
Install/reference Microsoft.CodeAnalysis.CSharp.Workspaces 4.4.0 directly to project

[Lenny]

Looks like Telerik release an update to their nuget package. I am going to try the updated one

[Lenny]

FYI the updated package has the same issue as the previous one. I opened a support ticket. Hopefully they will fix it soon.

[Mike]

Yes, I noticed that too this morning, however mine was about version 4.5, not 4.4.

Awaiting an update from Telerik on this issue.  I don't reference EF Core Design package, but I do have EF Core SqlServer and EF Core Tools (one of which may required the Design package).

I also tried directly referencing Microsoft.CodeAnalysis.CSharp.Workspaces 4.5.0 directly (as well as 4.7.0 - the latest available at the time of this post) and that still didn't work

[Alexander]

Hi,

Since Lenny opened an identical thread regarding the same subject matter, I will post my answer here, so that it could be helpful to the community as well:

"Generally, the Telerik UI library is compatible with .NET 8.0. Thus, to omit the error, a possible recommendation would be to install the all-in-one NuGet package "Microsoft.CodeAnalysis" instead. This package can be perceived as an indirect dependency, thus, it can be altered as per your requirements:

This would override the existing package reference to "CodeAnalysis" within the Telerik UI for ASP.NET Core assembly:

I have purposefully created a proof-of-concept sample application that tackles the aforementioned approach, as well as including some of the newly released EntityFrameworkCore packages that require a latter version of the dependency."

I hope this helps.

 

[Mike]

This doesn't seem to solve my issue.  I updated to the latest Telerik package (2023.3.1114 at time of comment) and bumped my projects to .NET 8.  I also added Microsoft.CodeAnalysis 4.5 (later updating it to 4.7) and it's still throwing the error

Version conflict detected for Microsoft.CodeAnalysis.CSharp.Workspaces. Install/reference Microsoft.CodeAnalysis.CSharp.Workspaces 4.8.0-3.final directly

I then added the package reference in the error (it's pre-release currently), and that still hasn't solved the issue.

[Lenny]

Telerik has a hard reference to Microsoft.CodeAnalysis 4.4.0 which has the reference to Microsoft.CodeAnalysis.CSharp.Workspaces 4.4.0 

They will have to fix this before we can add Microsoft.EntityFramework.Tools package.

 

[Mike]

I looked into what was using the Microsoft.EntityFramework.Tools package and was able to remove it.  After that, I am still not able to upgrade to .NET 8 - still getting the same error.  I guess I'll just have to wait until Telerik releases a .NET 8 compatible version.

[Alexander]

I am again giving you a follow-up on a previous communication with Lenny:

In regard to the source code, we agree with you that we have added an explicit reference to "Code.Analysis 4.4.0". Since we have received a vast amount of reports these past days, we will diligently explore the option of migrating the existing package to a version that is supported by ".NET 8".

Nevertheless, I have further added the following set of packages to the existing project infrastructure:

However, I did not manage to observe a compile-time or a run-time error.

Additionally, CodeAnalysis has direct dependencies in which it comes with:

Thus, if both of the packages are explicitly referenced on your side, I would recommend omitting them. Additionally, try to clean and rebuild the project.

[Paul]

I am having the same issues as well and it's Sep 9th 2024.  What is going on with this? I believe this issue warrants a refund to all people who purchased licenses expecting it to work for .NET 8.

 

[Alexander]

Hi Paul,

We have currently bumped the version of CodeAnalysis to version "4.8.0". However, I personally see that it would be more fitting to do an automated process of migrating the version to newest ones that surface.

I will bring this up for discussion within the team on a potential way of handling this. In order mitigate this behavior a possible recommendation to follow the guidelines mentioned in the following resource:

• Upgrading .NET8

Or, alternatively, include the following references to your application's project file in order to replace the outdated package versions:

<ItemGroup>
	<PackageReference Include="Microsoft.CodeAnalysis" Version="4.11.0" />
	<PackageReference Include="Microsoft.CodeAnalysis.Common" Version="4.11.0" />
	<PackageReference Include="Microsoft.CodeAnalysis.CSharp" Version="4.11.0" />
	<PackageReference Include="Microsoft.CodeAnalysis.CSharp.Features" Version="4.11.0" />
	<PackageReference Include="Microsoft.CodeAnalysis.CSharp.Workspaces" Version="4.11.0" />
	<PackageReference Include="Microsoft.CodeAnalysis.Features" Version="4.11.0" />
	<PackageReference Include="Microsoft.CodeAnalysis.Scripting.Common" Version="4.11.0" />
	<PackageReference Include="Microsoft.CodeAnalysis.Workspaces.Common" Version="4.11.0" />
</ItemGroup>