Hi, Fernando.

>>the book is not about migrating from onw platform to the other, but about how to do the same things in both.
>
>I dont want to sound obnoxious, but unfortunatelly I will. What's the point in "how to do the same things in both" if not to get used to the new tool and, maybe, migrate to it?.

Oh, I knew this will happen all the time while working on the book. And even more when I saw the final title.

But take a look at the book and you'll find that if this is a book about migrating to .NET, then there is a strange lot of VFP training.

>I would even imply there is a hidden excuse in your words for this happenning ("...the original one was Visual FoxPro and VB.NET Side by Side").
>
>Sorry, I'm just expressing what I felt when I read your message, nothing more.

Don't worry, I understand it. It's not an excuse, but as I said, I knew that this perception would arise. Take a look at the book. You'll find is not like that.

About the point in "how to do the same things in both", at least from my perspective, is to keep yourself proficient in both languages. I'm not a Java expert, but I did learn a LOT about software development by learning Java, and the same happened to me when learning .NET.

Now I regularly develop in both VFP and .NET (not VB.NET, but this was Les' choice, not mine). Both have their specific strengts, and I enjoy and hate many things from each one. Well, I actually hate just a few things in VFP and a lot in VS 2003, but it will improve over time.

I really don't think learning a new tool means dropping another. It can happen at some point, or not, but this is a personal decision. I think you don't really are choosing your tool when you know just one.

Best regards,