Susan Warren's Blog

Sub Title

Death of the browser? Again??

Just kidding :)  The browser is not dead by a long shot, for many many “reach” applications.  And yet...

First, a nod to Billie Hollis and his prophetic October 2001 article. Way back then, he nailed the big issue: many of the Web apps we build would be better for users as Windows clients.  But we make 'em Web applications because it's so much cheaper to deploy.

Now that I've abdicated my position as the “queen of ASP.NET” (as Tim Huckaby used to call me), I've started to give Windows client applications a fresh look. It took a couple years for me (and the platform) to catch up to the Smart Client vision, but now it's official -- I have sipped the coolaid (sweetened with future prospects of Avalon, ClickOnce, and managed Office development), and it tastes good!

Ever since Outlook 2003 landed on my desktop I've been grooving on smart clients... apps that work on the airplane just as well as in they do in the office, with great usability and zippy performance.  Ever since OWA 2003 landed in life I've been thinking: too bad it's still so hard to develop a great web application like that.

My team got the chance to do the deep dive into smart clients recently by authoring the content for the Smart Client track at the upcoming DevDays, as well as a new smart client reference application: IssueVision.  I learned a ton about just about every aspect of authoring smart client applications -- especially some very cool architecture and data patterns, and some great security/deployment tips.  One of the hangups I'd had with smart clients is that there seem to be at least 3 different choices for each basic design/ security/ deployment decision you face.  Well, for IssueVision, we drilled into just about every choice, and now I know which ones really work, and when.  :D

IssueVision is about as Outlook-2003-like as we could make it, and “just works” if the network is connected or not.  The scenario is pretty lightweight (online/offline issue tracking) but the application is chock full of those choices/tips we learned about.  The full source for the application (including setup, deploying security policy and post-deploy updates) will be available to DevDays attendees in VB, C#, and a couple other .NET languages.  I'm pretty proud of it :)

Comments

Questioning said:

Have the issues of dealing with 3rd party controls been handled with the ClickOnce approach? That has been a big problem for us. Some of the things we do require special controls and the SmartClient approach just doesn't handle it. We asked Billy himself how to do it.
# February 18, 2004 6:13 PM

Susan Warren said:

The only problems we saw with third-party .NET controls was dependencies, and whether we wanted to manage them. IssueVision actually includes a number of custom .NET controls without any issues.
# February 18, 2004 6:34 PM

TrackBack said:

I asked the question here, but didn't get a definite answer. Now Susan Warren has now let some IssueVision info slide.
# February 18, 2004 10:50 PM

Joel Semeniuk said:

What about posting IssueVision on www.windowsforms.net - and, will it be better than taskvision?
# February 20, 2004 1:36 AM

TrackBack said:

^_^,Pretty Good!
# April 10, 2005 10:06 AM

TrackBack said:

I'll be blogging on IssueVision in the days and weeks to come, as I use it as a sample application on...
# April 29, 2005 12:51 PM
Leave a Comment

(required) 

(required) 

(optional)

(required)