>THe biggest farce here I think is the fact that they apparently did this for UI reasons. If there's one thing that is weak in .Net it's the UI (not that VFP's UI is that strong and less buggy).
>
>There are possibly good reasons to use .Net but a migration 'just because' is not really a good reason. It looks to me this case study points exactly at that though...

Rick,

The only thing that is not straight forward with VFP is creating web apps in a WYSIWIG way, and perhaps there is simply no way to do that straight-forwardly with any tool (BTW I do have WebConnection).

So Rick, in you opinion, is .NET the best option for WISIWIG development for access through a browser? What are the alternatives, with pros and cons? I would like an integrated environment where you would draw the picture, add the behavior, and mostly you are done. What is best for that?

Thank you very much,

Alex