Visual Studio 2010 custom user controls and the Toolbox

Question

1.00/5 (1 vote)

See more:

.NET2.0

, +

We just recently upgraded Visual Studio from 2005 to 2010. Our solution was not upgraded to the 4.0 framework, as our user base is still on the 2.0 framework. The solution loads fine, runs fine and we were ready to get back to work.

We have hundreds of custom user controls. When in 2005, we created a user control in our solution, it would show up in the toolbox and from there we could drag & drop the user control onto any given form.

As we were developing, we noticed that our custom user controls are not showing up in the Toolbox in Visual Studios designer. Has anyone ran across this issue? How were you able to get them to show up?

Thanks!

Posted 20-Jul-10 4:19am

jasonHall

Add a Solution

2 solutions

Solution 2

A colleague of mine found the problem. For some reason, there was a conflict with Visual Studio 2010 and the install of Crystal Reports 2008 with SP2. We uninstalled & re-installed Crystal Reports 2008 with SP2 and the Crystal Reports 2008 runtime and now our custom user controls show up in the Toolbox.

Posted 7-Jan-15 10:29am

jasonHall

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

jasonHall · Accepted Answer · 2010-07-20T12:04:00