For us, it was things like making a grid editable, allowing data entry to use the 'Enter' key instead of the 'Tab' key.

The fact that objects worked differently WinForm vs Web

things like that

>So far the only thing which seemed noticeably more convoluted in .net than in vfp was when I created a custom base textbox. I put it on a winform and then I modified the properties and added some code to events. I wanted to take thed control from the form and make a separate new base textbox visually and couldn't.
>
>
>>An often heard exchange around the office while learning .Net
>>
>>"Can someone explain to me how this is so much better?"
>>"Well....it's all drag and drop!" Generally said with a smirk
>>"Yeah, 'til it's not - and most of what I want to do is not"
>>
>>4 days spent trying to figure out how to do something that's very simple in VFP
>>"Oh...THAT'S what you have to do?"
>>"uh-huh"
>>"Can someone PLEASE explain to me how this is so damn much better?"
>>.
>>.
>>.
>>Rinse - Repeat
>>
>>
>>>Back to your hesitancy on using an MSFT tool: I'm not sure any other tool would have more support, more users, more information available, or more longterm investment. If there is anything that is guaranteed these days, it is change. But don't worry, I don't think it's that far off to a day when programmers will be obsolete and users and business execs will be designing their own interface and databases with point and click by answering a few simple questions and dragging and dropping their controls on a web form.
>>>
>>>Maybe we should all just become moose hunters :o)
>>>
>>>(Just wanted to add one really big (HUGE) pet peeve of mine in VS2008. You can't set a breakpoint on a value such as a form prop and stop processing in the debugger whenever the value changes from any where in the solution like you can in VFP. That drives me nuts! You can set conditional breaks at a specific point, but that is not the same - not at all)