Boy, this is something that MS needs to fix fast. Every now and then the
designer just goes plain stupid for no rhyme or reason and gives off the
gross error message "One or more errors encountered while loading the
designer."

Even with this error, the code compiles and runs fine. But obviously you
cannot edit the form, and the only resolution I have found is to close the
application and re-open it.

It would be good to hear others experience, but just as important, it would
be great to hear from someone at Microsoft who is aware of the problem and
can enlighten us when there will be a resolution (can anyone say service
pack?)

Earl wrote:
I'm not aware of any issue which does this. Can you send me a project
which repros this? Send it to sriramk [at] microsoft [dot] com


--
Sriram Krishnan
Visual Studio for Devices
http://blogs.msdn.com/sriram

Earl wrote:
workaround was to rebuild the form.

I recently read a blog/forum post somewhere that suggested the problme s
caused by adding user/business code to auto-generated code areas that
should be left alone. As a newcomer to C#/Visual Studio I have found
this easy to do so I am now concentrating on adding business code to my
own classes and using the Partial Class and other new features (see below).

I note that this problem is also easier to avoid in code generated in
VS2005 because new projects created in VS2005 is split into frmClass,
partial FrmClass, frmClass.Designer and Program.cs. This does not happen
if the project was created in VS2003 and imprted into VS2005.


Regards


Will Chapman

Earl wrote:
workaround was to rebuild the form.

I recently read a blog/forum post somewhere that suggested the problme s
caused by adding user/business code to auto-generated code areas that
should be left alone. As a newcomer to C#/Visual Studio I have found
this easy to do so I am now concentrating on adding business code to my
own classes and using the Partial Class and other new features (see below).

I note that this problem is also easier to avoid in code generated in
VS2005 because new projects created in VS2005 is split into frmClass,
partial FrmClass, frmClass.Designer and Program.cs. This does not happen
if the project was created in VS2003 and imprted into VS2005.


Regards


Will Chapman