468,110 Members | 1,522 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 468,110 developers. It's quick & easy.

"Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information."

hi there

i have this error in VS2005 DEV Edition

"Unable to load one or more of the requested types. Retrieve the
LoaderExceptions property for more information."

i have create an windows forms application (exe) and in the same project i
have create 2 forms

form1 and form2 , and form2 inherits from form 1.
in the form1 designer it looks ok, but when i open form2 designer ... not ok
it throws this error "Unable to load one or more of the requested types.
Retrieve the LoaderExceptions property for more information."

can someone help me ???

thks
JSB
Nov 23 '05 #1
5 63313
I think you mean the bug somebody already found a work-around for in the
"User Control Designer Errors is [sic] VS2005 RC1" thread.

Change your AssemblyInfo.cs files in the UserControls DLLs as follows:
[assembly: AssemblyVersion("5.5.5")]

Where 5.5.5 is any hard-coded version number. The problem was the .* in it
causing the UserControl to have an auto-generated version that's different
than what your other DLL is expecting. As soon as you recompile it with
changes or something, you get the Unable to Load error.

BTW - Notice I called it a BUG. I truly believe it's a bug. There's a
rational explanation for what it's doing, but it is bound to cause a little
frustration for a lot of people.

Happy coding!
Jan 25 '06 #2
rob
This does not work for me. Actually the user control is not in a dll
but in the very same project. Therefore, I don't see that versioning
can be the problem. This thing is like SUPER annoying. Here is MS
claiming how much productive developers can be but stuff like that
wastes like so much time. Anybody has a real fix for this?

Feb 1 '06 #3
Rob you're an idiot

Feb 27 '06 #4
rob
mi****************@gmail.com wrote:
Rob you're an idiot


What the heck is that answer for...

Feb 28 '06 #5
raj

Workaround Description:
You would come across this error while trying to view a user control in
the design time that has third party controls in it. ( eg: sync fusion
control). The user control should render fine if it is built using the
regular windows controls.
Reason:- Whenever you create a user control, the .net framework
searilizes the controls into XML (resx file). The new versions of
visual studio (eg: VS2005) will be able to deserealize only the user
controls that are built using the regular windows controls in the
previous version (eg: VS2003). But it will not be able to deserealize
the resx files of third party user control. So all you need to do to
fix the problem is to recreate the resx files for the user controls
with the new version of visual studio.

Workaround Steps:
Heres how you do it.

1. Open windows explorer and go to the folder containing your third
party user controls.

2. Look for the resx file associated with your user control and rename
it (eg: userControl1.resx to userControlOld.resx). You will not need
the renamed resx files but you have it just in..

3. Open your visual studio project/solution and click on "Show all
files" icon on the top.

4. Delete the .resx file for your user control and you should be able
to see your user control in the designer.

5. To recreate the new resx file, try to make some changes to your user
control in the design view(like move a control etc) which will force it
to recreate the new resx file.

Raj Behra

Mar 10 '06 #6

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

4 posts views Thread by Kuldeep | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.