I would like to see the problem solved too :)
In fact it is this that I think really make visual inheritance completely
unusable to any professional degree.
If I can put #if statements into my code to work around this the designer
sure as heck can 'work some magic' behind the scenes for me. At least give
me a new compiler directive so I can use both debug and release builds in
the designer.
If I design my base controls as MustInherit my customers cannot even use
them in the designer.
What a crock!
Hmmm I wonder if there will be someone that I can push feedback on at the
release event this Thursday. I know there will be SOMEONE there but will it
be someone that will understand.
"Jay B. Harlow [MVP - Outlook]" <Jay_Harlow_MVP@tsbradley.net> wrote in
message news:OGllAXI5FHA.2560@TK2MSFTNGP12.phx.gbl...[color=blue]
> Ray,
> | Is VS.NET 2005 handling the visual inheritance problems centered around
> | controls and forms that are decorated with MustInherit any better than
> 2003
> | did?
> No.
>
> Which IMHO to a point makes sense; as an instance of the base form is to
> be
> created to display the derived form, allowing you to set base from
> properties, plus allowing the base form to display itself as *it* wants.
> The
> only solution I can think of would be for the form designer to dynamically
> generic a concrete proxy class that "fills" in the mustoverride members,
> however how would the proxy know what to put in the dynamically created
> classes?
>
> FWIW: I would like to see this problem solved!
>
>
> In fact in some ways its worse! :-(
>
> Adding a MustOverride method to base form, double clicking on the "Class
> 'DerivedForm' must either be declared 'MustInhert' or override the
> following..." error message opens up the DerivedForm.Designer.vb file
> instead of the DerivedForm.vb file.
>
> --
> Hope this helps
> Jay [MVP - Outlook]
> .NET Application Architect, Enthusiast, & Evangelist
> T.S. Bradley -
http://www.tsbradley.net
>
>
> "Ray Cassick (Home)" <rcassickNOSPAM@enterprocity.com> wrote in message
> news:euh4g9B5FHA.3188@TK2MSFTNGP15.phx.gbl...
> | Since I got such good feedback from the Xml comments question I will ask
> | this of the group as well.
> |
> | Is VS.NET 2005 handling the visual inheritance problems centered around
> | controls and forms that are decorated with MustInherit any better than
> 2003
> | did?
> |
> | I am getting really tired of having to do the good old '#If DEBUG Then'
> | workaround just to get by this.
> |
> | Thanks.
> |
> | --
> | Raymond R Cassick
> | CEO / CSA
> | Enterprocity Inc.
> |
www.enterprocity.com
> | 3380 Sheridan Drive, #143
> | Amherst, NY 14227
> | V: 716-316-5973
> | Blog:
http://spaces.msn.com/members/rcassick/
> |
> |
>
>[/color]
