Hi Giorgio,
Based on my understanding, you have several WinFoms application projects
which contain some inherited forms. You could open these projects and all
inherited forms without any problem. However, after you compile your
solution, and then open any form in the designer, an exception occurs. If
I'm off base, please feel free to let me know.
To make things clear, I'd like to ask you several questions:
1. You have mentioned 'Infragistics 2006 suite'. Is it a 3rd party
component?
2. > forms are inherit from base templates...
What're the 'base templates'? Are they related to the 'Infragistics 2006
suite'?
3. Are all forms that have the problem inherited from base templates?
In fact, if a form is inherited from a base form, when we open it in the
designer, an instance of the base form is created first and then the
InitializeComponent method of the currently opened form is executed. If we
couldn't open this from in the designer, we may narrow down the problem by
the following steps:
1. Change the base form of the form to be opened to
System.Windows.Forms.Form.
2.Build the project and re-open this form in the designer to see if it
could be opened properly. If no, the problem is at least related to the
code in the InitializeComponent method of the currently opened form;
otherwise, the problem is related to code in the base form.
3. If the problem is at least related to the code in the
InitializeComponent method, you may comment out all code in the
InitializeComponent method and re-open the form to see if it could be
opened correctly. If yes, you may uncomment some of the code in the
InitializeComponent method and re-open the form to see if it could be
opened. Repeat doing this until the form could not be opened correctly and
thus you find the exact code which cause the problem. Correct these code to
ensure the form could be opened properly.
4. Restore the form's previous base form.
5. Comment out all the code in both the base form's constructor and Load
event handler if any. Build the project and re-open the derived form in the
designer to see if it could be opened. If yes, uncomment some of the code
in the base form's constructor or Load event handler, and build the project
again. Re-open the derived form to see if it could be opened. Repeat this
until the derived form couldn't be opened. Then you find the exact code
that cause the problem. You may fix the problem by correcting these code.
You may try my suggestion if it's appropriate to your practice and let me
know the result.
If you have anything unclear, please feel free to let me know.
Sincerely,
Linda Liu
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx. ==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.