Version conflict within the same packages/versions

[Alejandro]

Good day,

I have a ASP.NET project targeting the .NET Framework v4.7.2 (32 bit) which has the following Syncfusion nuget package references:

- Syncfusion.Compression.Base 19.2.0.47

- Syncfusion.DocIO.AspNet.Mvc5 19.2.0.47

- Syncfusion.Licensing  19.2.0.47

- Syncfusion OfficeChart.Base 19.2.0.47

- Syncfusion.Pdf.AspNet.Mvc5  19.2.0.47

- Syncfusion.XlsIO.AspNet.Mvc5  19.2.0.47

So, all references are from the same version (19.2.0.47), and all asp.net are from the mvc5 type.

Whenever I compile the project, Visual Studio shows a lot of messages regarding version mismatch, like this:

1>C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2202,5): warning MSB3277: Found conflicts between different versions of "Syncfusion.Compression.Base" that could not be resolved.

1>C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2202,5): warning MSB3277: There was a conflict between "Syncfusion.Compression.Base, Version=19.2450.0.47, Culture=neutral, PublicKeyToken=3d67ed1f87d44c89" and "Syncfusion.Compression.Base, Version=19.2460.0.47, Culture=neutral, PublicKeyToken=3d67ed1f87d44c89".

There are many more lines, I just showed 2 for the sake of brevity.

I checked the (nuget) packages folder for the solution and found that the only Nuget Package available for XlsIO is the one located in Syncfusion.XlsIO.AspNet.Mvc5.19.2.0.47\lib\net45, while many other packages have versions for other frameworks up to net46.

And inside this folder, besides the obvious Syncfusion.XlsIO.Base.dll, there's a version of Syncfusion.Compression.Base.dll that is 19.2450.0.47 instead of 19.2460.0.47, which I guess is the one causing the warnings.

The problem is not the warnings themselves, but is that other Visual Studio project that is part of the same solution (the "entry point" project) has a bin folder which does not contain libraries that cause the conflict, thus when deploying the solution a yellow screen of death is shown.

I tried setting the binding redirects in web.config, but although this may fix the wrong bindings, it doesn't help with Visual Studio copying the referenced DLLs, because it doen't know which one to copy, so the bin folder ends up with missing DLL files.

To clarify further, the project with the SF references compiles ok and its bin folder contains all the DLLs (although with mismatched version), but other projects that reference the former one end up with their bin folder incomplete.

Is there any known workaround to this version issue?

Thank you

Alejandro

[Konduru Keerthi Konduru Ravichandra Raju]

Hi Alejandro, 

  

Greetings from Syncfusion. 

  

We found that the issue is with installing Syncfusion.DocIO.AspNet.Mvc5 NuGet package and forwarded it to concerned team for investigation. Syncfusion DocIO team will get back to you in 2 business days. 

  

Regards, 

Keerthi. 

[Lokesh Baskar]

Hi Alejandro,

Thank you for your patience.

On further checking, we have found that you are using ASP.NET.MVC5 NuGet packages in .NET Framework 4.5 above targeting application. Because of using higher framework, it rises assembly conflicts for the dependent packages at your side.

Also, we have considered this scenario and planned to resolve this problem in our upcoming Weekly NuGet release on 27th July, 2021.  

At now, as a workaround, we suggest you to use AspNet NuGet packages instead of Mvc5 NuGet packages in your application. Thereby, it will refere the corresponding assemblies as per targetting .NET Framework which resolves the problem at your side. Please refer the below table to refer ASP.NET NuGet packages for controls: 

  

Mvc5 NuGet Package	AspNet NuGet Package of respective controls
Syncfusion.DocIO.AspNet.Mvc5	Syncfusion.DocIO.AspNet
Syncfusion.Pdf.AspNet.Mvc5	Syncfusion.Pdf.AspNet
Syncfusion.XlsIO.AspNet.Mvc5	Syncfusion.XlsIO.AspNet

Please let us know if you have any other questions.

Regards
Lokesh B 

[Lokesh Baskar]

Hi Alejandro,

Thank you for your patience.

We have included the fix for mentioned “Assemblies conflicts within the same packages” issue in our latest Weekly NuGet (v19.2.0.49). We are glad to announce that our latest Weekly NuGet is now available. You can use that latest NuGet to get resolve this issue at your end.

Note: This fix will be included in our 2021 Volume 2 SP release, which is expected to be available at mid of August 2021 tentatively.

Please let us know if you have any other questions.

Regards,
Lokesh B

[Alejandro]

Hello Lokesh,

I'll update the packages to the latest version ( v19.2.0.49) and I'll come back to you with the results.

Thank you for your response

Regards

Alex

[Lokesh Baskar]

Hi Alejandro,

Thank you for your update.

We will wait until hear back from you.

Regards,
Lokesh B

[Lokesh Baskar]

Hi Alejandro,

Thank you for your patience.

We have included the fix for mentioned “Assemblies conflicts within the same packages” in our 2021 Volume 2 SP release. We are glad to announce that our Essential Studio 2021 Volume 2 SP release v19.2.0.55  is rolled out and is available for download under the following link.

Essential Studio 2021 Volume 2 Service Pack Release v19.2.0.55 is available for download | Announcements Forums | Syncfusion

We thank you for your support and appreciate your patience in waiting for this release. Please get in touch with us if you would require any further assistance.

Regards,
Lokesh B