>I don't know, maybe it's just me, but how the heck many properties are there to set/change in a simple control like a TextBox? I don't think that having to set those in code is really a big deal and not being able to see it visually is equally not a big deal, simply because the "look" of a simple control is not gonna change all that much, is it? (keep in mind, I'm only talking about WinForm controls)
>
>~~Bonnie

I bet you 90%+ of VS.Net "programmers" are dropping controls right from the tool box onto their forms. Whether they are FxCL classes or third party classes. The VB background just doesn't support the mentality of sub-classing the FxCL controls prior to using them cause you couldn't do that in VB. Also, the VB.Net developers didn't put that feature into VS because VB didn't have it and they probably didn't think about it.

But, remember in VS it is the "forms" designer not the "class" designer.

Although I do agree... I don't much miss not being able to visually design these classes. At least you can't put your code based class on the toolbar and drop it onto your form... you can't seem to drop prg based classes on a form in vfp... can you?

BOb