David Mohundro - "The designer loader did not provide a root component but has not indicated why."

Friday, April 14, 2006

"The designer loader did not provide a root component but has not indicated why."

Ever seen this error in Visual Studio 2005?

I've seen it all too often and it is really annoying.

However, I did find a possible fix today. I was working in a project that had multiple assembly references. One of the references was using a 1.1 assembly, so it came along for the ride. By simply removing that reference, I was able to view my form without any problems. If I tried to add the reference back, I would get the designer error again. I reworked the assembly being referenced to not use any 1.1 components and... lo and behold... the designer errors stopped.

Is this just a really random bug or is this a subtle way to push people to migrate to .NET 2.0?

.NET | Programming | Visual Studio

posted on Friday, April 14, 2006 2:09:51 PM (Central Standard Time, UTC-06:00)

Comments [3]
Related posts:
Programmatically adding EventSetters in WPF
Visual Studio 2010 is big… at least the CTP is…
How I Got Started in Programming
Best comment of the day
Have you guys ever looked at Microsoft Virtual Labs?
Reflection by example with Powershell

Saturday, April 15, 2006 11:17:34 AM (Central Standard Time, UTC-06:00)

Hi David:

I get a lot of this random errors in VS2005, at my work we port our little ERP system from VS2003 to VS2005 and a lot of errors arise.

We use a lot of Inherited forms, and with these, the VS become a bit crazy, some TypeLoadException thorws.

The official solution now is:

1- Close all the forms
2- Clean the Solutions
3- Close VS
4- Re-Open
5- Rebuild before open any form
6- now work with your form, but not rebuild with it open...

This is really annoying, and we migrate back until the home fix (that MS said that have) become public.

Cheers

Marcos

Saturday, April 15, 2006 12:35:40 PM (Central Standard Time, UTC-06:00)

Yes, that's the same situation we're having at work -- visual inheritance with forms. My department is one of the first to begin the migration to VS2005 but we're still using common controls that were built in VS2003. It really seems that as soon as the inherited forms' dependencies on .NET 1.1 components are gone, the designer bugs disappear.

I'm really looking forward to the service pack. I'm hoping it fixes a lot of these annoyances.

David

Saturday, April 15, 2006 5:33:05 PM (Central Standard Time, UTC-06:00)

I´m waiting it too...

I convinced my boss to migrate to VS2005 and he not happy when this little bug appear and the productivity of the team go down :)

Cheers keep working in this excellent Blog.

Marcos

Comments are closed.