Inherited forms and 2003

  • Thread starter Thread starter Jeff Levinson [mcsd]
  • Start date Start date
J

Jeff Levinson [mcsd]

I guess I would have to know what you mean by "not being
able to edit the forms". Does this mean you get an error
in the designer when you try to display an inherited form?
Does this mean the controls are visible, but you can't
move them around? What exactly does it mean?

There are a variety of methods for editing visuallly
inherited forms and I've never had a problem with it in
any version of VS.

Jeff Levinson
Author of "Building Client/Server Applications with
VB.NET: An Example Driven Approach"
 
Jeff Levinson said:
I guess I would have to know what you mean by "not being
able to edit the forms". Does this mean you get an error
in the designer when you try to display an inherited form?
Does this mean the controls are visible, but you can't
move them around? What exactly does it mean?

There are a variety of methods for editing visuallly
inherited forms and I've never had a problem with it in
any version of VS.

Jeff Levinson
Author of "Building Client/Server Applications with
VB.NET: An Example Driven Approach"
Click to expand...


Do you have a link to the article?

I have noticed that sometimes inherited forms forget that they are forms -
in the project file the SubType is "Code" instead of "Form", as it should
be:

<File
RelPath = "Form1.cs"
SubType = "Form"
BuildAction = "Compile"
/>

I've also found that a quick way to fix this in the IDE is to cut and paste
the inherited class. For example:

public class ApplicationView : BaseFormView

cut and paste "BaseFormView" right back. The Solution Explorer changes the
icon for the form back to a form.

Good luck,
Marc
 
Jeff - thanks for getting back to me. Back from holiday now.

My application builds and runs absolutely fine. I just cannot edit these
inherited forms anymore in the visual designer. I get an error that
something is wrong with the form. There is nothing wrong with the form.
This has just started happening since we migrated to 2003 and lots of
others have the same problem. It is a known bug. This doesn't help us
continue development of our application however.

These inherited forms override a couple of base methods. I thought that
may have been the problem - but temporarily removing this doesn't make
any difference - then I found messages from others with the same
problem, then the Knowledge based admission from Microsoft that there is
a problem.

I need to be able to properly edit and develop more inherited forms.
This app is written in VB.

The suggested methods of solving the problem don't help me much I am
afraid.

Temporarily removing the inheritance for the purpose of doing visual
edits sort of works, but when the inheritance is replaced, the size of
the form and location of the controls on it go a little strange. So it
gets very frustrating especially when our timescales are tight.

Louise.
 
Back
Top