Corro'll Driskell

Requirements for Building a Master Pages From the Bottom Up using SharePoint Designer 2007

Corro'll Driskell — Fri, 03 Apr 2009 19:49:00 GMT

There has been a number of conversations over the last year referencing building master pages from the bottom up using SharePoint Designer ( 2007).

Although It is a best practice – using SPD 2007 - to build customized master pages using an existing master page, it does not replace the fact that in order to recognize the various components that make up the master page a designer must build a master page from the ground up.

There are a number of blogs that speak to this process. It is not my intent to duplicate any postings. It is my intent to discuss this process in my own words and to add value based on the feedback from a number of sessions. All designers, should download the base.master file from Microsoft and use it as a starting point.

There are a number of blogs that identify the required controls and placeholders for Master Pages:

Discover How to Build Various Master Pages

To start, I would recommend that designers open up a number of master pages in SharePoint Designer’s Code View. You will note the consistent tags between the <HEAD></HEAD> elements. Remember, you would need to ensure that all of the required controls and content place holders are included on the master page.

1. You can copy the head elements of an existing master page. That is a great way to avoid making mistakes.

/***
<SharePoint:RobotsMetaTag runat="server"/>

/*** Displays the set title for the site in the tile bar ***/
<Title ID=onetidTitle><asp:ContentPlaceHolder id=PlaceHolderPageTitle runat="server"/></Title>

/*** The CssLink control calls the core.css cascading style sheets from the WFE server’s 12 Hive ***/
<SharePoint:CssLink runat="server"/>

/*** The Theme control calls the cascading style sheet for the associated theme ***/
<SharePoint:Theme runat="server"/>

/*** The ScriptLink control runs the core.js javascript file. It contains the basic SharePoint functions. ***/
<SharePoint:ScriptLink language="javascript" name="core.js" Defer="true" runat="server"/>

/*** Calls on any custom javascript files. ***/
<SharePoint:CustomJSUrl runat="server"/>

/*** Identifies the site’s disco file that defines the web services. ***/
<SharePoint:SoapDiscoveryLink runat="server"/>

/*** Content Place Holder that allows additional information to be added to the Page head. ***/
<asp:ContentPlaceHolder id="PlaceHolderAdditionalPageHead" runat="server"/>

/*** SharePoint uses the DelegateControl to add additional content between the head elements. ***/
<SharePoint:DelegateControl runat="server" ControlId="AdditionalPageHead" AllowMultipleControls="true"/>
</HEAD>

2. Copy the opening body and form tags from an existing master page and overwrite open body and form tags.

3. In the event that you created a Master Page using the .masterpage template, delete the ContentPlaceHolder1 ContentPlaceholder & Save the master page.

<asp:ContentPlaceHolder id="ContentPlaceHolder1" runat="server">
</asp:ContentPlaceHolder>

There are a number of Designers that would like to utilize absolute positioning to control the placement of objects on the master pages versus using tables. To be exact, Designers would like to get rid of the “SharePointy Look”. No,…. the SharePointy term is not yet recognized by Wikipedia. I could not resist adding a bit of humor to this post.

In order to leverage absolute positioning a Designer is required to do the following:

1. Wrap the PlaceHolders with DIV and SPAN elements.

2. Use a Cascading Style Sheet (CSS) to position the PlaceHolder on the page.

In the event that a Designer would like to leverage tables, there are a number of SharePoint Designer features that are available.

3. Click on the Table menu.

4. On the Master Page the Designer must identify the location of the Web Part toolpane. By default, the Web Part toolpane is located in a table cell. The MSO_ContentDiv is a placeholder control. It’s purpose is to allow SharePoint to add the web part toolpane.

Note: A Designer can use a table for formatting inside of the MSO_ContentDiv PlaceHolder. The default.master file provides a great example.

Note: The primary PlaceHolder used out of the box is the PlaceHolderMain. Within the PlaceHolderMain elements a Designer can use a table to layout the content in that area.

5. For all placeholders that are not used by the Designer, it is recommended that the Designer use the Panel control to hide the un-used placeholders. A Designer’s other option would be to set the visible property to false for each placeholder.

<asp:panel visible="false" runat="server">
<asp:ContentPlaceHolder ID="PlaceHolderBodyLeftBorder" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderBodyRightMargin" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderCalendarNavigator" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderFormDigest" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderHorizontalNav" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderLeftActions" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderLeftNavBar" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderLeftNavBarDataSource" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderLeftNavBarTop" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderMiniConsole" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderNavSpacer" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderPageImage" runat="server" />
<asp:ContentPlaceHolder id="PlaceHolderSearchArea" runat="server" />
<asp:ContentPlaceHolder id="PlaceHolderSiteName" runat ="server" />
<asp:ContentPlaceHolder id="PlaceHolderTitleAreaClass" runat ="server" />
<asp:ContentPlaceHolder ID="PlaceHolderTitleAreaSeparator" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderTitleBreadcrumb" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderTitleInTitleArea" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderPageTitleInTitleArea" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderTitleLeftBorder" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderTitleRightMargin" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderTopNavBar" runat="server" />
<asp:ContentPlaceHolder ID="PlaceHolderUtilityContent" runat="server" />
<asp:ContentPlaceHolder ID="SPNavigation" runat="server" />
<asp:ContentPlaceHolder ID="WSSDesignConsole" runat="server" />
<asp:ContentPlaceHolder ID="OSSConsole" runat="server" />
<asp:ContentPlaceHolder id="PlaceHolderBodyAreaClass" runat ="server" />
<asp:ContentPlaceHolder id="PlaceHolderPageDescription" runat="server"/>
</asp:panel>

This is just a start. I encourage you all to look out for Enrique Lima’s posting over the next few days. I will update this blog with a reference to his detailed steps for, “Building a Master Page from the ground up”.

Summary of Resources for the SharePoint Designers

Corro'll Driskell — Thu, 19 Feb 2009 14:33:00 GMT

During a number of facilitated sessions, I mention a number of resources that all SharePoint designers must reference. I have included a reference to those resources in this blog. I will update this blog post with additional information on a consistent basis. Please continue to add value by posting additional references in you comments.

Disclaimer: I am not personally responsible for the content of the listed resources.

In order to properly customize a SharePoint platform. It is my position that all designers must have a basic knowledge of SharePoint. I have included some links to introduce you to the SharePoint platform and its offerings.

An Introduction to Office SharePoint 2007

Microsoft Test-drive – (You need to sign up for this.)

Virtual Lab: SharePoint Products and Technologies

Although the use of SharePoint Designer 2007 doesn’t require knowledge of code, I strongly believe that all designers should learn about XML, HTML and CSS. There is a significant value in reviewing the following links:

XML, HTML, and CSS resources:

W3C MarkUp Guide

Introduction to CSS2

XML Schema Part 0: Primer Second Edition

CSS Classes in SharePoint’s core.css

CSS Zen Garden – some great examples of what can be done with CSS

World Wide Web Consortium (W3C) recommendations for XPath (version 2.0)

Surfacing CSS Classes in SharePoint Pages

In order to ensure that an organization follow organizational and government policies, SharePoint designers must ensure that they are knowledgeable about accessibility and how SharePoint Designer adds value. It has become more important for organizations today to include accessibility in their project plans.

Accessibility of SharePoint Sites:

Tips for Enhancing the Accessibility of SharePoint Web Sites

Section 508 VPATs for Microsoft products

Additional Workflow tools:

Windows SharePoint Services 3.0 Starter Kit: Workflow Developer Starter Kit for Windows SharePoint Services 3.0

Note: The Workflow Developer Starter Kit for Windows SharePoint Services 3.0 (WSSWorkflowStarterKitB2.msi) templates are now part of the Windows SharePoint Services 3.0 Software Development Kit (WssSdk.exe).

Software Development Kits:

Windows SharePoint Services 3.0 Software Development Kit

SharePoint Server 2007 SDK: Software Developer Kit

Design Policies and Templates:

Office SharePoint Server 2007 Customization Policy
by Sean Livingston

WSS 3.0 Master Pages and Content PlaceHolder’s: A Desktop Reference Companion

MOSS Navigation Deep Dive – Part 1

Other Resources:

Adding the Edit Button to the IE7 Toolbar:
by Kathy Hughes

How to configure form results and have them sent to multiple email addresses?

Customizing the menu control for MOSS

Overview of Field Controls

Stramit SharePoint 2007 Master Picker

Search Resources

Google Code Search

Discover SharePoint

Technorati Tags: SharePoint Designer,Office SharePoint Server 2007,Windows SharePoint Services 3.0

UDiscover SharePoint User Group

Corro'll Driskell — Wed, 18 Feb 2009 22:34:00 GMT

Become a member of 'potentially, the largest SharePoint user group. The purpose of UDiscover SharePoint is to remove the boundaries of brick and mortar style user groups. The official launch date is February 25, 2009.

Contributor Settings... Site by Site

Corro'll Driskell — Wed, 18 Feb 2009 22:01:11 GMT

There are a number of blogs that focus on configuring ( Create a Contributor group) the the Contributor Settings in SharePoint Designer 2007. It is not my intentions to provide the step by step to create and configure contributor settings.

Also, I can site a number of sites that clearly define the intentions of Contributor Settings (Introduction to Contributor Settings). In summary, the intent of the Contributor Settings is to control the use of SharePoint Designer on a site by site basis.

I am posting this blog to discuss the limitations of the Contributor Setting configurations and proposed work around. The fact that contributor settings are configurable on a site by site basis is not a great option in a number of site deployments. The fact that new sites are created within site collections at an alarming rate, is a compelling reason to ask for more of a centralized capability to set the contributor settings at the site collection level and to push it down throughout its namespace. In fact, it would be great to ensure that all sites across all web applications - scoped at individual sites - are dynamically configured with the required contributor settings.

The fact remains that Contributor Settings can only be set by using SharePoint Designer as the Site Manager. After the [contributor setting].htm - generally named using the GUID of the site - is created, the [contributor setting].htm can be added to a site template using the File element in the ONET.XML file.

But, in the event that Designers do not have access to the Web Front End (WFE) servers, adding the [contributor setting].htm as a file element to the ONET.XML file, is not a viable option.

What we have found that adds some value for our SharePoint Designers - using SharePoint Designer 2007 - is that you can create a site - using the Browser or SharePoint Designer 2007 as a tool. After creating and customizing - it is titled Branding in some eyes - the site.

Once the site is customized, the Site Manager can create Contributor Groups and Region Types. After configuring the Contributor Settings, the Site Manager, Site Owner or Site Collection Owner - that all depends on the level of the site and the tools - Browser or SharePoint Designer - can save the site as a template.

To ensure that the save template(s) are used, the Site Collection Administrator or Site Owner can limit the template choices to the template(s) configured with the Contributor Settings.

The option presented is not the most centralized way to ensure the use of a consistent contributor settings across a number of sites within a site collection. But, it presents an option to ensure the authorized use of SharePoint Designer 2007 on each sub-site.

I hope that this helps.....

Technorati Tags: SharePoint Designer 2007',SharePoint Technologies,MOSS 2007,WSS 3.0,Mindsharp

Rolling up Calendars using SharePoint Designer

Corro'll Driskell — Thu, 11 Dec 2008 18:26:00 GMT

There are a number of requests in regards to rolling up calendar events from various sites to a site hosting a master calendar. The most economical choice is to use SharePoint Designer 2007.

"This post, only, focuses on creating linked calendars."
1. You will need to open up the site that will host the master calendar. After selecting the URL for the hosting site, Click on the Open button.

2. After the web site is opened in SharePoint Designer you will see all related folders and files displayed in the Folder List.

3. Click on the Task Pane menu and Select the Data Source Library. The Data Source Library is displayed.

4. From the Data Source Library task pane, select Connect to another library... the Manage Library dialog box appears. Click on the Add button.

5. The Collection Properties dialog box is displayed. In the Display Name text box, type the name of the site. In the Location text box, type in the URL for the source site. Click on the OK button to close the Collection Properties and Click the OK button to close the Manage Library dialog box.

Note: The new Collection - IT Services - is available from in the Data Source Library.

6. In the Data Source Library task pane, navigate to the Current Site Collection . Click the plus symbol next to Current Site. Next, Click the plus symbol next to the Linked sources and Click Create a new linked source… button. Next, Click on the Configure Linked Source... Button.

7. The Link Data Sources Wizard dialog is displayed. In the Available Data Sources list box, ensure that the Current Site Collection data sources are displayed. Next, Click on the SharePoint Lists and select the Calendar list. Next, Click on the Add button.

8. In the Available Data Sources list box, Click on the IT Services Collection's data sources are displayed in the Available Data Sources. Next, Click on the SharePoint Lists and select the Calendar list. Next, Click the Add button. Finally, Click on the Next button.

9. In the 'Select the link type that best represents the relationship between the selected sources' section, Select the option, 'Merge the contents of the data sources. Choose this option if you'd like to sort, group, and filter the sources as one long list.' Click the Finish button.

10. The Data Source Properties are displaying the added Calendars in the Component source properties section. Click on the OK button.

Note: After the Linked Data Source is saved, it is named New Data Source in the Linked sources section.

11. Using SharePoint Designer, Create a new ASPX page in the current site. Click in the Form control to position your cursor.

12. Click on the Data View menu. Next, Click on Insert Data View.. option. The DataFormWebPart is added in the Form control.

13. Navigate to the Data Source Library task pane. Drag and drop the merged calendars - New Data Source - onto the DataFormWebPart on the new page.

14. Click on the 'On Object User Interface' (OOUI), It will open the 'Common Data View Tasks'. Click on the Edit Columns.. option.

15. Remove both Modified By and Modified from Displayed Columns list box and add Location field from the Available fields list box. Next, Click on the OK button.

16. Navigate back to the Common Data View Tasks properties. Click on the Filter option. Use the table below to configure the filters. After configuration, Click the OK button.

Field Name	Comparison	Value	And/Or
Start Time	Greater Than or Equal To	[Current Date]	Or
End Time	Greater Than or Equal To	[Current Date]	And

17. Save the page and preview in the browser. You can add events to all calendars included in linked sources and it is reflected in the rendered page.
Note: You can attach the page to the master page for the site to ensure that it is branded like all other pages.

Technorati Tags: SharePoint Designer 2007,MOSS,Office SharePoint Server,Windows SharePoint Services

Enable Enterprise Features

Corro'll Driskell — Fri, 28 Nov 2008 22:13:00 GMT

Enterprise Features
Enable Enterprise features
In the event an administrator decides to install Microsoft Office SharePoint Server 2007 by using the Standard license type, the following features are available:
Collaboration
Enterprise content management
Workflow
My Sites
Profiles and personalization
Enterprise search

On the other hand, a SharePoint Administrator can convert the license type to the Enterprise license, which would enable and, allow the SharePoint Administrator to push down the Enterprise feature set to all sites within a server farm. The following additional features, in conjunction with the Standard license features, are available with the Enterprise license type:
Business Data Catalog
Excel Services
Report Center
InfoPath Forms Services

Enable Enterprise features
In Central Administration, on the Operations tab, under Upgrade and Migration, click Enable Enterprise Features.
On the Enable Enterprise Features page, under Use these features, click Enterprise (Requires Enterprise client license).

In the Enter Product Key box, type the Enterprise Client license key.
Important You cannot return to using the Standard feature set after you have enabled the Enterprise feature set. If you want to return to using only the Standard features, you must turn off all of the Enterprise features on all sites. Alternatively, you can uninstall Office SharePoint Server 2007, reinstall it by using the Standard license type and create a new server farm, and then attach the content databases to the new farm. BTW, bad, bad, bad….
Enable features on existing sites
In Central Administration, on the Operations tab, under Upgrade and Migration, click Enable Features on existing sites.

On the Enable Features on existing sites page, select the Enable all sites in this installation to use the following set of features check box.

After enabling features for all sites, you will note the enabling status displaying a status of Initializing.
In essence, the configuration of the features allows a SharePoint Administrator to manage the features at both the Farm and Web Application level.

Manage Farm Features

Manage Web Application Features

Configuration of the BDC in the TrainsByDave environment

Corro'll Driskell — Thu, 06 Nov 2008 06:36:00 GMT

1. Login to the Student 12B image with the Administrator Account.

2. Click on the Start button and navigate to the Administrative Tools and click on Services.

3. In the Services dialog box. Locate the Microsoft Single Sign-on Service and double click it.

4. Click on the Log on tab. Select the ‘This account’ option and configure it with a domain account. After configuration, click on the OK button.

Note: I used the Administrator account to simplify the configuration process. Any other time, you would use a service account here. When configuring the Single Sign-On settings in the Central Administration site you would need to logon with the service account.

5. Right click on the Microsoft Single Sign-on services and click on the Start option. After start, close the Services window.

Note: After clicking on the Start Option is clicked. The Service Control dialog box displays the status

6. Navigate to the Central Administration web site and select the Operations Tab.

7. Go to the Security Configurations section and click on the Manage settings for single sign-on link. It will take you to the Manage Settings for Single Sign-On for MOSS01 page.

Note: You will notice that the Manage Server settings is your only available option. If you fail to configure the Microsoft Single Sign-On service with a service account - in our scenario the administrator account – no option would be available. They would all be grayed out.

8. In the Server settings section, click on the Manage server settings .

Note: You are taken to the Manage Server Settings for Single Sign-On page.

9. On the Manage Server Settings for Single Sign-On page in the Single Sign-On Administrator Account text box type the name of the group - we are using an individual account in our scenario - or user account – trainsbydave\administrator - that can set up and manage the single sign-on service. This account must be a member of the same domain to which the single sign-on service account belongs.

10. Next, on the Manage Server Settings for Single Sign-On page in the Enterprise Application Definition Administrator Account text box type the name of the group - we are using an individual account in our scenario - or user account – trainsbydave\administrator - that can set up and manage enterprise application definitions. This account must be a member of the same domain to which the single sign-on service account belongs.

11. Do not change any other setting on the Manage Server Settings for Single Sign-On page. Click on the OK button.

12. After you are returned to the Manage Settings for Single Sign-On for MOSS01, you will notice that you can configure other settings for the Single Sign-On service. Click on the Manage settings for enterprise application definitions link in the Enterprise Application Definition Settings section.

13. On the Manage Enterprise Application Definitions page, click on the New Item link.

14. On the Create Enterprise Application Definition, you will create an Application Definition file used by the Business Data Catalog (BDC) to connect to the AdventureWorksDW database.

15. Also, on the Create Enterprise Application Definition, you will configure the account type. In our scenario, we will use the Individual account type.

Note: In the event that you decide to use the Group – trainsbydave\domain users setting, the SQL database administrator must ensure the group account has permissions on the various databases.

16. Also, on the Create Enterprise Application Definition, you will configure the authentication type. In our scenario, we are using the Windows Authentication type.

17. Also on the Create Enterprise Application Definition, you will configure the Logon Account Information. In our scenario, we are accepting the default values. Click on the OK button.

18. On the Manage Enterprise Application Definitions, you will see the AdventureWorksDW SSO definition file.

19. Open the Windows Explorer application and navigate to the 2007 AdventureWorks Samples folder (C:\Program Files\2007 Office System Developer Resources\Samples\Business Data Catalog\AdventureWorks Samples)

20. Make a copy of the AdventureWorks2005DW.xml and AdventureWorks2000_SSO.xml files.

21. Open the AdventureWorks2005DW.xml file using SharePoint Designer 2007 or Visual Studio 2005. Once the AdventureWorks2005DW.xml is open, locate the RdbConnection Data Source property and set the property to MOSS01.

22. Next, open the AdventureWorks2000_SSO.xml file with SharePoint Designer 2007 or Visual Studio 2005.

23. Copy the Property elements for both, SSOApplicationID and SSOProviderImplementation from the AdventureWorks2000_SSO.xm. to AdventureWorks2005DW.xml after the RdbConnection Intergrated Security property. Verify that the Property elements are well formed and save the AdventureWorksDW.xml file. Close SharePoint Designer or Visual Studio 2005.

24. Navigate to the Central Administration site. On the Quick Launch Bar navigate to the Shared Services Service: SSP01 page.

25. Navigate to the Business Data Catalog section of the Shared Services Service: SSP01 page. Click on the Import Application Definition link. It will take you to the Import Application Definition page.

26. On the Import Application Definition page, click on the Browse button in the Application Definition section and browse to the location you saved the AdventureWorks2005DW.xml (:\Program Files\2007 Office System Developer Resources\Samples\Business Data Catalog\AdventureWorks Samples) file. Click on the Open button and verify the path.

27. Accept the default values for all other sections on the Import Application Definition page. Click on the Import button at the bottom of the page. A verification process status bar appears. Click on the OK button.

28. Next, you are taken to the View Application: AdventureWorksDW page. Click on the Manage Permissions link. It will take you to the Manage Permissions: AdventureWorksDW page. Click on the Add User/Groups link.

29. On the Add User/Groups page in the Choose Users section, add the trainsbydave\domain users group.

30. On the Add User/Groups page in the Choose permissions section, select all, four, permissions. Click on the Save button. You are taken back to the Manage Permissions: AdventureWorksDW page.

31. Select all users and groups on the Manage Permissions: AdventureWorksDW page. Click on Copy all permissions to descendants link. Click the OK button for the dialog box displayed.

Note: This option ensures that the permissions for the listed users and groups are on all Access Control Lists (ACLs) for each entity identified in the Application Definition file.

Note: Additional documentation will follow for demonstrations for, both, SharePoint Designer and Excel Services. If you are familiar with the existing Excel Services and Business Data Catalog (BDC) Web Parts, you can start using the BDC.

Understanding Change, Power, and Conflict in your SharePoint Server 2007 Deployment - Mark R. Schneider

Corro'll Driskell — Mon, 15 Sep 2008 23:23:00 GMT

Mark Schneider's focus is on on how to guide your organization through reasonable change.
Mark spoke to change in an organization as a skill. Mark stated that, "Share point is an agent of change." The point is that governance makes change more manageable. Overall, an organization need to be forthcoming and open. It is the empowerment of people." With that in mind, we have to provide guidance for that change.

You need. 5 things to properly manage change.

1. Support of A champion

2. Grassroots support

3. Approved and funded budget

4. Clear objective and goals

5. Control over the project

Most importantly, Mark expressed that an organization should ensure that people are trained. Mark encourages an organization to communicate leveraging the SharePoint technologies -Blogs - and provide an example by leveraging a Team Site template. That is, project managers should lead by example.

Best practices in a nutshell is to work to ensure that people don't result to using their imaginations to fill communication gaps. The psychological effect of ,an unmanaged, SharePoint implementation in an organization prompts negative responses at time. That is, you need to balance your approach for changing both technologies and processes. Overall , you want to avoid a chaotic impact. The fact that people naturally respond negatively to unplanned change encourages governance.

Submitted from the Blackberry....
-------------------------------------------------------
Corro'll Driskell

Getting on the SharePoint Roll

Corro'll Driskell — Thu, 21 Aug 2008 23:27:00 GMT

Over the last few months, I have been tasked with working on a number of SharePoint related engagements. What I find amazing is how can any one person can find the time to blog, speak, consult and manage to spend time with family. First, I have to be thankful for having a family that understands and support ME. It is obvious that I have worked with some great people over the last year. BTW - that includes some international travel.

Although I have a schedule filled throughout the year, I am speaking at the SharePoint Best Practices Conference. I want to discuss my presentation and how important it is to the actual deployment and branding of business application deployed on the SharePoint platform. First, the title of my presentation is, "Content Development and Deployment using Publishing and SharePoint Designer 2007". The purpose of the presentation is to solidify best practices in which multiple content developers can use SharePoint Designer and the publishing features of a single mirrored environment to simplify the development of content (masterpages, custom pages, pagelayouts, content and styles) and its migration into a production environment. Here is the catch...., both the mirrored and production environment are hosted on the same physical farm.

At the same time, I have been co-authoring a book with Enrique Lima. The title of the book is, "Developer's Guide to InfoPath Form Services". Openly, I admit that it has taken quite a bit of time out of my day and night. In fact, I have had quite a time over the last few months managing my time. But, I am enjoying every bit of the sacrifice. I will keep you all posted with the timelines.

Finally, I am working to promote the SharePoint Designer Discussion Group. I encourage all to visit and consider joining the group. The purpose of the group is to share SharePoint Designer 2007 experiences with others. It has grown over the months. In fact, I have taken more of a hands-off approach. I love the energy.

BTW - I am open to speaking at user groups. Yes, that is right. I am open to speaking at user groups.

Signing Off - Whoooo Hooooo

Corro'll Driskell

SharePoint Best Practices Conference

Corro'll Driskell — Mon, 28 Jul 2008 23:09:00 GMT

The message...

"The 2008 Best Practices Conference replaces confusion with Clarity, Direction and Confidence by establishing key principles to guide effective SharePoint decision-making in any situation. "

Working with many organizations there are a number of questions referencing Office SharePoint Server 2007 and Windows SharePoint Server 3.0 and Best Practices. Across the SharePoint solution stack, it is very difficult to answer all questions with the limited time constraint.

Enter the Best Practices SharePoint Conference utilizing a great tag line: "Clarity, Direction and Confidence".... The catch phrase does an excellent job conveying the goal of this conference. Obviously, all must consider attending.

http://www.sharepointbestpractices.com