Lamont Harrington's Blog

Quick Links

• MSDN Site: SharePoint Guidance
• Future Friendly URL: http://www.microsoft.com/spg
• Download: SharePoint Guidance - November 2008
• CodePle Site: http://www.codeplex.com/spg
• Community Forum: http://www.codeplex.com/spg/thread/list.aspx

Guidance at a Glance

This guidance helps architects and developers build SharePoint intranet applications.  The guidance contains a reference implementation that demonstrates solutions to common architectural, development, and lifecycle management challenges.  This guidance discusses the following:

• Architectural decisions about patterns, feature factoring, and packaging
• Design tradeoffs for comon decisions many developers encounter
• Implementation examples demonstrated in the reference implementation and in the QuickStarts
• How to design for testability, create unit tests, and run continuous integration
• Set up of development, build, test, staging, and production environments
• Managing the application life cycle including upgrade
• Team-based intranet application development

The following areas are not discussed in this version of the guidance:

• Content-oriented sites that use web content management
• Internet and enterprise-scale SharePoint applications
• Multilingual SharePoint applications
• Scale or security testing of SharePoint applications

To read my PDC Day 1 recap, click here.

Ray Ozzie once again kicked off the keynotes for the day.  Today, the focus was on the client and the Live Services component of the Windows Azure platform.  In his opening remarks, Ozzie further solidified our story around the integration of the PC/Web/Phone and how our strategy will fundamentally change how we as consumers interact with these devices and that consumers demands for this type of integration is growing.  Our approach is to seamlessly integrate our S+S platform across these devices, exploiting the power of the PC through our investments in Windows and client runtimes such as Windows Presentation Foundation (WPF), the power of the web through our investments in Silverlight 2 and Internet Explorer 8, and the power of the mobile device (e.g. Phone) through our investments in Windows Mobile and our Windows Live Services.  In his commentary, he basically broke down the 3 aforementioned areas as follows:
 
PC

• Full and high-performance access to displays & peripherals
• Natural UI & common controls for ink voice/audio, camera, touch
• Local data privacy, portability, reliable/fast/full access
• Use & recombine applications, data, documents, media
• A personal environment, trusted & assumed under your control

Web

• One common way to find, access, assemble & interact with people
• One common way to find, access, share & transact information
• One common way to connect devices, services, organizations & activities

Phone

• Like the PC, provide a natural UI & common controls for voice/audio, camera, touch
• Like the PC, provide facilities for local data privacy, portability, and reliable/fast/full access to data
• Like the PC, use & recombine applications, data, documents and media
• Provide a secure and reliable experience
• Provide rich access to media/data through similar facilities afforded by the PC and Web "tiers"

KEY TAKEAWAY: Microsoft's Software + Services strategy includes driving rich user experiences across multiple mediums highlighting the strategic advantage afforded to us through the Internet.  Our client runtimes such as Silverlight and WPF, coupled with our Windows brand (to include mobile) and key advances in our Internet Explorer technology will position us to deliver the next generation of user experiences on top of our investments in our Windows Azure Services Platform.
 
Windows 7 is Coming!
A lot of emphasis was put on Windows 7, as it was one of the main things PDC attendees wanted to see.  Most of the other topics discussed during the keynotes were further fleshed out during the breakout sessions, but I'll provide some commentary about those in this post.  Steve Sinofsky, Senior VP, Windows division discussed our strategy around Windows and it's future as it relates to delivering next generation experiences.  During his keynote, Sinofsky laid out our strategy around Windows 7 as it relates to what investments we're making in the OS to build upon the platform established by Windows Vista, learning from the mistakes we made with Vista (and yes, he openly said we made mistakes ) while at the same time building upon the groundbreaking work we've done in the area of Windows security, to deliver a product that we'll be proud to sell and our customers will be proud to use.  In his "Transition from Windows Vista" discussion, he highlighted several lessons learned from our Vista experience:

1. Ship solid Windows Server 2008 and Windows Vista SP1 products - With the negative press we got from the initial launch of Windows Vista, it was imperative that we shipped a solid Windows Server 2008 product and SP1 update to Windows Vista.  In reference to Vista SP1, we needed to ensure that we addressed the key issues highlighted by our customer feedback in efforts to drive broader adoption of Vista (and not just on new PC sales)
2. Ecosystem Readiness - Driving Vista readiness was a key area during the launch lifecycle where we needed to spend more energy.  Through working with our partners, ISVs, OEMs, we need to ensure that they are equipped with the information they need in order to make Vista the platform of choice for new deployments, highlighting the enhanced capabilities of the OS, and showing clear evidence of the value add for customers making the investment
3. Standards - Our investment in standards support as it relates to security, network protocols, etc has positioned us as a leader in driving industry standardization around the aforementioned areas in addition to new capabilities we introduce in future versions of the OS
4. Compatibility - Working closely with our OEMs to drive more hardware compatibility with Vista is key.  Microsoft is making significant investments in this arena, particularly as we drive towards the RTM of Windows 7, to ensure that customers have the best possible experience with Windows 7
5. Scenarios - Clear identification/clarification of Windows usage scenarios is key for us in improving the overall quality of the product.  We are taking very proactive measures to learn how the product is being used and what critical areas we need to focus on to deliver the best possible experience

Julie Larson-Green gave the PDC audience a demonstration of the Windows 7 (build 6933) and it was met with much applause and "ooohs and aaahs"   To quickly summarize the things she demoed/discussed:

• "One click" experience when navigating Windows taskbar and menus.  For example, if you have multiple instances of an application (say Internet Explorer) open on your desktop, by hovering over the any of the windows in the taskbar, you get a thumbnail view of all the instances, thereby allowing you to select whichever instance you want from a single mouse click
• Taskbar "Jump List" which essentially gives you an MRU list of the most recently launched applications & documents.  For example, if you have an Excel icon in your taskbar that you use to launch Excel, by hovering over the icon you can see a MRU list of Excel workbooks you've opened.  This capability extends to the Windows menu as well.
• "Libraries" which help you aggregate and search content across multiple hard drives and machines connected within your network
• "Homegroups", which gives you the ability to creates groups of Windows 7-based machines or other computing resources (ex: printers) within your home network and when your machine is connected, have any one of those machines automatically discover/connect to those resources.
• Ability for Windows 7 to automatically detect whether you are on your home or work network and automatically change your connection to network resources (such as printers) without you having to do any manual configuration
  Docable windows which essentially allows you to drag an application window to the left/top/right side of the screen and have it dock (or "snap") to that location.
• Windows Gadgets, which now work differently.  No more dependency of the Windows Gadget Sidebar.  Gadgets now float freely on the desktop
• Enhancements to the task tray that essentially allow you to organize what goes into the task tray (and not have it "dictated" to you by the installed application/driver/service)
• Windows 7 touch features extend to Windows Live Services such as Virtual Earth

Sinofsky stressed our focus on "Fundamentals" in our engineering efforts as we drive towards the RTM of Windows 7.  In his fundamentals discussion, he focused on the following:
 
Decrease

• Memory Footprint
• Disk I/O
• Power Consumption

Increase

• Speed (Faster Boot, Device Ready)
• Responsiveness (Start menu, Taskbar)
• Scale (256 processors)  - Yes, you read it right, Windows 7 is being positioned to support up to 256 processors)
  

It is important to understand though that Windows 7 shouldn't discount the benefits of moving to Windows Viata.  This essentially goes without saying, but opting Windows Vista positions enterprises to more easily migrate to Windows 7 when it becomes available.  Windows 7 is going to present some very compelling features that may have folks thinking they should wait, however, it's key that Microsoft wil continue to drive Windows Vista as the base platform to build upon.  Sinofsky made it evident in his keynote that we're still committed to Windows Vista.
 
What about Windows XP?
We will continue to push out updates to Windows XP for our XP customers.  It is important though to get them moving towards Windows Vista.
 
Developer Platform
Scott Guthrie came on stage and talked about our investments in our client runtimes (e.g. Silverlight, WPF) as well as our enhancements in Internet Explorer and IIS7, and our web development platform (e.g. ASP.NET, ASP.NET AJAX, ASP.NET MVC, ASP.NET Dynamic Data) as well as laid some groundwork for where our future investments are as we evolve these platforms/technologies.
 
Windows Live Services
David Treadwell rounded out the keynote to talk about our investment in the Live Services component of the Windows Azure platform.  He discussed the Windows Live Essentials offering (currently in beta and available for download at http://download.live.com/) which provides capabilities like email, blogging, messaging, photos, etc. In addition Treadwell talked about the rich integration of Windows Live Platform with Windows 7 and how key Windows Live capabilities will be a natural part of the Windows 7.
 
Announcements

• Windows Live Framework - Provides a developer framework for building applications on the Live Services platform.
• Office Web Applications - Web-based equivalents of the Office client applications (Word, Excel, PowerPoint and OneNote) During the keynotes, the Group PM of Office demonstrated the Office Web Applications.  This provides a solid platform for delivering web-enabled versions of our popular office suite that BLOWS THE DOORS off the competition.

IMPORTANT NOTE: As it relates to Office Web Applications, this should NOT be viewed as a replacement for the client suite.  As a matter of fact, the web applications should be viewed as complementary and a part of of the Microsoft S+S strategy.  It is important that this not be positioned as an alternative, but as a solution to further extend the reach of Office. 

The day was filled with great breakout sessions that covered the following products/technologies:

• Windows 7
• Live Mesh
• Silverlight 2
• ASP.NET 4.0
• WCF/WF 4.0
• "Oslo" - Codename from our new application modeling platform.
• Visual Studio 2010
• Windows Azure
• Live Services Platform
• "Dublin" - Codename for a Windows Application Server that essentially provides a highly scalable runtime environment for WCF/WF 4.0-based distrubuted applications/services

Resources

• Engineering Windows 7 Blog - Great blog that gives a "behind the scenes" view, from the perspectives of the product team themselves, on how Windows 7 is being built
• Windows Azure Portal - Provides information on the Windows Azure platform as well as it's sub-components (ex: Live Services)

That's about all I have for now   Hope it's useful.

The Best Practices Resource Center for SharePoint Server 2007 has been recently launched on our TechNet site.  The intent of the site is to provide a resource for guidance and best practices in efforts to avoid common pitfalls and keep your Office SharePoint Server 2007 environment available and performing well.  The best practices cited within the resource center is based on real-world experience from Microsoft Consulting Services and the SharePoint Product Team.

Version 1.4 of the SharePoint Server 2007 SDK and the Windows SharePoint Services 3.0 SDK has been released.

What's new in the 1.4 release of the SharePoint Server SDK?

• Installation enhancements: You now have a choice of installation path when you’re installing the SDK. Browse to your preferred folder during setup. The default installation path for the Microsoft Office SharePoint Server SDK is <%Program Files%>\2007 Office System Developer Resources.
• Start menu navigation: This release features a new Start menu shortcut for quick access to documentation (compiled HTML Help, or CHM for short) files and the Welcome Guide (ReadMe.htm), which is a landing page with links to all the tools and samples. In Windows Server 2003, click Start, Programs, 2007 Microsoft Office System Developer Resources, Office SharePoint Server 2007 SDK to open: MOSS 2007 Technical Articles and Visual How-Tos, Office Forms Server SDK Documentation, Office SharePoint Server SDK Documentation, Welcome Guide, Windows SharePoint Services SDK Documentation. In Windows Vista, click the Windows Vista Start button, All Programs, 2007 Microsoft Office System Developer Resources, Office SharePoint Server 2007 SDK to open: MOSS 2007 Technical Articles and Visual How-Tos, Office Forms Server SDK Documentation, Office SharePoint Server SDK Documentation, Welcome Guide, Windows SharePoint Services SDK Documentation.
• Offline experience improvements: All of the technical articles, visual how-to articles, and book excerpts are now packaged—plus the Excel Services and Excel 2007 Windows Compute Cluster Server 2003 Job Submission Developer Guide—into one searchable CHM file. Browse offline for content published on MSDN out-of-band with the SDK. (Known issue: Several links in the MOSSSDK_TechArticles.chm and WSSSDK_TechArticles.chm do not work in a strictly offline scenario. Also, WMV file screencasts or downloads associated with articles are not packaged in the CHM, to keep the download size manageable. Workaround: Browse to the content on MSDN online; for ease-of-use, the CHM file table of contents is the same as the MSDN Library table of contents.
• New tools and samples.  

What's new in the 1.4 release of the WSS 3.0 SDK?

• Expanded documentation of backup and restore features.  This release contains greatly expanded documentation of backup and restore features, including a new top-level node, "Backing Up and Restoring." The node includes twelve articles, including "Overview of Backing Up and Restoring Data in Windows SharePoint Services," and four new "How To" topics.
• Complete documentation of Microsoft.SharePoint.Administration.Backup.  Object model reference documentation in the Microsoft.SharePoint.Administration.Backup namespace is complete, and code samples are provided for all critical types and members.
• New documentation of the administrative object model.  A new section, "The Administrative Object Model of Windows SharePoint Services 3.0," contains six new articles, and the "Administration" section has a new, extended code sample.
• Revised Web Part documentation.  The section that provides conceptual documentation of Web Parts has been completely restructured, and two walkthrough topics have been significantly revised and rewritten.
• More migration support.  A new section, "Selective Content Migration," contains three articles to support selective migration strategies. Additionally, additions and revisions have been made to existing topics in the "Content Migration Overview" section, and a large number of API reference topics that support migration and deployment scenarios have been completed in the SharePoint.Deployment namespace.
• Expanded and updated reference documentation.  You can find enhanced documentation of types and members in the SharePoint.Workflow and SharePoint.WorkflowActions namespaces, the People Web service, and three ActiveX controls.

Version 1.2 of the Visual Studio extensions for WSS has been released and available for download.  Version 1.2 provides support for Visual Studio 2008 in building SharePoint-based solutions.  The following tools are included:

Visual Studio 2008 Project Templates

• Web Part
• Team Site Definition
• Blank Site Definition
• List Definition
• Empty SharePoint Project

Visual Studio 2008 Item Templates

• Web Part
• Custom Field
• List Definition (with optional Event Receiver)
• Content Type (with optional Event Receiver)
• Module
• List Instance
• List Event Handler
• Template

SharePoint Solution Generator

Used to generate a Site Definition project from an existing SharePoint site.

Note here that this release only works for Visual Studio 2008.  If you're still doing development using Visual Studio 2005, you'll need to install Version 1.1 of VSeWSS which can be downloaded here.

Announced on the SharePoint Team Blog, the SharePoint Deployment Planning Services program has been launched and is geared at helping our Software Assurance (SA) customers sucessfully plan and deploy SharePoint Products & Technologies.  I think this program provides a great resource for those customers who are struggling to make sense of SharePoint technologies or are trying to uncover proven "best practices" around how to properly deploy and implement SharePoint-based solutions.

During my time as a Technology Architect within the Reston, VA Microsoft Technology Center, I worked with a number of customers in definining SharePoint-based solution architectures where we covered topics such as understanding SharePoint architecture, definining portal taxonomies and physical deployment topologies/architecture, development and integration opportunities through Strategy Briefings and Architecture Design Sessions as well as "real world" implementation through Proof of Concept engagements to demonstrate the capabilties of a "live" SharePoint solution.  It's certainly great to see these getting packaged into a set of service offerings that we can make more widely available to our customers and partners.

And speaking of partners, this program is jointly managed by our partner ecosystem as well as Microsoft Consulting Services which together provides proven business and technical expertise in architecting/deploying SharePoint-based solutions for small, medium, and large organizations alike.

To learn more about the SDPS program and what it can do for you, head over to the SDPS website.  Microsoft Partners having strong competency in the Microsoft Office System stack are encouraged to sign up and participate in this growing community.

Version 2.0 of the OBA Composition Reference Toolkit was released to the web today, on schedule and with all the great new features promised for the release. Version 1.0 of the toolkit was released at the Office Developer’s Conference in February 2008.

Watch the OBA Composition Reference Toolkit Overview Video to get an overview of the toolkit, the motivations for creating it, and its intended use. Visit the OBA Composition Reference Toolkit site to access and explore related resources: Installers for the toolkit & sample components, Documentation – architecture, user, admin, developer, and overview video.

What’s New in Version 2.0?

• IT administration capabilities integrated into the SharePoint Central Administration portal
• A prescriptively secure user experience for OBA composition
• Support for incremental deployment of OBAs.
• Support for installing the OBA Composer on a client computer that is running the Windows Vista operating system and connecting to a remote computer that is running Office SharePoint Server.
• Spport for many new, out-of-the-box components, too, which cover scenarios that pertain to Expense Reporting, Purchase Requisition Management, Financial Services, and Health & Life Sciences solutions
• Source code (framework, tools, and sample components) of the OBA Composition Reference Toolkit to enable independent software vendors (ISVs) and solution integrators to extend and repurpose the Toolkit to suit their individual needs.

Visit the OBA Composition Reference Toolkit site for more information.

Zach Rosenfield (a Program Manager on the SharePoint Team) posted an announcment introducing the SharePoint Administration Toolkit.  This promises to be a great resource for administering your MOSS and WSS v3.0 deployments.  The initial version of the toolkit contains a couple of useful administrative tools, including the Batch Manager, which allows you to schedule bulk operations against site collections in a SharePoint farm, and a new command to the STSADM command-line utility called "updatealert" which will refresh all alert URLs in a specific site collection, which is important if you change the URL of a web application or after an upgrade.  A full whitepaper describing the toolkit can be found here.

Check out Zach's post of you want to have a good understanding of what the toolkit addresses and the features it contains.  The toolkit is available for download for both x86 and x64 SharePoint deployment configurations.

Enjoy!  I know I will!

I mentioned in a previous post the work I've been doing with the Library of Congress.  It has been a great effort and an excellent showcase of the power and flexibility of our platform.  On April 12th, we closed another chapter in this unprecendented effort by officially launching their myLOC.gov website.  The website has been architected and built on top of a platform consisting of SharePoint Server 2007, Silverlight, Windows Communication Foundation, and Windows Live ID.  The launch of the myLOC.gov site on this past Saturday marked the culmination of 9 months of work to deliver a compelling solution that's geared at reshaping how Americans view American History by literally bringing many of the historical treasures contained within the walls of the Library of Congress to life and allowing not only the American people, but the entire world to experience this great treasure.

The launch of the myLOC.gov website capped off a great week for the Library of Congress and Microsoft.  As a part of the revitalized digital experience, coined the "Library of Congress Experience", is also the launch of Windows Presentation Foundation (WPF)-based interactive touch screen kiosks that's running within the Library of Congress's Thomas Jefferson Building in DC.  There, US citizens, and people travelling to DC from around the world, will be able to enage within an immersive technology experience that allows people to interact with the Library's historical collections in new and exciting ways.  The myLOC.gov site takes this onsite experience and brings it to the web!

In the coming weeks, myself, in combination with our great partners, Portal Solutions and Schematic will be creating a "How We Did It" article (likely to be posted on the SharePoint Team Blog), in the same vein as the two-part article I published on another great effort with Conservation International, that'll dive deeper into the overall solution architecture and cover specifics around logical and physical architecture as well as discuss implementation details of key features and functionality.

So stay tuned!

Microsoft has recently released a set of lectures and whitepapers on advanced topics around Office SharePoint Server 2007.  Below is a description (taken from the TechNet website) of topics and links.

An excellent whitepaper is available on our downloads site that provides guidance on implementing solutions on top of SharePoint Server 2007 and Windows SharePoint Services 3.0.  A breakdown of the sections is cited below:

• Chapter I - Document Goals
• Chapter II - Implementation Scenarios
• Chapter III - Implementation Environments
• Chapter IV - Implementation Activities
• Chapter V - Deployment Methods
• Chapter VI - Tools for the Job
• Chapter VII - Implementation Project Plan and Team
• Chapter VIII - Implementation Worksheet
• Chapter IX - Hotfixes
• Chapter X - Testing
• Chapter XI - Summary
• Chapter XII - Glossary
• Chapter XIII - References
• Virtualization
• SDKs and Centers
• Dev Tools
• Packaging Tools
• SOLUTION Framework
• Bin or Global Assembly Cache
• Features
• Authoring and customization
• Content Deployment / Migration
• Team Development
• Testing, Source Control and MSF
• Patterns and Practices
• Chapter XIV - Credits and Thanks To

Definitely worth the download.

Our Architecture Strategy Team has recently unveiled a great solution geared at simplifying the task of building Office Business Applications (OBA) using the Microsoft Office System platform. 

The solution, called the OBA Composition Reference Toolkit,  surfaces the underlying composition capabilities of the 2007 Office System and provides a prescriptive application composition experience for Information Workers to build OBA solutions. 

You can head over to the Architecture Center on MSDN to get more information about the solution and download the bits.  Right now, only the binaries are available, but the plan is to release the source code by mid-March.

Over on the SharePoint Team Blog is a good post citing resources related to deployments of MOSS/WSS on Windows Server 2008.  With the pending launch of the next release of Windows Server, it's important to know the impacts it has on deploying SharePoint Products & Technologies within your organization.  The resources cited in the post cover the following areas:

• WSS deployment on Windows Server 2008
• MOSS deployment on Windows Server 2008
• Upgrading from Windows Server 2003 to Windows Server 2008 with existing SharePoint deployments
• SQL Server 2008 and SharePoint deployments

Check out these resources if you're planning on deploying MOSS/WSS on Windows Server 2008 or want to understand more about the process.  As we near launch of Windows Server 2008, you'll start seeing even more resources around this very topic.

Microsoft has recently released SP1 for both Office SharePoint Server 2007 and Windows SharePoint Services 3.0.  For a list of what's included in the service pack, you can view the SP1 whitepaper posted to Microsoft's TechNet website.  This information will be important from both a business and technical perspective as it relates to support installing SP1.  There's also a KB article that's recently been posted that provides invaluable information about SP1.

Important Note: WSS 3.0 SP1 should be installed before SharePoint Server 2007 SP1.

Critical Planning and Deployment & Installation Information 
Before installing SP1, read deploying software updates for Windows SharePoint Services 3.0 which will help you understand tips tricks and troubleshooting steps and Planning and deploying SP1 for Microsoft Office SharePoint Server.

Download locations:

Windows SharePoint Services

• Windows SharePoint Services 3.0 SP1, 32-bit edition and 64-bit edition
• Windows SharePoint Services Language Pack 3.0 SP1, 32-bit edition, 64-bit edition

Office SharePoint Server

• Office SharePoint Server 2007 SP1 (includes SP1 for Project Server, Forms Server, and Groove) 32-bit edition and 64-bit edition
• Office SharePoint Server 2007 Language Pack 3.0 SP1 32-bit edition, 64-bit edition