>>VFP not being a .Net tool won't have native Web controls for WEB apps to be compiled as ASP+
>
>Voodoo web controls is to VFP as ASP.NET is to the CLR. The beauty of our community if third party products.
>>you leverage the new capabilites of ADO.Net
>
>What in particular?
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguidnf/html/cpconadonetarchitecture.asphttp://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguidnf/html/cpconcomparisonbetweenadoadonet.asp>In VFP? I never have problems with the VFP runtime after its installed.
Good for you. With .Net component registration is no longer an issue.
>>platform issues from PC to mobile phones
>
>Third party solutions here too, I believe there is someone working on WAP version of Voodoo too (its pretty easy to subclass).
>
>>and if Linux gains significant OS crowd, CLR is just ready for deployment and your apps will be ready for crossplatform, etc.
>
>This looks like the only big advantage to using the CLR from VFP.
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."
