We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy. Image for the cookie policy date
Unfortunately, activation email could not send to your email. Please try again.
Syncfusion Feedback

Syncfusion NuGet package structure changes

Platform: Miscellaneous |
Control: Extension

Syncfusion has provided separate NuGet packages for each .NET Framework version assembly till v16.1.0.24. From Essential Studio 2018 Volume 1 SP 1 release (v16.1.0.32) onwards each NuGet package will contain all applicable .NET Framework versions for the Syncfusion component. 

NuGet package structure

Example NuGet package structure changes have been shown below.

Component Name

Till v16.1.0.24

From v16.1.0.32

Chart WPF











Grid Windows








Modified NuGet packages

NuGet package structure changes has been applicable for the below listed platforms. List of packages with older and newer format is listed and available for download in PDF format.

Platform Name

Package Structure changes list



Windows Forms

Windows Forms.pdf




ASP.NET Core.pdf

Follow the below steps to update the NuGet package structure changes in your project

  1. Locate your Windows development Visual Studio project location. No need to make any changes for Web development project.
  2. Open the packages.config file from any editor.
  3. Remove the .NET Framework character such as 20,35,40,45,451 and 46 from Syncfusion packages and change the version to or latest Syncfusion release version. Refer the screenshot below.
  • 2018 Vol 1 NuGet package name (v16.1.0.24)

<?xml version="1.0" encoding="utf-8"?>


  <package id="Syncfusion.Data.WPF46" version="" targetFramework="net46" />

  <package id="Syncfusion.SfChart.WPF46" version="" targetFramework="net46" />

  <package id="Syncfusion.SfGrid.WPF46" version="" targetFramework="net46" />

  <package id="Syncfusion.Shared.WPF46" version="" targetFramework="net46" />


  • 2018 Vol 1 SP1 updated NuGet package name (v16.1.0.32)

<?xml version="1.0" encoding="utf-8"?>


  <package id="Syncfusion.Data.WPF" version="" targetFramework="net46" />

  <package id="Syncfusion.SfChart.WPF" version="" targetFramework="net46" />

  <package id="Syncfusion.SfGrid.WPF" version="" targetFramework="net46" />

  <package id="Syncfusion.Shared.WPF" version="" targetFramework="net46" />


  1. Remove the packages folder from the Visual Studio project location.
  2. Open the Visual Studio development project and restore the NuGet Packages by right click on the solution file and select Restore NuGet Packages. Now you get the Syncfusion NuGet packages with combined .NET Framework libraries.
  3. Use the NuGet Update option to get the latest Syncfusion NuGet packages.
You must log in to leave a comment
Pieter van Kampen
Apr 04, 2018

So has the Nuget package source url changed?

Dheepa Kumar [Syncfusion]
Apr 05, 2018

Hi Pieter van Kampen,


No, you can use same NuGet package feed link (source url) for package configuration. We have changed only the NuGet package name and structure.

And that feed link contains both framework wise (before v16.1.0.32) separated package and framework grouped packages (from v16.1.0.32).


Dheepa Kumar 

Michael Brown
Jul 12, 2018

I have upgraded ALL nuget packages to version yet I still get this error when I compile my Xam Forms app:

Severity Code Description Project File Line Suppression State

Error The "LinkAssemblies" task failed unexpectedly.

Java.Interop.Tools.Diagnostics.XamarinAndroidException: error XA2006: Could not resolve reference to 'Syncfusion.DocIO.DLS.Rendering.DocumentLayouter' (defined in assembly 'Syncfusion.DocIORenderer.Portable, Version=16.1140.0.37, Culture=neutral, PublicKeyToken=3d67ed1f87d44c89') with scope 'Syncfusion.DocIO.Portable, Version=16.1140.0.37, Culture=neutral, PublicKeyToken=3d67ed1f87d44c89'. When the scope is different from the defining assembly, it usually means that the type is forwarded. ---> Mono.Cecil.ResolutionException: Failed to resolve Syncfusion.DocIO.DLS.Rendering.DocumentLayouter

   at Mono.Linker.Steps.MarkStep.HandleUnresolvedType(TypeReference reference)

   at Mono.Linker.Steps.MarkStep.MarkType(TypeReference reference)

   at MonoDroid.Tuner.MonoDroidMarkStep.MarkType(TypeReference reference)

   at Mono.Linker.Steps.MarkStep.MarkType(TypeReference reference)

   at MonoDroid.Tuner.MonoDroidMarkStep.MarkType(TypeReference reference)

   at Mono.Linker.Steps.MarkStep.MarkType(TypeReference reference)

   at MonoDroid.Tuner.MonoDroidMarkStep.MarkType(TypeReference reference)

   at Mono.Linker.Steps.MarkStep.InitializeType(TypeDefinition type)

   at Mono.Linker.Steps.MarkStep.InitializeType(TypeDefinition type)

   at Mono.Linker.Steps.MarkStep.InitializeAssembly(AssemblyDefinition assembly)

   at Mono.Linker.Steps.MarkStep.Initialize()

   at Mono.Linker.Steps.MarkStep.Process(LinkContext context)

   at Mono.Linker.Pipeline.Process(LinkContext context)

   at MonoDroid.Tuner.Linker.Process(LinkerOptions options, ILogger logger, LinkContext& context)

   at Xamarin.Android.Tasks.LinkAssemblies.Execute(DirectoryAssemblyResolver res)

   --- End of inner exception stack trace ---

   at Java.Interop.Tools.Diagnostics.Diagnostic.Error(Int32 code, Exception innerException, String message, Object[] args)

   at Xamarin.Android.Tasks.LinkAssemblies.Execute(DirectoryAssemblyResolver res)

   at Xamarin.Android.Tasks.LinkAssemblies.Execute()

   at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()

   at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__26.MoveNext() PTS.Mobile.Android


Please sign in to access our KB

This page will automatically be redirected to the sign-in page in 10 seconds.

Up arrow icon

Warning Icon You are using an outdated version of Internet Explorer that may not display all features of this and other websites. Upgrade to Internet Explorer 8 or newer for a better experience.Close Icon

Live Chat Icon For mobile