If you use VFP with .Net you're diminishing that platform's performance and scalability significantly. Many of the benefits you gain by using .Net in the first place just go out of the window. Second, using VFP COM objects with .Net is painful if you do anything non-trivial because there's no direct connection to those objects. You have to use Reflection to get to lower level objects/properties etc. or VB and Option Strict off which also is not what I would call an option. Can you do it? Sure. Is it easy to do it? No, especially not in the face of native code.
I think COM interop with .Net is a nice stop gap choice, but not a permanent solution. If you want to go that route than classic ASP is actually a better choice IMHO.
No comments:
Post a Comment