Help - I'm in Windows Forms Designer Hell

[Guest]

I am using VS2005 Team System Edition.
Third party tools: Infragistics, Developer XPress and some SharpLibrary

I converted my working App from VS2003 to VS2005. The App now compiles and
runs pretty well. I have one problem, however.

Whenever I open a UserControl or a Form in the Designer, I am greeted with a
full screen error message with a title in red. Most of the time the info in
the message is singularly unhelpful. Strange thing is that sometimes I can
open a UserControl fine, only to get the error messaqge 15 minutes later
without any reason that I can decipher.

Right now my productivity is zero as I find myself running around trying to
put out these fires - and I don't even have a clue as to why they are
happening. Remember - there is no problem running the App or opening the
same forms at runtime. I have gone over the references over and over again -
removing and re-attaching them. Is there some setting in Options that I am
missing - like HaveMercy = False!!

Thanks for your help
Jav

 

[Jim Wooley]

I am using VS2005 Team System Edition.

Third party tools: Infragistics, Developer XPress and some
SharpLibrary
I converted my working App from VS2003 to VS2005. The App now
compiles and runs pretty well. I have one problem, however.

Whenever I open a UserControl or a Form in the Designer, I am greeted
with a full screen error message with a title in red. Most of the
time the info in the message is singularly unhelpful. Strange thing
is that sometimes I can open a UserControl fine, only to get the error
messaqge 15 minutes later without any reason that I can decipher.

Right now my productivity is zero as I find myself running around
trying to put out these fires - and I don't even have a clue as to why
they are happening. Remember - there is no problem running the App or
opening the same forms at runtime. I have gone over the references
over and over again - removing and re-attaching them. Is there some
setting in Options that I am missing - like HaveMercy = False!!

Thanks for your help
Jav

Try moving the user control into a separate project. Also, if you are using
the new object binding, it may be that you re-built your object store after
the last build of the user control. The winform object binding hard-codes
the version number for the objects. If you rebuild the business layer, the
version number is not updated until you close and re-open VS. (royal pain
at times).

Jim Wooley
http://devauthority.com/blogs/jwooley/default.aspx

 

[Guest]

Thanks Jim. That's valuable info. I will work with those suggestions.
Jav

 

[Guest]

Jim, come to think of it, it makes a lot of sense. I do notice that my
symptoms get a lot better if I close VS and re-open it. Also one time, the
big old error message kept saying that it couldn't find one of my assemblies
with a certain Version Number. I kept wondering how the heck it can find the
assembly during compiling and running, and where is that version number
coming from. Ultimately, I just deleted all the bin and obj folders and
re-built the solution and the error message went away. This hard-coding of
version numbers explains a lot. I wonder if the UserControls' assemblies'
version numbers is also hard-codes in other Container controls and Forms
where they are used.

Jav