Tnx for the replies.
One big reason for me to switch from the old VB6 to VB.NET was the fact
that all the code for a form was in 1 file and it was all code, which
gave us a lot more control over all the controls in a form compared to
the hidden and unreachable code behind VB6 forms. als great for
applying inheritance and so forth.
Then came VB.2005 and they started to give up the principle of having
everything in one file and moved to more hidden files again. There's a
an american saying : "If it ain't broken, don't fix it". If only they
could appreciate this a bit more at Microsoft.
BTW they did add a lot of good things too, but if only they could keep
their hands off of things that worked.
Robinson schreef:
"jandhondt" <ja*******@jadesoft.bewrote in message
news:11**********************@h48g2000cwc.googlegr oups.com...
In VS2005 with VB.NET when a form or usercontrol is inherited: it is
terribly annoying that the code view shows as Public Class statement
without the inherits statement.
You have to go to the myform.designer.vb code to show this inheritance.
I have to agree to with this. I have solved it to an extent as Patrice says
by having a folder structure that reflects inheritance in my solution.