Building Infragistics WebUI Design Assemblies

The Infragistics Design assemblies (Infragistics.WebUI.Design.v1.1.dll, Infragistics.WebUI.UltraWebGrid.v3.2.Design.dll, etc.) have dependencies on 7 specially built Infragistics Win assemblies listed below.

Infragistics.WebUI.Design.Shared.v3.2
Infragistics.WebUI.Design.Win.Misc.v3.2
Infragistics.WebUI.Design.Win.UltraWinEditors.v3.2
Infragistics.WebUI.Design.Win.UltraWinTabControl.v3.2
Infragistics.WebUI.Design.Win.UltraWinToolbars.v3.2
Infragistics.WebUI.Design.Win.UltraWinTree.v3.2
Infragistics.WebUI.Design.Win.v3.2

These assemblies are located in the Global Assembly Cache (GAC). If you open up one of the Design projects, you may notice that these references appear with an exclamation point inside of a yellow triangle in the references list. This is because Visual Studio was unable to find these assemblies, since it does not look in the GAC for project references. To resolve this, you must re-add the references to your project by browsing to the file. Since these files are only in the GAC, you must first copy the files out of the GAC into a new folder. Unfortunately, this can not be done from Windows File Explorer, as the GAC subdirectories are all hidden. Instead, open a Command Window. You can use the Visual Studio .NET Command Prompt option in your start menu. From the command line, navigate to %windir%\assembly\gac You can use the following command –

cd %windir%\assembly\gac

You’ll notice that there is a folder for each uniquely named assembly in the GAC. Navigate into each of the assembly folders with the same names as in the list above. Inside the folder you will notice there is at least one directory uniquely named with the Assembly Version Number, and it’s public key token.
Navigate into the proper versioned folder, and you will find the Assembly file inside.
Now you can copy the assembly into the folder of your choice.

Statement on Source Code Releases:

All .NET products are fully regression tested upon each major volume release, and updated source code is posted approximately one week after a major release.

Currently we publish hot fixes at interim periods between major releases, but typically do not re-release the source code for every hot fix published. Hot fixes contain fixes for specific problems. They are tested only for those reported issues. Some in-depth testing is conducted but, as you will note on the hot fix download page, we advise developers to only install the hot fix if they have read that it resolves a problem they are having. As always, please exercise caution as the potential for unforeseen behavior may occur as the result of a hot fix.

Infragistics strongly recommends waiting for volume-release source code if possible, rather than interim-released source code.