>>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?
>
>WYSIWYG design is not all that great in VS.Net. Really the the visual aspect of that is a good HTML editor. If you use .Net and you want to do visual editing you're sure not going to use the VS editor to do it. I use FrontPage most of the time after I've dropped my ASP.net server controls on the form.
>
>This process is not that much different that what you do with classic ASP or Web Connection in VFP.
>
>But, where ASP.Net really shines is in its object model and how the Web backend works. It is very slick and completely extensible and you have full control over almost every aspect of creation of output. It's complex to understand the whole architecture but of course one doesn't need to know all of it to be productive (although it will help significantly when you hit a wall with the drag and drop type programming).

Thank you for the information Rick. Please give me a for instance about where the .NET object model shines.

>I really like ASP.Net and its flexibility and I've built a lot of stuff that I've taken for granted with Web Connection and plugged it into my Web framework.
>
>But the tools (VS.Net) are crude (both for Web Forms and WinForms). Luckily that will be addressed in the next version of VS.Net but we'll have to wait for that yet...