I'm also concerned about Microsoft's beginning this on the front end. From a marketing standpoint, this approach certainly makes sense: Get Dynamics users excited and even dependent on custom apps built on this Snap architecture, then begin the longer and more painful process of merging the back-office server platforms into one product. Although it's certainly technically feasible to do this without affecting the slew of Snap applications that might be in existence by then, Redmond's track record in this department isn't stellar.

Sure, we consulting types are inwardly grinning. Worst case, we've got a new custom application architecture to sell. Best case, we can sell it twice and blame the rewrite on Microsoft. But from a journalist's perspective, all my little this-is-going-to-bite-us-in-the-booty alarm bells are going off. But then again, hey, I'm a long-time snark.

If you want to play with the Snap apps and draw your own conclusions you may be temporarily out of luck. Microsoft intends to give this code away as part of the CodeGallery on its .Net developer community site, but the linkwasn't active at the time of this writing. Chec k my SMB IT blog for the link, as well as screen shots of the Snap plug-ins, as soon as they become available.