Feature Spotlight: Infragistics WPF NuGet Packages

On Infragistics product ideas website there is a highly voted product idea titled “Use Nuget for Distribution”.  Well, it turns out that Infragistics does have NuGet packages for some of their products that are installed locally with the Infragistics Ultimate Installer.  You just have to know where to look.

Where can I find them and how do I use them?  Good question! 

Find and Extract Packages

Simply navigate to “C:\Program Files (x86)\Infragistics\2016.1\WPF\NuGet Packages” and you will find two zip files.  One for the standard assemblies and another for the “version free” assemblies.

nuget packages location

Extract the content of the zip file and you will see the available NuGet packages for all of the WPF controls.

Create a Local Repository

Next create a new folder somewhere on your hard drive to be used as the location of your local Nuget repository.  After you create this folder, copy all of the Infragistics WPF NuGet packages and paste them into this location.

Infragistics WPF nuget packages

After that, open up Visual Studio and open the NuGet Package Manager Settings

open package manager settings

Now, add a new NuGet Package Source and set the “Source” to the location of your newly created folder containing the Infragistics WPF NuGet packages.

create new nuget package source

Using The Infragistics WPF NuGet Packages

Now, all you have to do is create a new WPF application in Visual Studio and open the NuGet editor.  This can be done by right-clicking the solution and selecting “Manage NuGet Packages for Solution”.

In order to add the Infragistics WPF NuGet packages you must change the “Package Source” to use the local repository you created in the previous steps.

change nuget package source

Once you do this, all of the Infragistics WPF NuGet packages will be available.

add Infragistics WPF Nuget Packages

Now search for the control of your choice, add the package, and you are ready to rock-and-roll!

That’s it!  It’s that simple.  Now go have some NuGet fun.

As always, feel free contact me on my blog, connect with me on Twitter (@brianlagunas), or leave a comment below for any questions or comments you may have.


Comments  (7 )

Damon Wilder Carr
on Wed, Sep 21 2016 7:02 PM

Your icon is not resolving for these packages. Try to browse to: www.infragistics.com/tempicon.png

And you'll see what I mean.

Thanks,

Damon

Brian Lagunas
on Wed, Sep 21 2016 7:22 PM

Thanks for reporting this.  We'll get this fixed.

Jon Heaton
on Wed, Nov 23 2016 1:31 PM

If I wanted to add these nugets to my private nuget server instead of adding the package source locally, how would I do that?

When I put the nugets on my nuget server, I am currently having licensing issues when I pull them down to my application.  I get the "Unlicensed Trial" watermark in the bottom right corner.  Do I need to install Infragistics on my nuget server for this to work?  If so, does that violate the license agreement?  If that worked, it would mean that anyone in our company that got the DLLs from that nuget server would have fully functional DLLs, right?

FYI: The 2016.2 installer only ships with the VersionFree nugets and not the versioned ones.  I did post on the forum earlier today, but haven't heard back yet.

Brian Lagunas
on Mon, Nov 28 2016 10:22 AM

When we release 16.2 we accidentially shipped the trial NuGets instead of the licenced versions.  This is being fixed and the proper NuGets will be available in the next SR.  Yes, we only ship the versionless with NuGet.  NuGet has built-in versioning and it would not be wise to ship a versioned NuGet package ID, otherwise you would not be able to upgrade your packages properly.  Essentially, when using NuGet there is absolutely no reason to use the versioned assemblies.

bryant
on Fri, Jan 13 2017 10:31 AM

I have to respectively disagree regarding versioned assembly nugets.

Although I agree you *shouldn't* need versioned assemblies with nugget, this assumes you own your whole world.  Unfortunately in enterprise development this is not the case in many instances.  You often have multiple (potentially independent) teams (on potentially different release schedules) that role up into one shell   Coordinating teams to keep things in sync and upgrade to new versions is a PITA.

I don't think the "package ID" should contain the version information however it should include the word "versioned" (or similar) and the version of the assemblies be the version of the package.

Neil Benn
on Tue, Mar 14 2017 6:34 AM

I tried to download ultimate and the nuget packages are not there.  How can I obtain the installer that has these nuge packages?

Neil Benn
on Tue, Mar 14 2017 6:39 AM

Scratch that - it is an option on the installer!