>>>
>>>I've gotten to where I really enjoy working in the VS2008 IDE. There are some advantages over VFP. There are two disadvantages though that are pet peeves of mine.
>>>
>>>1) Writing a constructor for every case of parameters that may be passed - no more multiple conditionally passed parameters in an init
>>>2) Putting a breakpoint when a value changes not in a specific location
>>
>>For (1), C# 4.0 may offer some relief (Named and Optional Arguments)
>

>I remember being disenchanted as soon as I found out I couldn't visually subclass, but that didn't last long. I guess that is something you get used to. I'm not surprised that it is a 'limitation' often complained about by VFPers moving to or trying .net though :o) It is a limitation when compared to VFP. It's just not one that causes me major stress :o) #2 above has though.
>
>I've seen the named and optional arguments in c# 4.0, and it may offer some relief. However, there are rules that must be taken into consideration:
>
>http://codebetter.com/blogs/matthew.podwysocki/archive/2008/10/28/named-and-optional-arguments-in-c-4-0.aspx
>
>Also, for those of us who have worked on major rewrites already, it's a little late in the game. Still welcome though. :o)


>I remember being disenchanted as soon as I found out I couldn't visually subclass, but that didn't last long.
Like you say - it's a habit - it's not because it's different that it is a bad thing


>I've seen the named and optional arguments in c# 4.0, and it may offer some relief. However, there are rules that must be taken into consideration:
I did read up a bit about them so I did not answer "n'importe quoi" http://code.msdn.microsoft.com/Project/Download/FileDownload.aspx?ProjectName=csharpfuture&DownloadId=3550

That's why I have written some relief

As to (2) I cannot really comment on that - I'm still fiddling and writing a few classes - you're way ahead of me