Forums Ultimate UI for WPF
Your Privacy Matters: We use our own and third-party cookies to improve your experience on our website. By continuing to use the website we understand that you accept their use. Cookie Policy
Close
Graham Stoneman
125
NuGet package names changed in 2016.2
posted

Hi,

We use the 'version free' NuGet packages, but in latest 2016.2 release the names of all the NuGet packages have changed.  Previously they were InfragisticsWPF.*, now they all are all Infragistics.WPF.*  Is this a mistake?  The version free packages are supposed to make upgrading easier, but the name change prevents the VS package manger or the update-package command from detecting the newer versions.

Thanks very much,

Graham.

  • 1530
    posted

    Hi Graham,

    The pattern for the NuGet packages IDs wasn't following the standard. In 16.1 the dot was missed since it was the only product that offered nuget packages. When we added NuGet packages for multiple other products, the issue was found and corrected.

    The pattern our packages should be following should start with “Infragistics.<Product>”. So that’s why it’s coming up as Infragistics.WPF. It’s the same for other 16.2 products like WinForms and ASPNET. We’ll be having the packages up on our public NuGet feed for licensed customers at some point.

    Sincerely,
    Teodor Tenev
    Software Developer