Or vice versa, host a .NET UserControl in the HTML... (I mention only for the sake of completeness -- and because I just accidentally replied to the cross-post on dotnet-winforms... please don't do that, Vince.)
http://msdn.microsoft.com/msdnmag/issues/02/01/UserCtrl/default.aspx Just how great a "web experience" this makes for is... debatable. As always, a lot depends on your application. -S -----Original Message----- From: Curt Hagenlocher [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 20, 2004 09:04 Subject: Re: Using a common form for web and windows-based application. From: "Seref Arikan" <[EMAIL PROTECTED]> > I'm certainly aware of the differences between local apps and HTML. The > ONLY capability i want to use is to display a form for data entry. > That's all. No data validation on client side, no fancy user interfaces, > they're as simple as they can be (call it exteremely idiotic if you > want). My business logic is responsible for any kind of processing on > data. Why not host an HTML control in the local app then? Even without a web server, you could embed any needed HTML in the app itself. -- Curt Hagenlocher [EMAIL PROTECTED] =================================== This list is hosted by DevelopMentorR http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
