I would think the biggest question is why?

If you are taking a VFP app and making a web based interface, I would guess the point would be to enable any client type access to the application, (ie if you connect from Linux running Netscape or Windows running IE, it doest matter as it is a web interface)
In which case creating the web interface using WinForms where the client needs .NET installed would mean that only clients running NT, 2000, or XP could currently access the interface, in which case, why do it as a web interface at all?

Note that I havnt experimented with all this stuff, but if you need the framework for the WinForms to work, then it kinda defeats the purpose of a web interface IMHO.



>Well, just when I thought I was starting to really learn...
>
>I've been working on converting the UI layer of a a VFP application to ASP.NET. However, another developer started to introduce me to WinForms in VB.NET.
>
>Admittedly, I assumed that WinForms were for 'desktop' and 'thick client' apps. However, the developer I spoke to said that WinForms can be used on the client end and still utilize a Web Server, with the advantages that the UI can be even richer, you don't have to deal with VIEWSTATE stuff, developer productivity is greater, and that performance is better. Only 'downside' he mentioned was that the .NET framework would have to be installed on a user's machine.
>
>So here's my question...for a rich UI in a 'web-based' environment, what would be the benefits (and pitfalls) of using WinForms over ASP.NET??
>
>Thanks,
>Kevin