TKG, the architecture of the new version of iGrid.NET (3.0) was changed a lot comparing to the previous versions (2.x). The main difference is that iGrid.NET now consists of two DLLs. One of them is the core part, and the other is the design-time functionality. This was caused by so-called ".NET client profiles" introduced in the .NET 4.0.
To make it possible to find the design-time functionality of iGrid in the VS IDE, it is not enough to place an icon for the control (which points to the core DLL) on the VS toolbox. We also need to have a special registry key with the path to the design-time DLL of iGrid. Here is an example of how to do that in the format of the standard Windows .reg file:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v2.0.50727\AssemblyFoldersEx\10Tec iGrid 3.0 Design DLL]
@="C:\\Program Files (x86)\\10Tec\\Windows Forms .NET\\iGrid.NET 3.0\\Bin\\DesignTime\\"
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v2.0.50727\AssemblyFoldersEx\10Tec iGrid 3.0 Design DLL]
@="C:\\Program Files (x86)\\10Tec\\Windows Forms .NET\\iGrid.NET 3.0\\Bin\\DesignTime\\"
(Correct the path if required depending on your installation of iGrid.NET)
This registration is performed during the demo installation, but if you redistribute the control by yourself, you also need to do that manually.
You have not provided us with detaied info about the problem (what we always ask to do when you contact our tech support service), so this is the first and only idea by now. If it does not help, please, give us more info about the problem - what you are doing step-by-step (starting from the control installation) and what problem you have (a screenshot).
From our side, we can only guarantee that our control will work properly in the "official" development environment from MS, i.e. Visual Studio, but sure we'll do our best to make it possible to use our control in other 3rd-party development environments.