Why not decouple the UI from the business and data layers and use them with
any UI you want (be it web or win32). You are trying to re-use the wrong
part... I think an n-tier design would get you where you want just in a
slightly diff way. Take a look at Model-View-Controller (not .NET
specific).
--
Derek Davis
dd******@gmail.com
"David" <Co*********@AdsorptionProcessModeling.com> wrote in message
news:siHnf.17618$Mi5.13200@dukeread07...
One advantage of ActiveX is that something that is developed for (and
tested with) a desktop app can be used on the web. Can .NET do this? Is
there a way to develop a user interface first for a Windows app and then
use that UI on the Web? It seems to me that the classes used to develop a
Forms-based Windows app are very different from those used to develop ASP.