Yeah I've done a WinForms version of my web-based application, and
working with Windows Forms is so much nicer than with web apps...
Partially because of the "neatness" factor of managing synchronization,
updating, and offline manipulation of data coming from a series of
remote web services, and using threads to do it. I'm a newbie to a lot
of parts of the .NET framework, so hitting new areas is great fun!
You know what would be REALLY cool, though? If the future version with
the Windows Forms or Avalon or whatever it's called, with the UI mark-up
called XAML (right?), could be portable between windows and web apps.
I mean, a treeview is a treeview right? If I have a Windows Forms app
with a TreeView and a ListView in it, and the output of the form is
XAML, why couldn't IIS or the framework itself see that and render
either a Windows Form or a Web Form, depending upon the context of the
client? THAT would be extremely cool. :)
By the way, about NTD in the browser, have you tried using the OBJECT
tag and referencing the DLL + class name for one of your Windows Forms
in HTML? I hear it works the way old-style OCX would..
-----
Aaron Lewis
GuildPortal.com Development
www.guildportal.com
Bruce W.1 wrote:
That sounds like really good advice and I must try it sometime. But I'm
sorry to say that I have shifted gears and turned it in to a No-Touch
Deployment (NTD) winforms program, and it works great. ASP.NET is not
so great for real-time information.
Of course it only runs on .NET. That's okay for now.
I wish Microsoft would let NTD programs run in an IE browser window.
--