Hi, David...

First, thanks for the previous information you sent me on remoting. It was very helpful [along wtih some code I got on c-sharpcorner.com].

Second, I checked out the URL, and I see what's going on. That leads to some other questions...

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]?

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.

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?

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?

Reason for asking all this is that we've already developed a Winform app with an MDI parent/MDI child approach. It's fairly complex, and while it seems from this web site that it might be possible to get all the Winform controls that we're using into an ASP.NET page...there's still the issue of forms/windows management, etc....and I'm not sure we have the development time to switch gears that quickly [and I'm not sure one way or the other if it's worth it...it sounds like the only advantage is one of redistribution of the front-end]. Again, we had a consultant at the 11th hour describe this approach.

Thanks,
Kevin