>Then there is the problem of new .NET technologies. If I'd adopted .NET 1.0 from the start, I'd probably find myself rewriting data handling parts 2 times now, and with the next version for a third time, just because of the rate of introducing new data handling technologies.
If you have a separate data layer then you will only adjust that portion if you want to because I don't think succeeding versions will totally replace the entire thing. There will always be backward compatibility I think. LINQ maybe just an option to handle data although I don't have any idea as to how it works now. What I really want with .NET is that you can create an application with a presentation layer that is awesome. You have so many options which is not so in VFP. We are stucked to where it is now (at least for Windows Forms).
>I'm probably going to be a late adopter of .NET (Personally I don't see much value in learning PHP, Java, MySQL), because I Just want to use the LINQ stuff when its properly implemented. It will be a steep learning curve and a very difficult time since timewise I can't afford being unproductive for long. If it was not for a financial reason, it would be because clients would not allow for that.
JESS S. BANAGA
Project Leader - SDD division
...shifting from VFP to C#.Net
CHARISMA simply means: "Be more concerned about making others feel good about themselves than you are in making them feel good about you."