><< We need a book written the other way around (VFP for the VB developer). >>
>
>Yeah, try finding a publisher for that one. Actually, what would be really great is a book that spelled out the differences between the two products, focused on their strengths and weaknesses, told you when to use each one when and how to get them to work together. Actually, a book (or more likely a series of books) along these lines for all of VS would be awesome.

Hear, hear! If Microsoft Publishing or some other publishing house came out with the Visual Studio Programmers Guide (volumes 1 through 9, 1 book for each product plus a book that helps to explain what tools are best for what tasks), it would weigh around 30 pounds, take up 2 feet on your bookshelf, cost around $300, and would probably be the number one resource for new developers, or for developers in VB, VFP, VC, VJ, and HTML to leverage their existing skills across the spectrum.

Think about it. Bring 'em in, sit 'em down, train 'em right, occasionally wake 'em up, and set 'em loose!

I can dream, can't I?

>
>BTW, the reason I didn't mention any specifics is I kind of wonder if this book will ever really come out.

Unfortunately, I agree with this conclusion, for the reasons stated above (we're talking one SERIOUSLY time- and resource-intensive learning curve!)

I'm curious: is there really anyone out there that is utilizing the full power of Visual Studio? They need to be very well-versed in all of the technologies, an expert in most, and have the experience to know when one language will do the job better than another.
I would love it if Microsoft came out with a new certification: Visual Studio Certified. It would only take, what, 10 or 12 exams?

>
>Besides by definition VFP for the VB Developer would be over all of the VB developer's heads. :-)

I don't think so. They just need a VFP person to explain the big words, like "inheritance"...

Bill