The same paradigm applies to a Winform app if you're using Web Services to access your biz/dataaccess layer, since Web Services are also stateless.

~~Bonnie


>>>That demonstrates a very important point. ASP.NET is used in a variety of architectures such as Web and Winform development. Methods used to access data in a Winform application may not be appropriate for use in a Web application.
>>
>>Unfortunately, too many examples are floating around the Internet that indicate that it's good practice to have DataAccess in your UI layer. Whether your UI is a WebForm *or* a WinForm, it doesn't matter ... your DataAccess should be a totally separate layer. The UI should *never* have DataAccess code in it, nor should it know *anything* about where it's data comes from.
>>
>>~~Bonnie
>
>
>Agreed, about no data access or biz logic in the UI. I can't say I've looked at many examples that promote this practice though. One major difference in developing Web apps versus Winforms is that your data layer and business layer must be lightweight for the stateless web environment. Methods that would be preferable in a Winform application would not provide the speed and scalability required for a web app.