Become a Columnist Microsoft Exchange Site Microsoft Support SiteMSDN Exchange Site

   

Subscribe to OutlookExchange
Anderson Patricio
Ann Mc Donough
Bob Spurzem
Brian Veal
Catherine Creary
Cherry Beado
Colin Janssen
Collins Timothy Mutesaria
Drew Nicholson
Fred Volking
Glen Scales
Goran Husman
Guy Thomas
Henrik Walther
Jason Sherry
Jayme Bowers
John Young
Joyce Tang
Justin Braun
Konstantin Zheludev
Kristina Waters
Kuang Zhang
Mahmoud Magdy
Martin Tuip
Michael Dong
Michele Deo
Mitch Tulloch
Nicolas Blank
Pavel Nagaev
Ragnar Harper
Ricardo Silva
Richard Wakeman
Russ Iuliano
Santhosh Hanumanthappa
Steve Bryant
Steve Craig
Todd Walker
Tracey J. Rosenblath
 
 
Book Reviews
Exchange & Outlook: Constructing Collaborative Solutions (Macmillan)
by Mitch Tulloch
Here's a terrific book by Joel Semeniuk and Duncan Mackenzie on how to get the most out of your Exchange/Outlook messaging platform. Joel is one of the cofounders of ImagiNET Resources Corp here in Winnipeg where I live, and Duncan works for Microsoft Consulting Services also in Winnipeg. I've often asked myself what good could come out of Winnipeg, and here it is! I'm too modest to include myself of course...

Part I of the book takes an overview of what collaborative applications are about and looks at a number of examples including workflow, tracking, messaging, and knowledge management. 

Part II continues with an overview of the components of collaborative application development for the Microsoft platform, and covers Microsoft Exchange, SQL Server, IIS, Outlook, COM, COM+, DCOM, Visual Basic, VBA, CDO, MAPI, OWA, team folders, and the digital dashboard. Most of this stuff is covered fairly generally, and you need a good programming background to see how it all works together. 

Part III is the most valuable part of the book, and deals with the actual processes involved in designing and building various kinds of collaborative solutions for workflow, tracking, and knowledge management. The focus is on Outlook 2000 and Exchange (mostly version 5.5). Lots of well-explained code examples are included for the reader to follow, but what's really good is the planned, orderly approach which the authors use for application design and development. 

The book ends with several appendices on CDO and a brief look at the collaborative possibilities of Exchange 2000. My hope is that the authors will soon revise the book to include more Exchange 2000 coverage, but it's still extremely useful because of its focus on Outlook 2000.

I give this book stars out of five. You can find it on Amazon here

Do YOU have an opinion about this book?  Let me know!
back.gif (2457 bytes) Back to the book reviews section of Mitch Tulloch's column on OutlookExchange.Com.
home.gif (2448 bytes) Go to the home page of Mitch Tulloch's column on OutlookExchange.Com.
letter.gif (161 bytes) Send me feedback on this article.
Disclaimer: I hope that the information in these pages is valuable to you. Your use of the information contained inthese pages, however, is at your sole risk. All information on these pages is provided "as -is", without any warranty, whether express or implied, of its accuracy, completeness, fitness for a particular purpose, title or non-infringement, and none of the third-party products or information mentioned in the work are authored, recommended, supported or guaranteed by me. I shall not be liable for any damages you may sustain by using this information, whether direct, indirect, special, incidental or consequential, even if it has been advised of the possibility of such damages.

Disclaimer: Your use of the information contained in these pages is at your sole risk. All information on these pages is provided "as is", without any warranty, whether express or implied, of its accuracy, completeness, fitness for a particular purpose, title or non-infringement, and none of the third-party products or information mentioned in the work are authored, recommended, supported or guaranteed by Stephen Bryant or Pro Exchange. OutlookExchange.Com, Stephen Bryant and Pro Exchange shall not be liable for any damages you may sustain by using this information, whether direct, indirect, special, incidental or consequential, even if it has been advised of the possibility of such damages.

Copyright Stephen Bryant 2008