Hi Bill,

The trauma is actually a polyfacetic one: It involves learning a new language (or two), new IDE, a framework, a design approach, and then a couple of technologies that are really just additional framework components packaged in fancy names (WCF, WPF, etc?) that will render existing techniques and technologies obsolete before you even have a chance to learn them.

At this stage, unless you have the time and resources to attend a formal class on the subject (and considering its vastness, it'll likely be a looong class), concentrate on your immediate needs and how to solve them with the new set of tools.

Yeah, you will end up using a pipe wrench for something you could've done with a set of fine plyers, if you catch my drift, but that's what learning is about and if you've been in this business long enough, you have learned to live with the fact that the first few apps you write using a new language/tool/framework/you name it is going to be something you would rather die than show it to a fellow developer :-)

Have fun!

Alex

>
>This thread is a good example of what someone trying to learn .NET faces.
>There are many more ways to accomplish even the most basic tasks in .NET than there were in VFP,
>and there are ardent evangelizers for all of them on the UT and all over the web.
>
>When I go to conferences, code camps etc, invariably I hear people arguing over which latest and greatest
>gizmo is best down to the nth nanosecond.
>
>These dialogues, however well informed, confuse the life out of someone
>struggling with things like when to use curly braces with an if statement.
>
>Fortunately, I ran into a C# developer at a conference who had gone thru the same maze
>and he advised me to narrow my focus and forget the alternatives till I had one method down pat.
>
>I did that by getting a good book and keeping my head in the sand till I had the basics down
>and that has been working for me.
>
>
>
>
>
>
>