They provide a change log but not to that level of detail. In that case I believe they changed the name of that assembly. From 10.x to 10.x I usually let the errors bubble up and just ad hoc fix them. The system does a good enough job of letting you know the exceptions.
This one has broke again with the upgrade from 10.2.200 to 10.4.400.13.
The code is the same in both, but the assembly references look different, with .400 having 3 different Native Assemblies compared to 10.2.200’s single entry. Please see below, left is the 10.2.200 that works, the right is 10.2.400.13 that does not. Same error message as at the beginning of this thread.
I’m throwing my ‘using’ section here as it may help.
using System;
using System.Collections;
using System.Collections.Generic;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Reflection;
using System.Text;
using System.Windows.Forms;
using Erp.BO;
using Erp.Proxy.BO;
using Erp.Adapters;
using Ice.Adapters;
using Ice.BO;
using Ice.Core;
using Ice.Lib.Customization;
using Ice.Lib.Customization.Designers;
using Ice.Lib.Framework;
using Ice.Proxy.BO;
using Ice.UI.App.UD01Entry;
using Ice.UI.FormFunctions;
using Infragistics.Win.UltraWinGrid;
using Infragistics.Win.UltraWinToolbars;