Having winform controls on a IE page seems a very slippery slope into a morass of code. When I saw it presented, the presenter (Jeff Prosise) explained that it took a lot of code to make it work correctly, although its cool to see that it can actually be done. Plus, you need the .NET runtime on the client anyway, so a winform client sounds like it would usually be a better solution. Besides, if your consultant had to refer you to a white paper it sounds like he didn't have any first hand experience either.

>1) In general, would a developer have the same 'control' over the appearance that a developer has when designing pure Winforms? In other words, does ASP.NET allow me to place a Winform control anywhere [i.e. location 456, 134]?

Yes.

>
>2) To the best of your awareness, can this be done for ALL WinForm controls? [tab pages, datagrids, etc.]. I realize I can do some experimenting to find out on my own [and probably will], but figured I'd ask if you knew of any known issues.

As far as I know, Yes.

>
>3) If you have a complex Winform with many controls, do all the controls get 'downloaded' into the workstation's memory everytime? Let's say a person loads a page with 25 controls...and then closes down Explorer, and re-loads the page later in the day...even if the controls haven't changed at the server, would they still get downloaded again?
>

As far as I know, they would be cached on the client like any other kind of active-x control.

>And related...if the contents of controls get changed [result set that's bound to a control, for instance]....would the refreshing take place on the server and then redisplayed, or does the refreshing take place on the client end?
>

As far as I know, refreshing takes place on the client there is no server side postback until you click a submit button.