Why are the controls still old fasioned?

[Steven Sartain]

I consider myself to be both a competant and experianced VB developer. I
have recently installed .NET and decided to write an application that I recently
developed in VB6 to familiarise myself with the language.

After opening .NET I have noticed that the controls collection does contain
a few extra components, but on the most part they are the same old rubish
that I wasn't happy with when VB6 was released. The .NET IDE uses to msoCommandbar
class for its toolbars, yet it expects us to use some second rate 90's toolbar
- why?

I must be missing something, or are MS again expecting me to write my own
toolbars, menus, grids etc.

Can someone please clarify that my conclusions are correct.

Thanks

[Jacob Grass]

> I consider myself to be both a competant and experianced VB developer. I
> have recently installed .NET and decided to write an application that I
recently
> developed in VB6 to familiarise myself with the language.

I did the same thing. . .

>
> After opening .NET I have noticed that the controls collection does
contain
> a few extra components, but on the most part they are the same old rubish
> that I wasn't happy with when VB6 was released. The .NET IDE uses to
msoCommandbar
> class for its toolbars, yet it expects us to use some second rate 90's
toolbar
> - why?

Well, they are under no obligation to provide to you what they themselves
use. Plus, who knows if there will be improved components in the product by
the time it ships. . .

>
> I must be missing something, or are MS again expecting me to write my own
> toolbars, menus, grids etc.
>

Well, with Visual Inheritance, this is mostly a whole lot easier. . .

Jacob

[Steven Sartain]

I agree with your comments, although it hasn't helped or answered my questions.
I don't expect MS to provide me with the latest technologies that they are
using. What I would like is toolbars that MS delivered in Office 97! Can
I make use of the msoCommandBar class as it obviously part of the .NET or
Win2000 distribution?

Thankfully things are easier, although this does mean recoding my VB6 code
to work efficiently under .NET - no mean task.