One other thing - go to MSDN and look for a set of articles titled "Death of the Browser" It's all about using WinForms via a server deployment.

Oh, and please say hi to the folks at Synectics... <g>

yag

>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