>>I think I'm going to start learning VB.NET instead of C#.NET because there seem to be more jobs (big priority right now) and I think easier going from Foxpro. Also, employers might think that Foxpro and VB are close enough to give me some credit for the Foxpro experience. Any thoughts?
>
>Jay;
>
>I began using .NET with VB, and it was much like VFP. I then redid the project in C#. C# threw errors that VB.NET did not find or report. That brought back memories of VB 6.0 projects working for months and then failing due to an error in coding. Once the error was thrown the application would not work again. You had to fix the problem and the fun part was finding it!
>
>My favorite programming language is C. Using C# was not difficult for me because of that. However, I think that there is a larger issue. Learning how to use the IDE, what to do and how to do it is very different than VB 6 or VFP.
>
>What tool and version will you use for .NET development?

I'm thinking VB.NET 2003 as that is the version I currently have.

>When I began using .NET I started off with simple projects. I would use the data objects and wizards. Then I hand coded the data objects which gave me much more functionality. Finally, I created Business Classes and Data Classes to handle things in a multi tier approach. I think that it is enjoyable to have gone this route as I learned a great deal.
>
>To be honest of all the books I have purchased about .NET, the series from Murach has been the best. It is a meat and potatoes approach with examples that work.

Is this the one? http://www.murach.com/books/adon/index.htm

>Probably the best approach to .NET development is to use a commercial application framework. Now if I could just convince my company!

Yeah, but as far as finding work for the next few years - let's just say 15 for the sake of retire- uh, argument - I wonder if learning a framework is the way to go?

>I have not checked for some time about which language is in greatest demand for .NET. I agree with you that if it is VB.NET then go for it!

As much as I can tell, it's VB.NET, but that I bet the salary is diluted as well.

Thanks, Tom; good information.