Info: how to get rid of NuGet references

[ic2]

After upgrading to the latest version 32.x from 29.x of Syncfusion Essential Studio, my programs gave a message that I was using a unlicensed version. I tried to reference all necessary DLL's which was not possible. It turned out that the main library was a NuGet link (with a different icon) which somehow in the background also included other DLL's and could not be deleted. I hate NuGet (and VS) for many reasons and this added another reason. Note: I did try to update the NuGet package first, but the problem remained. As a NuGet reference does not show you any details either, this stupid product (of course developed by Microsoft, via Outercurve Foundation) leaves a user completely in the dark about references & versions.

Syncfusion support, which is really great, sent me the below instructions which helped me get rid of the NuGet reference, so I could include the latest DLLs myself. WIth visible names & properties and my license message issue was solved too.

In case anyone get's across a NuGet problem, I include the instructions from Syncfusion below.

Dick

------------------------------------------------ -------------------------------------------------------------------------------------------------------------------
Syncfusion.SfKanban.WPF is coming from NuGet, not from your local folder. Visual Studio protects NuGet references, so the “Delete” option is disabled in References.

Build output prefers the NuGet package version. As long as the package remains installed, it will keep dropping 29.2462.4.0 into your bin\Debug, regardless of what’s in precompiledassemblies\4.6.2.

The Syncfusion.Licensing DLL should also be referenced (and a license key registered at runtime). If not, you’ll get license popups or runtime issues even after you fix versions.

Follow the steps below to resolve this issue. This approach ensures consistency and prevents conflicts that can occur when mixing local DLLs with NuGet‑managed assemblies.

Close all designer windows in VS (XAML designers can lock assemblies).

Find your package style:
If your project has a packages.config file → you are using the old packages.config style.
If not, open your .csproj → look for <PackageReference .../> entries (that’s the new PackageReference style).

Uninstall the old package:
Package Manager Console (Tools → NuGet Package Manager → Package Manager Console):

Code: Select all

Uninstall-Package Syncfusion.SfKanban.WPF -RemoveDependencies -Force
Uninstall-Package Syncfusion.Licensing -Force

2. Or via Manage NuGet Packages… → Installed → Uninstall.

Clear caches throug VS (prevents old 29.x from being restored):
Tools → Options → NuGet Package Manager → Clear All NuGet Cache(s).

Delete build artifacts (while the package is uninstalled):
Close VS.
Delete the project’s bin and obj folders.
If using PackageReference, also delete obj\project.assets.json if present.

Add local references:

Right‑click References → Add Reference → Browse…
Add:
C:\Program Files (x86)\Syncfusion\Essential Studio\WPF\32.1.19\precompiledassemblies\4.6.2\Syncfusion.SfKanban.WPF.dll
C:\Program Files (x86)\Syncfusion\Essential Studio\WPF\32.1.19\precompiledassemblies\4.6.2\Syncfusion.Licensing.dll

Build and verify bin\Debug shows version 32.1.19.

[Chris]

Hi DIck,

Don't even get me started about nuget...

Good thing at least is that nuget package files are actually zip files, which contain the dll file which is actually used. So you can just get the dll from it, add a normal reference and get rid of that nuget thing completely...

[ic2]

Hello Chris,

Indeed. Sometimes it even works. I normally do the same as, rename to aa zip file and retrieve and add the DLL's manually; I think this went differently here because I started working from the Syncfusion sample project for which they must have used NuGet.

Anyhow, good to know to get rid of it again.

Dick