The web designer and the HTML view are collectively analogous to a Windows form. The code-behind is analogous to the code supporting a Windows form, although you can still write client-side script in ASP.NET web pages. You get the idea.
Web pages are becoming easier to implement, and we'll begin to see richer web applications because of ASP.NET. From the examples described in this article you might guess correctly that building web applications takes more effort than building Windows applications, but the margin of effort between the two is narrowing. Of course, if you want Windows forms richness with ease of deployment, consider thin client programming in .NET. (You'll need to know all about reflection and assemblies, and a book like Visual Basic .NET Unleashed can help you with that.)
In this article you learned how to describe a web page with a DataList control, filling out the templates to support rendering the page in browse and edit mode. You also learned how to write the code that supports the page programmatically. As you build web pages and explore .NET, remember that you're not limited to working with DataSets. Many kinds of objects can be bound to a web page and managed directly.