I sure hoped you feel that way Kevin because if not you would have wasted a lot of time writing that book and making that framework <g>

Would'nt it be frustrating if someone worked long and hard with .Net not really liking it but progressing to the point of becoming an MVP.

And then after getting that MVP that developer comes out and say "After losing too many hours studing .Net I came to the conclusion that .Net is just a load of crap."

I probably won't see that soon <vbg>.

I'd have to be really dumb to not see that .Net is the tsunami of development environments.

But the thing that gets to me is the hypocrisy caused by its popularity.

Practically overnight many said that .Net is so good and VFP is so bad. The same developers that said many times how VFP was used to build rock-solid apps.

The other thing is that there are only advantages on using .Net and disadvantages on using VFP.

So there's no market anymore for VFP? I mean 0?

>>I wish someone would start a seminar/website called "Why Convert?"!
>
>I know it can be very frustrating to be at the top of your game in a particular language/toolset and then have a brand new technology like .NET come along. When Rick Strahl and I first began to learn .NET we felt like we went from gurus to complete idiots in two seconds flat--that can be completely demoralizing. But I remember feeling very much the same way when Visual FoxPro was released. I had to ask myself whether it was worth it to stay in FoxPro 2.6 or make the leap to VFP knowing that I would have to rewrite applications to do so.
>
>It's a great question--has Microsoft introduced the .NET technologies simply because they want to make more money, or is there a technological advantage that makes .NET worth looking at? We all know Microsoft DOES want to make a lot of money <s>, but there ARE very real, tangible benefits found in .NET. Here are a few of them:
>
>

• I think one of the biggest advantages of .NET is the reward you get for your learning curve. Although the .NET curve may be steep at first, once you've "arrived" you can create Windows applications, Web applications, Web Services, and Smart Device (PocketPC/Windows CE) applications. In the next version of SQL Server you'll even be able to write stored procedures in C# or VB .NET. In contrast, with Visual Studio 6 you have to learn one language / toolset for Windows, another language / toolset for Web, and yet another language / toolset for smart devices.
  >
  >
• Strongly typed languages! Because Visual FoxPro is weakly typed, you must run your code to find most of your bugs. In contrast, C# and VB .NET are strongly typed languages, which means you specify the data type (integer, string, DateTime) of variables, method parameters, method return values, etc, which allows you to find most of your errors at compile time. If you've never worked with strongly typed laneguages I recommend checking out this feature. It's phenomenal.
  >
  >
• Advanced Object Orientation - It used to be that we Fox developers looked down on VB because it wasn't truly object-oriented. At this point, VB .NET (along with C#) has leap-frogged VFP's OOP capabilities with important advancements such as interface inheritance, the ability to create custom events, true abstract classes and methods, overloaded methods, enumerations, and so on.
  >
  >
• Targeting Multiple Platforms - Microsoft submitted C# to the ECMA standards committee and C# has been adopted as a universal language. This paved the way for the Mono Project (http://www.mono-project.com). You can write C# code today that can be compiled for either the Windows or the Linux platform

>I've literally taught hundreds of VFP developers .NET, and although the learning curve can be tough at first, I have yet to find someone who was sorry they arrived on the other side. Most VFP developers who are using .NET love it (well for the most part, love it and sometimes hate it as is the case with most MS products <s>).
>
>I know there's a lot of heat behind the VFP/.NET discussions, but I highly recommend VFP developers take a serious look at .NET when getting ready to rewrite or create brand new applications.
>
>Regards,