|
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 structureExample NuGet package structure changes have been shown below.
Modified NuGet packagesNuGet 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.
Follow the below steps to update the NuGet package structure changes in your project
|
This page will automatically be redirected to the sign-in page in 10 seconds.
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.
So has the Nuget package source url changed?
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).
Regards,
Dheepa Kumar
I have upgraded ALL nuget packages to version 16.2.0.42 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