Hello,
occasionally VS2010 takes a lot of time when I open the Toolbox.
I created a log file and as far as I can see, the infragistics packages are not installed properly? I renamed the log file from .txt to .xml and loaded it into MS excel. Then I filtered for error.
To upload the file i zipped it.
vslog.zip
Wolfgang,
Manually adding assemblies to the Visual Studio Toolbox has been a feature for a very long time, and common way to build your tabs, other than using Windows Explorer and searching for the location and selecting them all. The delay you are seeing is to be expected because Visual Studio has to generate the list of components, and he have quite a few.
Let me know if you have any questions.
short update, I deleted the Infragistics tool box tabs but the problem still persists. As soon as the toolbox is being opened, the delay occurs. And right now, I have observed, that the infragistics items / tabs got restored...
right now I tried to uninstall the extension via the extension manager. It seems like older or earlier installed versions were hidden by newer ones. So I had to repeat uninstalling until no extension from infragistics was visible in the extension manager.
I did this for VS 2010 and 2012, because this are the most recently used IDEs I have installed.
It seems like uninstalling all Infragistics extensions has no effect on the startup time of Visual Studio 2010.
Readding of toolbox items... I never tried it the way you describe. Is this possible in VS2010 and VS2012?
I will try to readd the toolbox items tomorrow. But I dont think that this will help. Perhaps first resetting to factory defaults.
Greetings Wolfgang
Hello Wolfgang,
Thank you for following up.
Uninstalling the Infragistics Visual Studio Extension shouldn't have any impact on the toolbox or the versions you have installed. It should provide a clear indication if the utilities we provide are causing some sort of issues with Visual Studio and how it loads the toolbox when the designer is opening and either adding components for the first time or during continuous (daily) use.
After you uninstall the Visual Studio Extensions and if you continue to see performance issues with the toolbox, then I recommend deleting and re-adding the tabs in the Toolbox manually.
This can be done by right-clicking in the toolbox and individually adding and deleting tabs for each version. 1.In Windows Explorer, navigate to the Bin directory where the Infragistics Professional assemblies are installed. The assemblies contain the DLLs that you want to add: C:\Program Files (x86)\Infragistics\2017.2\Windows Forms\Bin
2.Select the DLLs that contain the Infragistics Professional controls/components you want to add to the Visual Studio toolbox.3.Copy (via Ctrl+c or through the right click context menu) the DLLs4.Select the tab you wish to populate and paste (via Ctrl+v or through the right click context menu).
It might also help to check how the performance is handled when Visual Studio has all but the inbox (default) tabs in it's toolbox. Knowing whether or not the issues you are experiencing is directly caused by our components is vital and testing when they're not present is necessary.
If the issue(s) persist when the Infragistics toolbox tabs are no longer present then this would mean the issue(s) may pertain to Visual Studio or some other external extension.
Hello Michael,
I appreciate your efforts to help me. But unfortunately I cant spend that much time in uninstalling and reinstalling the Infragistics Tools. Because we have many different versions installed (from which I need to reinstall exactly the previously installed version, so I have to look for the correct installer) and because I have so many different visual studios installed - I cannot uninstall VS2010 without affecting the newer ones.
Is there no other possibility? Disabling the tool box packages and then enabling them one by one?
I dont understand the difference in the two options from your first question. We always use the toolbox utility to create the toolbox registers for infragistic tools, but it seems like the utility doesnt always run correctly, so I am missing some or all parts of the tools. Rerunning the utility doesnt help either. But this might be a second problem.