Smart Client – Best Practices my arse

http://www.windowsforms.net has two new samples for developing Smart Client applications (basically applications that use the Web behind the scenes, a cross between a web site and an application with the best of both worlds.)

Unfortunately Microsoft doesn’t seem to be worrying too much that their "Best Practices" don’t match their samples. 

Examples:

  1. They suggest that communication with the Web Service should be done asynchronously from the User-interface, yet their sample application IssueVision doesn’t. 
  2. They suggest that communication with the Web Service should be secure and authenticated, yet their IssueVision sample sends a clear-text username and password with each web-request.
  3. They suggest that when developing a smart client, the first point of call is writing the Contracts, or WSDL, and then making the client and server communicate based upon that contract. IssueVision just uses the cheats approach of dumping the entire Database schema down in one DataSet – not scalable or efficient in the slightest.

Just pisses me off that the future of Windows applications is the Smart Client and Microsoft still haven’t given a good example of it working.

Advertisements
  1. Leave a comment

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: