SharePoint Happenings

There are many ways to programmatically retrieve documents from within SharePoint. Some choices are more obvious, like for instance when you're within a web request that has a SharePoint context. When that is the case the best approach is to leverage that SPContext (SPContext.Current.Site…) and pull out an SPFile object that contains the byte array of your document's content. However, some of the less obvious choices come when you don't have an SPContext. These are as follows:

Option 1) Leveraging the SharePoint API and specifically the SPFile Object (AGAIN)

Even without a SPContext you can get at the SharePoint API if your code is running on one of the farm's web front ends. In this case you'll have a SharePoint DLL available to you in the global assembly cache, and you can code against the API, eg: SPSite site = new SPSite("http://intranet");

Option 2) Leveraging the SharePoint Web Services

If you're not on the web front end, it would be a better choice to use SharePoint's web services to get at SharePoint data. For instance, with the Lists.asmx web service you can do stuff like download/upload a document, instantiate a new List, check out a document, etc. The only problem with the SharePoint web services is the goofy XML you got to deal with – making "batches", as they call them, can be daunting for newbies.

Option 3) Keep it simple with HTTP

A third and not well known approach is simply to use web requests to get at data over HTTP. If you know the URL to your SharePoint data, simply create a web request/response to that data and do something with it. The WebClient object makes this very easy:

using (WebClient wc = new WebClient())

{

wc.Credentials = new NetworkCredential("domain\\username", "password");

byte[] doc = wc.DownloadData("http://intranet/documents/documentA.docx");

MemoryStream mems = new MemoryStream();

mems.Write(doc, 0, doc.Length);

// Make some Edit to the stream here...

wc.UploadData(url, "PUT", mems.ToArray());

}

Notice how I'm passing credentials into this WebClient, and thus authenticating to secure SharePoint data. Then I call the DownloadData mehtod and pass a URL, this returns a byte array that contains my data/document from the web response. In essense these are the bytes of a document if that URL is the URL to a document in SharePoint, otherwise it would be the bytes of a SharePoint page or list.

Next I load that byte array into a stream, in which case I could make all kinds of alterations to that document that I want. Afterwards, I can call the UploadData mehtod to save my changes back into SharePoint.

Pretty easy huh? I guesss there's 2 morals to this story – 1) don't make things more complicated than they ought to be, and 2) HTTP web requests/responses still have their place. Truth be said, I often leverage all three mechanisms quite oftent, and the architecture usually dictates which approach is best. The order though makes sense. My first preference is option one. Then the second option is usually needed for more complicated functions. If it is simple I go with option 3.

Now with all that said – the Client Object model that comes new with SharePoint 2010 sure mixes this up a lot. But more on that later…

Phil

Presentation Slides & Source: SharePoint and Azure Integration

BENDER\pwicklund — Tue, 03 Nov 2009 08:01:00 GMT

Note: this presentation was derived from a solution first built by Wictor Wein and Eric White, please reference this article for the complete write-up

Last Thursday I presented at Microsoft and RBA's October brew, featuring the Twin Cities Cloud Computing user group. My topic was on integrating SharePoint Online services with Windows Azure. For those who were there, below you'll find my slide decks and a link to download my source code. Email with questions!

http://tccloud.com

Phil

InLine List Item Editing with SharePoint 2010

BENDER\pwicklund — Mon, 02 Nov 2009 10:35:41 GMT

I'm sure you've seen the "Web Edit" functionality as described in the sneak peak, but did you know you can also do inline edition of list items? It's pretty slick… by default however, inline editing of list items is not enabled. You must alter the view to enable it. Here's how to do it (pretty easy stuff):

STEP 1) Navigate to your list. In the ribbon, click List, then click Modify this View:

STEP 2) Scroll to the bottom, and expand the Inline Editing plus box. Check the Allow inline editing box and click ok:

DONE!

Now test. Notice you now get a "New" icon that wasn't there before. When clicked, you can add a new item into the list without needing a post back:

Also, when you hover over an existing item, you can click the edit icon and start editing the item right inline:

LOVE IT!

Phil

New Conditions and Actions for SharePoint Designer 2010 Workflows

BENDER\pwicklund — Mon, 26 Oct 2009 07:53:38 GMT

With the onset of SharePoint Designer 2010, there are quite a few new out of box actions and conditions that can be leveraged in SharePoint Designer workflows. Check the list below to see what's new:

Out of Box Actions List for SharePoint Designer 2010:

Highlighted Actions are New for 2010

APPROVAL ACTIONS
Assign Item For Approval	You can start a new Approval workflow instance on this item, or a new/different.
Assign Item For Feedback	You can start a new Feedback workflow instance on this item, or a new/different.
General Task Process	Seems to do the same thing as Assign Item For Approval
CORE ACTIONS
Add a comment	Similar to "Log to History List"
Add Time to Date
Do Calculation
Log to History List
Pause for Duration
Pause until Date
Send an Email
Set Time Portion of Date/Time Field
Set Workflow Status	You can use this action to set a custom workflow status – AKA, instead of showing only "In Progress", "Complete", or "Error Occurred", you could specify a value that would better communicate the workflow's state.
Set Workflow Variable
Stop Workflow
LIST ACTIONS
Add List Item Permissions	This action gives you the ability to assign item level security permissions to the item
Check In Item
Check Out Item
Copy List Item
Create List Item
Declare Record	Used to declare an item/document as a record for Records management (may thereafter perform some archiving/routing action on the document)
Delete Item
Discard Check Out Item
Inherit List Item Parent Permissions	With this action you can set the permissions to inherit from its parent list or folder (first unique ancestor)
Remove List Item Permissions	This action clears all permissions set on this list item – no access for non-site collection admins
Replace List Item Permissions	This action deletes all the permissions on the item (or breaks inheritance) and assigned NEW permissions to that object.
Set Content Approval Status
Set Field in Current Item
Undeclare Record	See note on "Declare Record"
Update List Item
Wait for Field Change in Current Item
RELATIONAL ACTIONS
Lookup Manager of a User	This action will look at a user's profile and return that user's manager from within their profile
TASK ACTIONS
Assign a Form to a Group
Assign a To-do Item
Collect Data from a User
Utility Actions
Extract Substring from End of String	Replacing "Build Dynamic String" from SPD 07
Extract Substring form Index of String	Replacing "Build Dynamic String" from SPD 07
Extract Substring form Start of String	Replacing "Build Dynamic String" from SPD 07
Extract Substring of String from Index with Length	Replacing "Build Dynamic String" from SPD 07
Find Interval Between Dates

Out of Box Conditions List for SharePoint Designer 2010

Highlighted Conditions are New for 2010

COMMON CONDITIONS
If any values equals value	Replaces compare any data source
If current item field equals value	Replaces compare any data source, but with current item preselected.
OTHER CONDITIONS
Check exact list item permissions	If specified users have EXACTLY these permissions (additional permissions NOT ok)
Check list item permissions	If specified users have these permissions (additional permissions ok)
Created by a specific person
Created in a specific date span
Modified by a specific person
Modified in a specific date span
Person is a valid SharePoint user	Is not anonymous?
Title field contains keywords	Parse title of item for sub string(s)

Leveraging Visio Graphics Services within SharePoint Designer 2010 Workflows

BENDER\pwicklund — Thu, 22 Oct 2009 07:44:47 GMT

A great new feature that comes with SharePoint 2010 is the ability to leverage Visio diagrams to show business data and/or workflow statuses. As you may have heard, you can create a SharePoint Workflow from within Visio 2010, and thereafter import that workflow into SharePoint designer. It's a pretty neat way to empower your business users to model their OWN process, and then hand them off to people who are more technical who can deploy them and do other dirty work.

Beyond this ease of use factor, there's another great advantage that comes with building workflows in Visio first. This other advantage is you can leverage that diagram to convey where in the process the workflow is currently executing. For example:

In SharePoint 2007, all you could do is "Log to history list":

Now this is a great way to log information, but the trouble is it takes a while to read and draw conclusions, as well as it is dependent on the individual building the workflow to actually log stuff – which one may forget or not know how to do. A cooler approach is to use a Visio 2010 diagram:

With this diagram, it is very intuitive to see both what the workflow is doing, as well as where in the process the workflow is currently executing. SWEEEEET!!!!

Continue reading to see how to import a Visio SharePoint Workflow into SharePoint Designer, and thereafter enable Visio Web Access on that workflow...

Leveraging Visio Web Access within SharePoint Workflows in 10 Easy Steps!

STEP 1) Build a Visio SharePoint Workflow. Build a visio workflow that maps to your business process. Mine is very simple: first logging to history list, then a condition, if "Yes", log something, and if "No", log something else. Then complete.

STEP 2) Click the "Check Diagram" ribbon button to validate that the workflow will properly import into SharePoint Designer:

STEP 3) Export the Visio diagram:

STEP 4) Import that Visio diagram into SharePoint Designer. Open your SharePoint site in Designer, click "Workflows", then click "Import from Visio":

Browse to the file you exported, specify a name for your workflow, and choose a deployment target (List, Reusable, etc)

STEP 5) Add specific logic into the imported workflow. Notice how my workflow created in Visio looks after being imported into SharePoint Designer:

I still have the 3 "Logs" activities, as well as the Condition activity. Now simply add the values you need:

STEP 6) Click Save, and re-open the workflow through the left navigation in SharePoint Designer.

Control "S"

Click "Workflows" on left navigation and double click the workflow you just created:

STEP 7) Check the "Show workflow visualization on status page" check box in the "Settings" box:

STEP 8) Publish the workflow and Verify the necessary features are active. Publish:

Under Site Actions, Site Settings, Manage Site Collection Features, verify the Visio Web Access feature is active:

Also necessary, verify the Visio Graphics Service is active in Central Administration:

STEP 9) Add the workflow to a list or library (List settings, Workflow Settings, Select the workflow, Next, Save)

STEP 10) Initiate a workflow instance, and view the status!

Notice you get a green arrow next to each activity that has completed:

Cheers!

Phil

SharePoint Groups or AD Groups: When to use Which?

BENDER\pwicklund — Wed, 21 Oct 2009 13:31:15 GMT

It is often stated that you ought to use Active Directory(AD) groups as much as possible, if not always. However, any seasoned SharePoint administrator will know that it is impossible to always use AD groups, and there often develops a blurry line between when to switch over to SharePoint groups. Another complicating factor is knowing when it is appropriate to simply add users individually to SharePoint objects without first adding them to a group. These "explicit" permissions can be hard to control.

Below is a decision tree I put together to know when to use which. Start at stage 1, and use what is suggested when you first answer "Yes". If the first 5 stages all come back as "No", just add the users individually. Hope it helps!

DECISION TREE FOR GROUP TYPES:

1 - If the group will contain more than 50 users:

If yes, an AD group is required.

2 - If the group needs to be leveraged across multiple Site Collections:

If yes, an AD group is required.

3 - If the group will be provisioned onto objects that have audit implications:

If yes, an AD group is required.

4 - If the group will be provisioned onto multiple objects within the same Site Collection:

If yes, a SharePoint group is required.

5 - If membership to the group requires approval by the Site Collection administrator (sensitive assignments):

If yes, a SharePoint group is required.

6 - Else, adding users to the objects individually is acceptable…

RATIONALE OF EACH STAGE

STAGE 1) If the group will contain more than 50 users, then AD Group

The milestone of 50 users is nothing set in stone, but it is important to remember that as group membership increases, so does maintenance. If you have a site collection administrator managing SharePoint groups with hundreds or thousands of users therein, that will undoubtedly consume large amounts of their time. It is a better practice to offload that maintenance onto an IT help desk of some sort, whose specialty is such activities and can commit to SLAs, etc.

STAGE 2) If the group needs to be leveraged across multiple site collections, then AD group

SharePoint groups never span a single site collection. Therefore, if a group of users needs to be given permissions within multiple site collections, SharePoint groups will not be an option. Rather, an AD group is required.

STAGE 3) If the group will be provisioned onto objects that have audit implications, then AD group

When dealing with SOX or HIPPA information, it is best to stick with AD groups because there are more third party reporting appliances that can be leveraged during an audit.

STAGE 4) If the group will be provisioned onto multiple objects within the same site collection, then SharePoint group

You never want to recreate the wheel. Why manage the same set of users in 10 different places? It is better to create a SharePoint group, even if it only has 5 users in it.

STAGE 5) If membership to a group requires approval

Built right into SharePoint, you can setup requests for group membership which can be approved or denied. If you have sensitive content in your site collection, you may want to leverage these approval capabilities because if people adds users individually to content, there is no notification or approval process that you can tap into.

STAGE 6) Else, adding users to the objects individually is acceptable…

If stages 1-5 come back as "No", there's no reason to not simply add the users individually without adding them to a group first.

Phil

Building an Event Handler and Custom Error Page in SharePoint 2010

BENDER\pwicklund — Wed, 21 Oct 2009 07:35:07 GMT

What's in this post:

How to build a Event Handler in SharePoint 2010 from scratch
How to leverage a custom error page when canceling an event

Example leveraged: This walkthrough builds an event handler that executes when a site is being deleted in a site collection. When such as action occurs, the handler cancels the action and redirects the user to a custom error page where it informs them that sites shouldn't be deleted, but rather they should be archived.

STEP 1) Create a new Visual Studio 2010 project. Use the Empty Project template and specify the .NET 3.5 framework:

STEP 2) Type the URL to the Site Collection you want to deploy your project to as well as specify you want to deploy as a full-trust solution:

STEP 3) In the newly created solution, open the Feature and the feature designer will appear. Change the Scope to Site. This will make it so the event handler will be deployed across the entire site collection:

STEP 4) Add the event handler to the project. Right click the project and choose Add, New Item…

Select the Event Handler item template:

Select which event you want the handler to listen for (for this demo, we're capturing the Site Deleting event under Web Events):

STEP 5) Add code to the event handler. Open the code file, and enter your logic. For example:

properties.Cancel = true;

properties.Status = SPEventReceiverStatus.CancelWithRedirectUrl;

properties.RedirectUrl = "/_layouts/CustomEventErrorHandler/CustomErrorPage.aspx"

In this example, the Site Deletion is terminated and the user is redirected to a custom error page. This is accomplished by specifying the Status property and assigning it to the CancelWithRedirectUrl enumeration within SPEventReceiverStates. Other options include:

SPEventReceiverStatus.CancelNoError, cancel action but don't raise an error to the user
SPEventReceiverStatus.CancelWithError, cancel action and show default error dialog box (default)
SPEventReceiverStatus.CancelWithRedirectUrl, cancel error and redirect user to custom error page. Note that a RedirectUrl MUST be specified
SPEventReceiverStatus.Continue, do not cancel the action, even if properties.Cancel is set to true…

To Setup the Custom Error Page, Continue… (otherwise Deploy)

STEP 6) Add new application page by right clicking the project, and choose Add, New Item. Select Application Page:

Notice it creates a Layouts "Mapped Folder" that gets packaged up in the Feature/Solution…

STEP 7) Add page verbiage and other logic. In my example, I add some language that describes to end users that they need to archive sites (through some external process) rather than delete them:

STEP 8) Deploy and test the new Feature. Right click the project, and click Deploy:

Note – this will automatically activate the feature on the Site collection specified in Step 2.

Now, attempt to delete a site within that Site Collection:

SO EASY!

Phil

TONS OF GREAT SHAREPOINT 2010 MUST READS

BENDER\pwicklund — Tue, 20 Oct 2009 20:17:53 GMT

It's only been two days, and there's already a wealth of SharePoint 2010 info out in the community. I've been trying to keep up – but it's HARD. Just tonight I've read through 40+ posts from my favorite SharePoint bloggers, all of which were posted after 9AM yesterday. Busy times…

Anyways, here are some highlights:

SharePoint SDK: http://tinyurl.com/yhu3b2o

New Event Handlers in SharePoint 2010

BENDER\pwicklund — Tue, 20 Oct 2009 07:55:52 GMT

With SharePoint 2010, there is now a new host of event handlers that Developers can leverage to interject custom code into their sites when end users perform various actions. To be precise, there are 12 new event handlers available. Notice the chart below, highlighting what is new:

List Events

A field was added

A field is being added

A field was removed

A field is being removed

A field was updated

A field is being updated

A list is being added

A list is being deleted

A list was added

A list was deleted

List Item Events

An item is being added

An item is being updated

An item is being deleted

An item is being checked in

An item is being checked out

An item is being unchecked out

An attachment is being added to the item

An attachment is being removed from the item

A file is being moved

An item was added

An item was updated

An item was deleted

An item was checked in

An item was checked out

An item was unchecked out

An attachment was added to the item

An attachment was removed from the item

A file was moved

A file was converted

The list received a context event

List Workflow Events

A workflow is starting

A workflow was started

A workflow was postponed

A workflow was completed

List Email Events

The list received an e-mail message

Feature Events

A feature was activated

A feature is deactivating

A feature was installed

A feature is being upgraded

Web Events

A site collection is being deleted

A site is being deleted

A site is being moved

A site is being provisioned

A site collection was deleted

A site was deleted

A site was moved

A site was provisioned

Of particular interest is the site provisioning event handlers. I believe this greatly opens the doors for corporations to interject their custom site approval or request workflows into SharePoint, and the obvious, run some custom code on a site after it has been provisioned. Notice that now you are no longer depending on "feature stapling" to execute code on a site after it is provisioned. You can now just attach this web event.

If you recall, feature stapling was/is the action of editing the ONET.xml file within a site definition, adding features to the "WebFeatures" element which would auto-activate features upon provisioning. People would use that functionality to execute code upon site provisioning via a feature activating/ed event receiver, but that is now no longer necessary. Much simpler with this new event!!

Another great improvement to event handlers in SharePoint 2010 is with the improvements to Visual Studio 2010, and what it takes to create them. Notice, when you add a new item into a Visual Studio project, three is an Event Receiver template you can choose from:

When you choose that template, you get a dialog box allowing you to choose what event you want to capture, as well as what content type you want to associate the event receiver with:

After you click finish it will stub out all the code for you! Very slick!

Also notice how Visual Studio 2010 will also stub out all the necessary features and Solution Packages necessary to deploy into SharePoint. Literally all you have to do is hit F5, and then navigate into SharePoint and unit test your event receiver. SO COOL:

It is really great to see Microsoft place such a significant effort on enabling Developers to customize the product, as well as make it so easy to do so (which is so easily seen with their improvements with Visual Studio 2010). Thanks MS!

Phil

How to Enable the Developer Dashboard in SharePoint 2010

BENDER\pwicklund — Mon, 19 Oct 2009 13:00:20 GMT

What is the developer dashboard you may say? Well – the developer dashboard in SharePoint gives developers the ability to monitor how well their code base is performing – on a page by page basis. For instance – when enabled, at the bottom of every page you'll see a report of all the custom code that has ran on that page, as well as how long it took to run. This becomes very valuable information especially when querying SharePoint content. You may have several web parts on one page all querying information from across your Farm, and the SharePoint developer dashboard helps you know how well each performs, which can help you identify if one is becoming a bottle neck for your whole page.

Notice this example (the report always shows at the bottom of the master page):

The report shows the following information:

What controls loaded and how long each took to load
What specific database queries executed and the execution time of each
Events that were fired during the page load
Order of the page lifecycle and time during each stage

How to Programmatically Activate the SharePoint Developer Dashboard

Via Command Prompt

Create a new console application visual studio project, and in Program.cs, add the following code:

SPPerformanceMonitor perfmon = SPFarm.Local.PerformanceMonitor;
perfmon.DeveloperDashboardLevel = SPPerformanceMonitoringLevel.On;
perfmon.Update();
Ensure that .NET version 3.5 is specified (SP 2010 is not yet .NET 4.0 compatible)
Also – in project properties Build tab, ensure "Any CPU" is specified (defaults to x86, but SharePoint 2010 is x64 only)
Build, Execute, and Enjoy!

Via Power Shell

$snapin = Get-PSSnapin | Where-Object {$_.Name -eq 'Microsoft.SharePoint.Powershell'}
if ($snapin -eq $null) {

Write-Host "Loading SharePoint Powershell Snapin"
Add-PSSnapin "Microsoft.SharePoint.Powershell"

}
$farm = Get-SPFarm
$perfmon = $farm.PerformanceMonitor
$level = [Microsoft.SharePoint.Administration.SPPerformanceMonitoringLevel]::On
$perfmon.DeveloperDashboardLevel = $level
$perfmon.Update();
Write-Host "Sucess"

Cheers!

Phil

Visio Graphics Services Dashboards against SharePoint Data

BENDER\pwicklund — Mon, 19 Oct 2009 09:06:34 GMT

Have a bunch of Visio diagrams floating around your IT department, showing network configurations and/or server configuration? Well – now is the time to bring those Visio diagrams to LIFE!

With SharePoint 2010 Visio Graphic Services, you can tie your Visio diagrams into backend data, and then render that diagram over the browser within a SharePoint site. This is a great way to build IT dashboards of server performance or other statuses. Notice the example below:

Now this is obviously a very generic example – but you'll notice that this SharePoint site has a Visio Web Access web part within it that is rendering a Visio diagram showing server performance. What makes this really compelling is the data within the diagram is not hard coded, but is rather pulling it out of a backend data source – in this case a SharePoint list. Keep reading to see how I went about building this dashboard…

Steps to Create a Visio Graphics Services Dashboard in SharePoint

Start with your Data Source. I just created a quick SharePoint list that contains my data. This could be a SQL table, Access database, web service, etc. In my case it would be easy to have a process that every few minutes could update this list, or you could manually update it. Whatever works best for you.

Notice I created a custom list with four columns, Server Name, CPU, Memory, and Network Util. These are just a few basic server metrics to the sake of my walkthrough. Replicate something similar:

Now that you have a data source, create a new Visio 2010 diagram. In my case I used the Enterprise Application Visio template:

Once the new diagram loads, click Link Data to Shapes:

Choose your data source location. In my case this is a Microsoft Windows SharePoint Services list:

Type the URL to your SharePoint site:

And specify the SharePoint list that contains your data:

Click Finish:

After you setup the connection, you'll notice your SharePoint list data at the bottom of the diagram:

Click on a row, and Drag and Drop the row onto the diagram surface:

The next thing we need to do is customize what data we want rendered, as well as setup some charts. Right click on one of the server diagrams and choose Edit Data Graphic:

Within this Edit dialog, you can customize what fields in the SharePoint list to render, where you want them rendered (Position), as well as rendering format (chart, text, font, color, etc). In my case I changed the "Name" field to my CPU field:

Then I changed the Displayed As drop down to speedometer:

Click ok to unit test your changes. Notice it pulls the data from the SharePoint list:

To add more columns, Edit the Data Graphic again and click the New Item button. Specify the field in the SharePoint list, as well as your rendering preferences:

Notice you can also specify the data elements position around the object:

Lastly, you can add a Legend if you wish:

When you're done configuring you diagram and you're ready to publish the diagram into SharePoint, click the Blue tab:

On the Home page, click Share and then Publish to Visio Services:

Click Save As, and notice the file type is "Web Drawing" with a vdw extension. Vsd extensions won't work, so make sure you publish the web drawing format and not Visio diagram format:

First, upload that VDW file into a document library in SharePoint. Next, find a SharePoint page you want to add the Visio Graphics Services web part onto:

Once you get the web part on the page, open the tool pane and browse out to the document library you uploaded the Visio diagram into:

DONE!

Phil

Speaking at the October Cloud Computing User Group

BENDER\pwicklund — Tue, 13 Oct 2009 18:35:00 GMT

My blog has been a little quiet lately… actually, I've been biting my tongue because I'm feverishly ramping up on SharePoint 2010 and can't publically post stuff yet (for 6 more days!). "Investigation" outside of my 9 to 5 makes for slow posting J.

But anyways, this post serves as an FYI that I will be speaking at the upcoming Cloud Computing User Group in the Twin Cities. My talk is on how to integrate SharePoint with windows Azure to create highly flexible and scalable applications in the cloud. Specifically, I'm going to show how you can extend SharePoint online services with custom code, hosted in Azure. My demo will cover how to write a "event handler" that can listen to document library modifications and make necessary changes.

There are two other presentations/presenters as well. Check out http://tccloud.com to find out more.

Time: October 29, 2009 from 8:15am to 10:30am
Location: Microsoft Office - Bloomington
Street: 8300 Norman Center Drive, Suite 950
City/Town: Bloomington, MN 55437
Website or Map: http://www.bing.com/maps/de...
Phone: 952-404-2676
Event Type: meeting
Organized By: RBA Consulting
Latest Activity: 3 hours ago

Key Presenters and Topics:
Bradley Dupay - Learn more about Microsoft Online Services future roadmap and how it can give your business powerful productivity capabilities.

Phil Wicklund - Learn about integrating SharePoint Online Services with Windows Azure to create highly flexible and scalable applications in the cloud.

Adam Grocholsk - Learn how you can get involved to build a custom cloud based application that integrates with Microsoft Exchanged Online Services.

Speaking at The Experts Conference 2010

BENDER\pwicklund — Sat, 26 Sep 2009 18:16:00 GMT

Exciting news! Next April I'll be presenting two sessions at the acclaimed The Experts Conference! This conference features tracks across Active Directory, Exchange Server, and SharePoint Server. The conference specializes in 400 level tracks – so if you're looking to go deep into some advanced training, it shouldn't disappoint!

Check it out: http://www.tec2010.com/

And here are the sessions I'll be giving:

Building the Next Generation of SharePoint Web Parts – How to Leverage JQuery and Silverlight within your SharePoint Sites!

Simple, static pages are a thing of the past – today's standard is becoming rich in usability and graphical charm. Come learn how to leverage JQuery and/or Silverlight so you can really "light up" your SharePoint sites!

Leveraging InfoPath forms in your custom Visual Studio SharePoint Workflows

Visual Studio workflows and InfoPath Forms Services are a powerful team for your company's business processes. Three examples of how you can leverage InfoPath within your custom Visual Studio workflows will be demonstrated. 1: how to deploy a workflow enabled form into a form library programmatically. 2: how to programmatically retrieve form data entered by a user. 3: how to leverage an InfoPath form to collect custom workflow initiation data and task edit data.

See you there!

Phil

SharePoint Happenings

Speaking at SharePoint Saturday San Antonio!

5 Traits of a Virtuoso Business Analyst

5 Traits of a Virtuoso BA:

Changing a Document in SharePoint Over HTTP Programmatically

Option 1) Leveraging the SharePoint API and specifically the SPFile Object (AGAIN)

Option 2) Leveraging the SharePoint Web Services

Option 3) Keep it simple with HTTP

Presentation Slides & Source: SharePoint and Azure Integration

InLine List Item Editing with SharePoint 2010

New Conditions and Actions for SharePoint Designer 2010 Workflows

Out of Box Actions List for SharePoint Designer 2010:

Out of Box Conditions List for SharePoint Designer 2010

Leveraging Visio Graphics Services within SharePoint Designer 2010 Workflows

Leveraging Visio Web Access within SharePoint Workflows in 10 Easy Steps!

SharePoint Groups or AD Groups: When to use Which?

DECISION TREE FOR GROUP TYPES:

1 - If the group will contain more than 50 users:

2 - If the group needs to be leveraged across multiple Site Collections:

3 - If the group will be provisioned onto objects that have audit implications:

4 - If the group will be provisioned onto multiple objects within the same Site Collection:

5 - If membership to the group requires approval by the Site Collection administrator (sensitive assignments):

6 - Else, adding users to the objects individually is acceptable…

RATIONALE OF EACH STAGE

Building an Event Handler and Custom Error Page in SharePoint 2010

To Setup the Custom Error Page, Continue… (otherwise Deploy)

TONS OF GREAT SHAREPOINT 2010 MUST READS

Recent SharePoint Team Blog-ings

PowerShell

"Services" Architecture

Enterprise "Readiness"

Enterprise/Web Content Management

SharePoint Designer

SharePoint Development

Search

MySites and Social Networking

Project Server

Competitors (eg. Lotus Notes)

New Event Handlers in SharePoint 2010

List Events

List Item Events

List Workflow Events

List Email Events

Feature Events

Web Events

How to Enable the Developer Dashboard in SharePoint 2010

How to Programmatically Activate the SharePoint Developer Dashboard

Via Command Prompt

Via Power Shell

Visio Graphics Services Dashboards against SharePoint Data

Steps to Create a Visio Graphics Services Dashboard in SharePoint

Speaking at the October Cloud Computing User Group

Speaking at The Experts Conference 2010