By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,827 Members | 2,220 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,827 IT Pros & Developers. It's quick & easy.

Inherited forms and 2003

P: n/a
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"
-----Original Message-----
Hello,

I have fallen foul of not being able to edit inherited
forms via the visual designer. I found an article on
knowledge base about this. Nice one Microsoft - it is a
bug, but it is a pretty serious one! I need to use 2003
for the Oracle classes. I have many many forms, all
inherited. Now I can't edit them easily. Knocking off the
inheritance for the purposes of editing/creation results
in odd sizing problems - particularly if they contain
Active X controls.

The article suggests registering my assembly in the GAC,
but to do that it has to be strongly typed... but this
means all the assemblies my assembly depends on have to bestrongly typed... Unfortunately they are mostly interops.
These are not strongly typed. I don't know how to type
these. (Getting late here I have to go, no time to find
out right now, and I am out of the office for a few days.)

I tried copying a copy of my assembly (actually an exe) tothe location of Winres.exe. This didn't work.

Anyone any other ideas how I can get round this one??
Editing forms with Active X controls on is very flaky whenI remove my inheritance. It messes up the layout.

This is causing us serious problems! Any idea when this isgoing to be fixed? We have some more forms to create, theyHAVE to be inherited!

If anyone can shed light or give me any ideas I would be
very grateful.

Thanks,
Louise
.

Jul 19 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
"Jeff Levinson [mcsd]" <je***********@comcast.net> wrote in message
news:03****************************@phx.gbl...
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"
-----Original Message-----
Hello,

I have fallen foul of not being able to edit inherited
forms via the visual designer. I found an article on
knowledge base about this. Nice one Microsoft - it is a
bug, but it is a pretty serious one!

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
Jul 19 '05 #2

P: n/a
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.
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Jul 19 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.