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
.