Some Infragistics controls like WinChart and WinGrid are not displayed properly in the Visual Studio 2008 Designer.When I drag i.e. a WinGrid from the Toolbox on my Form and drop it there the WinGrid will be shown as a symbol with a name on the bottom of the Designer window in a separate area (below the actual form area). I am not the only one in my company who experienced this problem. My working mate had the same problem but he could solve it with a complete de- and re-install of your product. I tried the same but the problem still exists.
I hope you have a solution for this problem already.Best regards, Gerald
i think Infragistics Developer Support would be better able to help you work through this problem. try contacting them at http://infragistics.com/gethelp
I have the same problem but with my ultragrid when I trie to drop ultragrid onto winform in vs 2008. I tried to reinstall but It didn't resolved my problem. I noticed that problem appears when designer of ultragrid tries load. Please for help.
Regards,
Paul
raggiholm,
in my case it happened after an upgrade. I think it was the hotfix installation.
An Infragistics support member sent me the following description:
(A) When working with Base Build version:
In case if you are facing the problem while dragging controls in base build version (8.1.20081.1000 CLR2) then I would like to inform you that if Visual Studio can't find the controls designer, it will display the control as a component in the component tray. This is due to the corrupt installation. In this particular case I would suggest you to uninstall and re-install the NetAdvantage 2008 Volume 1.
(B) After installing hot fix:
As per your previous mail I interpret that you are using the hot fix version 8.1.20081.2013 CLR2. Please confirm whether you have run the Toolbox Utility. Failure to do so can also lead to the controls being shown in the tray instead of the form. If you have not run the toolbox utility then I would suggest you to run the Toolbox Utility or manually remove and re-add the controls into the toolbox.
(C) Working with existing application:
Something in your project must still be referencing old assemblies. Check all the references in the sample application the references should be of correct version i.e. 8.1.20081.2013 CLR2. You may need to look at the License.licx file and make sure that file does not reference old version assemblies. In order to bring the old application in tandem with the latest hot fix installed on your machine I would like to suggest you to please run the Project Upgrade Utility.
Make sure your sample application does not reference the .Design assemblies for the controls on the form. These assemblies should be in the GAC, but not referenced by the project directly.
The hint with the License.licx file did it for me.
I hope it helps.
Regards, Gerald
I have this same problem, the chart doesn't appear on the form. I have reinstalled the product and verified that dll's are not local. I tries the debugging procedure and no exception is thrown (I verified that the process is correct). What is the solution of this? There seem to be numerous controls present this behaviour (f. ex. UltraCalendarInfo, UltraGauge, UltraListView, UltraTree).
it sounds like you don't have the Design assembly in your GAC, which explains why an uninstall/reinstall fixes the problem. it could also be the dlls copied locally in your application's "bin" folder, which causes problems at design time. there could be other causes to this problem, though.
try attaching another instance of visual studio to debug this problem. that is,
1: open another instance of VS.
2: select Tools > Attach To Process... and select "devenv.exe" to attach to that process. make sure "Managed Code" is checked.
3: in the Debug > Exceptions dialog, make sure you are set to break on all managed code exceptions.
4: in the Tools > Options dialog, under Debugging, make sure "Break when exceptions cross AppDomain boundaries" is checked.
5: go back to the first instance of visual studio and reproduce the problem by adding a chart or grid to your form.
the debugging instance should break at some point when visual studio throws an exception - most likely you will have a FileNotFoundException due to a missing assembly in your GAC, but whatever error you see should be a big help.