How to resolve issues with Toolbox items

DOES NOT WORK AT ALL FOR ME!!!

Win 7 Ultimate (x64) Visual Studio 2010 SP1 DevExpress 12.1.4, Just installed toolbox for "DX.12.1: XAF Templates", "DX.12.1: XAF Action Containers", "DX.12.1: XAF Web.v12.1"

Anybody at DevExpress is going to fix this for GOOD?

It is difficult to provide you with any solution based on this information. First, try to reset the toolbox. If our toolbox items were hidden for some reason, they will appear.

If this doesn't help, please create a separate ticket concerning this issue. In addition, attach a Visual Studio log.

Step 1 to 6 worked for me!

I had to remove an older version of DevExpress and then follow the steps above in order for this to work. I could not get both the old version and the new version to work together.

It is possible to have toolbox items of version 12.1 and prior versions together. Try to reset the Toolbox and then run the ToolboxCreator of a prior version. This should resolve the issue.

I am experiencing Issues 2 and 3 when the RIA toolkit is installed. Unfortunately none of the above worked for me. This has to be fixed since it is affected the DevExpress controls and making them useless.

Removing the following keys should resolve this issue. After this, VS shouldn't load the RIA services toolbox.

In a 32-bit Windows:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Silverlight\v4.0\AssemblyFoldersEx\Ria Services v1.0 Silverlight Libraries\Toolbox
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Silverlight\v5.0\AssemblyFoldersEx\Ria Services v1.0 Silverlight Libraries\Toolbox

In a 64-bit Windows:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SDKs\Silverlight\v4.0\AssemblyFoldersEx\Ria Services v1.0 Silverlight Libraries\Toolbox
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SDKs\Silverlight\v5.0\AssemblyFoldersEx\Ria Services v1.0 Silverlight Libraries\Toolbox

Perhaps, something else is causing the issue. Would you please create a separate ticket along with a Visual Studio log file.

Solved issue for me only after reapplying VS 2010 Sp1.

Problem solved for me after running the script 64bit.reg.

- ResetSkipPkgs did not work, neither was there a logfile created
- Reapply SP1 did not work, it failed during the process because of some missing files... neither cancel of the process was possible (missing files as well...)
- Running Script 64bit.reg WORKED

We are missing the Toolbox Creator!

- It still takes a very long time to start Visual Studio now.
- What do you mean with "After issues with this assembly are resolved"? How?
- DevExpress Silverlight Demo does not work anymore. Even after the repair function. The Error Message is: "Ein Fehler ist bei der Weitergabe des Befehls an die Anwendung aufgetreten"

Hi
I'm getting all the time mail regarding this issu how can handel it ?
thanks

Please give us back the toolbox creator. I have to switch versions of devexpress a lot. I don't like keeping all the different versions in my toolbox all together because it is WAY too easy to use controls from the wrong version. I used the toolbox creator to easily switch control sets when I worked on different projects.

To Danny Melki:
You receive an email notification because this article is added to your favorites. Just remove it from there.

To Bradley Uffner_2:
The current model of toolbox registration is more correct because it uses native methods to register toolbox items. We don't plan to return to the previous model. Sometimes we can't resolve toolbox issues of our customers with the old model.
For your scenario, you can remove unnecessary records about our toolbox items from the registry and restore your registry when they will be necessary.

No toolbox items for me after installing 12.1.5 - had no problems with 12.1.4. Actually had no Programs menu items either but a Repair fixed that. No such luck with the Toolbox.
No "Microsoft.VisualStudio.IDE.ToolboxControlsInstaller.ToolboxInstallerPackage in the ActivityLog.xml" but the Registry entry (64-bit Windows version) *is* present, however Toolbox\Default Items under that key was set to 0. Just tried changing it to 1, restarted VS2010 and got my toolbox items back! Any idea how it got changed to 0 after running 12.1.5 Update??

We have verified the 12.1 installation and made sure that it does not modify registry keys. Likely, the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\10.0\Packages\{2c298b35-07da-45f1-96a3-be55d91c8d7a}\Toolbox\Default Items key was set to 0 initially.

So after trying everything in this article (and using a few "choice" words) I decided to peek at the comments. I did what Simon Hewitt tried. I navigated to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\10.0\Packages\{2c298b35-07da-45f1-96a3-be55d91c8d7a}\Toolbox\Default Items and changed the value from 0 to 1. Voila!!!

Thanks Simon!

Thanks Simon!

I reset the toolbox in Visual Studio 2012 RC and they came back. I had to delete the version 11 tabs manually.

Hi David,

This behavior is correct and it works in a similar way as standard VS toolbox items. If you do not need to show our controls' toolbox items, either uninstall our products or remove DX items from the following registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\10.0\ToolboxControlsInstaller

If you still have any problems, I would appreciate it if you create a separate ticket about it and describe your problem there.

I also noticed that, at least for me, the .NET project needs to be a .NET 4.0 project for the DX.12.1 toolbox items to show. I opened an older .NET 2.0 project in Visual Studio 2010, and the DX.12.1 items were not in the toolbox.

Separately from that, I also encountered the missing toolbox items after upgrading to 2012.1.5. I deleted the (hidden) .TBD files in the "%USERPROFILE%\AppData\Local\Microsoft\VisualStudio\10.0" folder (as described in the solution above), then ran the appropriate reg file (the 64bit version for me) from the scripts.zip file above, then opened Visual Studio 2010, opened a (.NET 4.0) ASP.NET web project, opened an ASPX file, then opened the toolbox. There was a long delay and several messages about adding items to the toolbox, then the toolbox was correctly displayed with all the DX.12.1 entries. On subsequent openings of Visual Studio and projects - there was no delay in opening the toolbox.

I tried everything as above for missing toolbox items and it was setting the default items key to 1 as Simon described that fixed. Thanks for adding the feedback Simon.

Running the correct reg file and setting the default items key to 1 seems to have fixed it for me....whoohoo. Thank you DevExpress and Simon

I installed Visual Studio 2010 on a Windows XP (32bit) machine that also had Visual Studio 2008 installed with DXperience 11.2 installed. I updated the DXperience sweet to 12.1.5 and all the DevExpress Toolbox Items vanished in Visual Studio 2010 but could still be seen in Visual Studio 2008. None of the above fixes worked for me. As a last resort I decided to re-install Visual Studio 2010 and hay presto the DevExpress Toolbox items are back. I did notice that the DevExpress Toolbox items are not loaded until you open your first Project after re-installing.
Hope this helps anyone else having the same trouble.

I'm trying to put all these comments and responses together. From what I've gathered if you've installed v12.1 then all other versions are unusable unless you uninstall 12.1? I say this because I have a project that uses 11.2 but after installing 12.1 I no longer see the 11.2 toolbox, just the 12.1 items. Even though all my references are set to the 11.2 assemblies. If this is your approach then you have failed the way many of us use your tools. Is this an accurate understanding? If not,please shed more light on how to use different versions for different projects. Thanks

I find it amusing that those that using Express editions (roughly 50% of your customers?) are forced to refer to a 5 year old article that is not only very time consuming and error-prone, but also does not describe how to register item templates (which have likely have not install correctly along with the toolbox items).

DevExpress has a great looking and well built control suite, but actually getting those controls into the IDE requires you to use their slow abomination of an installer.

Installing two different versions (VS 2008/11.1.11 + VS 2010/12.1.5) is really terrible!
It totally annoying that this does not work.
Your components are really great, but your installers are absolute real big shit.
I wish that your boss read this!
Well, then I'm going on with your registry experiments, I've still got the whole weekend time to repair the registry.
Let's see what happens.
Thank you for this great surprise ...

i just right click on the ToolBox and selected "Reset ToolBox"

The 'Reset ToolBox' thing does not work, it gets duplicated again the next time you open VS. You MUST follow the instructions explained above for it to be permanent. I did it and it worked!!

I had issue 1...so steps 1-6 and then adding the missing registry key worked for me. Thanks, however it seems like these steps could be automated in the next installer release...

My entries installed correctly on the initial install of 12.1 on VS2010. Then, cleaning up my machine, I uninstalled 11.2.5, and that removed all of my DevEx toolbox entries.

Steps 1 through 6 got them back, but of course, it wiped out any groups that I had created manually with other controls :(

These steps worked for me when I upgraded to 12.1.4 but they do not for 12.1.5. The scripts do nothing to resolve this and when i was following the above instructions, there is no "ActivityLog.xml" to review on my entire machine. How am I supposed to get work done when this does not work??????

Steps 1-6 worked perfectly!!!! Thanks!

Ted, most issues with toolbox items relate to a corrupted toolbox cache. So, it is necessary to reset this cache to resolve the issue. Unfortunately, this removes all custom toolbox pages and there is no a way to avoid this except to recreate them.

Msprygada, we would appreciate it if you create a separate ticket regarding your problems with toolbox items. Please clarify what version Visual Studio you are using, the OS you are using, and where you have found the VS log.

If you use the "C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv" /ResetSkipPkgs /log command, a log will be in the C:\Users\YourUserName\AppData\Roaming\Microsoft\VisualStudio\10.0 folder for VS 2010 and Windows 7.

I did....(http://www.devexpress.com/Support/Center/p/Q286935.aspx). I entered it yesterday first thing in the morning and DevExpress has yet to respond. I have reset the cache several times to no avail. I did run that command several times yesterday and I could not find a log file on my entire computer (ActivityLog.xml). I am using VS 2010 SP1, Windows 7 32 bit SP1.

Thank you for creating a separate ticket. We will answer you in that context.

For Slow loading of toolbox steps, also delete key:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319\AssemblyFoldersEx\RIA Services Toolkit Libraries\Toolbox

re: Slow loading:

Better yet, simply follow these steps if you need WCF RIA and have loading issues:

1) uninstall RIA Services and Sept 2011 Toolkit.
2) Install RIA services again (but not toolkit yet)
3) run devenv with /ResetSkipPkgs switch
4) close VS after all is loaded
5) Install Sept 2011 RIA Toolkit
6) Start VS Normally
7) After VS loads, close it again
8) Remove the Toolbox keys for RIA services as described in this article.
9) Additionally, remove the key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319\AssemblyFoldersEx\RIA Services Toolkit Libraries\Toolbox
10) Open the "%USERPROFILE%\AppData\Local\Microsoft\VisualStudio\10.0" folder and remove all .TBD files.
11) Start VS normally (WITHOUT the ResetSkipPkgs switch)
12) After intial tdb build and VS load is complete, close VS again.
13) Now your problem should be resolved and you can use VS normally without delayed loading.

VIOLA! Worked for me.

Thank you Gosha for this explanation.
In my case, I installed the demo version of DXExperience this was 12.1.5. After some time, I deinstalled it and installed the latest WPF version, this was 12.1.7 After that I could not find all the DX.12.1 Toolbox items. Following your post I found out that the subkey {2c298b35-07da-45f1-96a3-be55d91c8d7a}\Toolbox was missing. I recreated it using your script and that was the solution.

Hi to All,

Guys - we have prepared a toolbox diagnostic tool that allows you to perform all the above mentioned operations automatically. I am going to update this message's answer accordingly.

I have DevExpress 11.1. I have two versions of Visual Studio, 2010 and 2012. 2010 has all the correct tool box grouping and components. In VS 2012 I cannot get the tool box populated with the DevExpress components no matter how many times I rerun your solutions. I can of course drag and drop the dlls directly into the Toolbox but this provides a huge mess of components. I would be interested in your toolbox diagnotic tool.

One more thing, all tool box items can be added individually to my toolbox using VS2012 "Choose Toolbox Items" but this is a real pain and again they end up in groups with all the Microsoft tools.

Oh as I am not in control of the development tools it would appear at the moment that moving to a later version of DevExpress is not a valid option. Can you get my DevExpress V11.1 tools to show in Visual Studio 2012 please?

Thank you for contacting us, Phil. Version 11.1 does not support Visual Studio 2012. That is why there are no toolbox items. To correctly use our controls in Visual Studio 2012, update your version to the latest versions, 11.2 or 12.1.

Thanks for your prompt response.

After running the ToolBar analyzer i got all the controls except for Silverlight. I am using DeEx v12.1.5 on a Win7 64 bit and VS2010

Hi Ahmed,

Please create anew ticket and attach the corresponding logs provided by the ToolboxAnalyzer.

Hi,
Just a small remark about the ToolboxAnalyzer tool.

I had to use it today but encountered a small problem with it. It went to the step where it starts Visual Studio (which succeeded) but then it looked like it was blocked. I waited more than 15 minutes and then manually closed Visual Studio. The tool then continued and the process was successful.

Apparently it could not close VS.

Hi Geert,

Thank you for your comment. You are right, in some circumstances the ToolBoxAnalyzer may not be able to shut down the Visual Studio. This is a really heavy application, and it is almost impossible to imagine and catch all situations in which the studio may hang. Nevertheless, we have done all possible things we can imagine to make the ToolboxAnalyzer work stable and make sure that the studio is closed. I would like to note that the ToolboxAnalyzer starts the studio in Debug mode. It attaches to the studio as a debug process and tries to collect and analyze the log files. This may significantly increase the loading time. So, depending on the Visual Studio adjustments even half an hour may be acceptable. Anyway, if you wish, we can research the behavior on your side further. In this case, create a new ticket and attach all logs to your message.

Thanks,
Stan

I had set my notebook down on the bed and left for about 20 minutes. When I came back, it had overheated and shut down (I had blocked the air vents and the system crashed)... When I started the notebook back up and started Visual Studio 2010, all my 12.2 toolbox items were gone. The 12.1 toolbox items were still there. though.. I ran the ToolboxAnalyzer program and it fixed the problem... You might want to consider adding this in the tools directory during install (like you use to do before changing the way you create toolbox items).

Thanks for making it easier to fix this issue.

Where is the script files? (scripts.zip)

Hi Jimmy,

You do not need to use scripts, because the ToolboxAnalyzer automatically patches required registry keys. Just download it, run on a problem machine, and follow instructions. If this does not help, create a new ticket and attach all files generated by this tool.

This "tool" did not work for me. It ran without errors, but all it did was pull back in 12.1 assemblies which I had to delete. I Manually added the controls back. It was a major pain in the ass. Simple things that I use all of the time (like the Ribbon Control and Grid Control were missing.

I cannot imagine the frustration of a new potential customer trying out your tools for the first time. I'm certain you are losing sales because of this. You need to get this fixed and working Out of the Box.

Hi,

Starting with version 12.1, we use native toolbox item registration mechanisms. Out installer sets up all required settings to add our toolbox items. However, some our customers may have their own toolbox settings that prevent our toolbox item from being displayed. That's why we may need to ask a developer several questions when fixing the toolbox. Most of the problems can be resolved with the help of our ToolboxAnalyzer by clicking on two buttons, but there are very specific cases when we need to research ToolboxAnalyzer logs. We do our best to make our toolbox item appear out-of-the-box in all cases. But currently we have not found a way to do this.

To help us improve our tool, would you please create a separate ticket and describe your scenario in greater detail? What assemblies and why do you need to remove?

This saved me a lot of time... thanks!

Thanks, this speeded up the project loading times greatly.

I am having a lot of issues with opening projects when CodeRush is installed. It often takes over a minute, sometimes 2 to open the project and be able to start editing. I tried running this tool, which says:

"ToolboxAnalyzer has not found references to DevExpress toolbox items in this Visual Studio version. Please run the installation in "Repair" mode and check the toolbox items again."

I ran a repair for CodeRush and then tried the tool again and get the same message.

Jonathan: CodeRush is a separate tool that does not relate to our components and does not affect their toolbox items. So, the ToolboxAnalyzer cannot help in this situation.

I have extracted your comment to a separate ticket created on your behalf: Q371925: Issues with opening projects when CodeRush is installed. We will process it shortly. Your patience is greatly appreciated.

ToolboxAnalyzer did the trick for me. Thanks

I am having this problem also. I tried running the Analyzer, and it did not solve the problem. Then when I try going to "C:\Users\<username>\AppData\Local\DX Toolbox Analyzer" I find that this path does not exist on my XP computer. Nothing similar to it exists in "C:\Documents and Settings\<username>\Application Data\...". The toolbox analyzer sent out an email with attached log files to "Auto Reply - Stellana Laxå ".
At present I am not able to build any of my projects that use DevExpress.

Hi Mike,

Our ToolboxAnalyzer tool removes its logs on closing. So, just click the "Save Logs" button to send log files, and our tool will collect the required files automatically. For further processing this issue, I have created a separate ticket on your behalf. Please see the Q372916 ticket.

I tried your toolbox tool and it did NOT put the DX Experience controls into my toolbox.

Hi Robert,

I have extracted your inquiry in a separate ticket for further processing. Please refer to the Q373393 ticket.