>>>>>I'm confused as to why you think .NET is lacking...
>>>>>
>>>>>

>>>>>public class MyJunk: OldJunk
>>>>>{
>>>>>   public myJunk() : base()
>>>>>   {
>>>>>      this.SomeProperty = "nondefault value";  
>>>>>   }
>>>>>}
>>>>>

>>>>
>>>>So how exactly do you subclass and just set a property, without writing any method code, just clicking around the PEM window?
>>>>
>>>>I know you can do everything in code - stool, you can even write forms in prgs (I know a guy who does and he's doing great, his forms are tight and his exe shrank by 50%, gaining some speed too), but... which part of Visual evades understanding here?
>>>
>>>I guess I don't feel like I'm missing anything without the visual subclassing. I feel no desire to design my business objects using a designer. Whatever floats your boat.
>>
>>But you've got to admit that when you need to change parent classes VFP gives you a lot more to "look" at than the one line of code it takes in VS. <s>
>
>Ha. I guess I've gotten out of the habit of using a wizard or designer for everything.

I was thinking more of the dancing around with the class browser, trying to change parent classes and move classes around between class libraries. <s>

I love RAD tools but I agree, wizards and designers can make a whole lot of things harder (especially, when like the VFP view designer they have been fatally flawed from birth and never really fixed )

The namespace and inheritance thing, as well as being able to go grab whole chunks of one project and drop it into another project is actually kind of nice. I still freak out sometimes about not having the granularity of the VFP method code interface (which made me crazy when I originally encountered it <g>). I had trouble warming up to the idea that code was at the form level in many cases. It's a real different world from VFP in a lot of ways. I think the only thing I really have a problem with is the FUD that claims once you leave VFP there is no more data handling, oop, RAD etc. Different can be very cool <s>