I use FlowLayout out of personal preference - I like to finely control the HTML layout and I've been sleeping,breathing,eating HTML for years <g>.

GridLayout by default outputs absolute positioning so yes, in this mode (with the default settings) this would not render properly on downlevel browsers. HOWEVER, you can change the browser target by setting the TargetSchema on the project properties/designer defaults section and selecting IE 3.02 & Navigator 3.0. Now when you design your web form in GridLayout, the designer will convert your positions to TABLE format automatically using TD widths and TABLEs within TABLEs - basically what Dreamweaver/Fireworks can do if you are familiar with that.

GridLayout tends to drive HTML-savy people crazy, so I'd choose FlowLayout if you're one of us <g>. Otherwise, for people that like to just drag-drop stuff on the designer, just be aware of your target browser.

HTH,
-B

>>I use FlowLayout mainly due to the poor results with GridLayout and its support (or lack of) for browsers other than IE. If your only concerned with supporting IE browsers then GridLayout would be ok.
>>
>>As far as the HTML formating yeah its a PITA. I hard code 95% of my pages so it's really not an issue for me. You can view the page in design and switch back to code without it auto-formating as long as you don't change anything while in design mode (I know, a lot of help that was).
>>
>>When I do need to reformat I load the page into Macromedia's Dreamweaver MX and let it reformat the code. Dreamweaver's reformat (though not perfect) does a pretty good job with the HTML.
>
>Michael;
>
>At work we develop Intranet applications only, and our corporate standard is ASP with I.E. browsers. I have not tried ASP.NET with different browsers – yet!
>
>The folks at Microsoft that I have talked to as well as the training I have received indicates “all browsers are supported by ASP.NET”! Somehow, perhaps because of my name (Thomas), I doubt that bit of “reality”. :) Thank you for your comments.
>
>Tom