I am trying to install the toolbox into VS 2008 and the command that I am attempting to run is Infragistics2.ToolboxUtility.exe /t 9 and it does not work. Does anyone have samples of a proper command line that will work?
I am using VS 2010 Ultimate edition. I have Infragistics 2008 Vol 3 and tried to run the toolbox utility in Win7 using cmd (running as Admin). Could not work either. Error that was displayed: "Argument 1 was Invalid.". So I have to manually add the components. The Infragistics controls are able to load in VS2010.
I almost have it....because of another issue (toolbox grayed out for most items) I installed framework 3.5, updated SP1 for VS2008 and framework 3.5. Fixed part of the problem, now I have about 1/2 the items I should have. I also uninstalled and re-installed NetAdvantage.I then tried the solution mentioned above (shortcut in programs from start menu "Create NetAdvantage Visual Studio Toolbox Tab"). Managed to successfully get through all the commands with no arguements. The tab NetAdvantage8.3... is now showing in the toolbox, however only if "show all" is checked and it remains grayed out, so unusable, but it is there. Just thought I would pass this along in case the service pack update may help...
Leslie
This does not work for me either. I get the following.
VS: 9.0
Removing Tabs...
Removing tabls... COMPLETE
Removing tabs...
Removing tabs...COMPLETE
Argument 1 was invalid
What next?
It doesn't work for me too. If I run it from the start menu (Infragistics2.ToolboxUtility.exe /v 8.2) it pop-ups usage dialog.If I run it in the following way: Infragistics2.ToolboxUtility.exe /v 8 it starts to work and I get the following output:
Begin processing NetAdvantage version 8
VS: 8.0Removing Tabs...Removing tabs...COMPLETEArgument 1 was Invalid.
Please solve this.
Hi
I did what Tom did and it worked right up to the point where a log file was generated saying that controls had been successfully installed and then the last line said that they in fact had NOT been successfully installed, so i logged a support call and included the contents of the log file. I then proceeded to add the controls manually - seems to be working now.
Chris - South Africa