Intoduction to SharePoint 2010 for Developers

This webinar is also available on the DevExpress Channel.

SharePoint 2010 Data Access

This webinar is also available on the DevExpress Channel.

Andrew was also kind enough to publish a wrap-up blog post with links to additional references.

Real World SharePoint 2010

I never got around to buying Real World SharePoint 2007: Indispensable Experiences From 16 MOSS and WSS MVPs (Programmer to Programmer) but, I did get a chance to glance through the book and there was some great material. Today, I found out that Real World SharePoint 2010: Indispensable Experiences from 22 MVPs is going to be available on November 23, 2010.

Of course, I just pre-ordered my copy.

In a MOSS 2007 installation we have a site with a wiki library. The wiki library has been customized a bit with event handlers to do some fancy automatic permission assignments to individual wiki pages and prevent some users from approving wiki pages that they are not allowed to. This was done so that every user is able to add, read, edit wiki pages but let individual identified users handle the approval of the pages in a large wiki library. These details are probably inconsequential.

The real problem is there is a single user who can can read, add, and edit wiki pages. He is also assigned to approve some wiki pages. However, when he attempts to view the history of a wiki page for approval he gets an access denied error. The history page for a wiki page in a wiki library is an application page (in _layouts directory) with the following path: http://<path to sharepoint site>/_layouts/VersionDiff.aspx?ListID=<my wiki library id>&ID=<id for the wiki page>&Source=<return path>

The user also experiences this error when clicking the link to view incoming links. The path for this page is: http://<path to sharepoint site>/_layouts/BackLinks.aspx?ListID=<my wiki library id>&ID=<id for the wiki page>

This user has the following permissions being applied:

• Site Permissions – Limited Access
• List Permissions – Limited Access
• Item Permissions – Design

This user is also part of a domain group which has the following permissions being applied:

• Site Permissions – Limited Access
• List Permissions – Contribute
• Item Permissions – Contribute

Solution

I started a thread in the TechNet SharePoint forum in hopes of finding someone who has run into this problem before. Thanks to the folks in the forums, there were a few suggestions on how to resolve the problem. Unfortunately, I didn’t have the opportunity to try most of these. But here are the suggestions:

• Delete the user from the SharePoint site and re-add the user and re-apply permissions.
• Recreate the AD account
• Assign a higher level privillege to a parent object (This is the band aid that I applied which resolved the problem)

Essentially, the solution is to wrap the SiteActions control with a SPSecurityTrimmedControl in the master page. The only trick to this is identifying the appropriate permission string to use for the control so you do not remove the menu from users who will actually need to use it. The string can easly be composed after reviewing the set of users (or a group of users) who will need access and checking the rights associated permission levels granted those users (or group).

Important details to note are:

• FeatureId (optional): This is the ID of the feature in which the list template is defined
• BaseType (required): Specifies the base type, or default schema, for lists created using this template. See the table below for the 5 possibilities.
• Type: this is the template type on which the new list template is based. Se the table below for all base types of standard SharePoint list templates.
• DisplayName: the display name of the list template.

More details can be found in André Vala’s post.

The following table lists the 5 base types:

Base Type	Description
0	Generic List
1	Document Library
3	Discussion List
4	Survey
5	Issue List

The following table lists all available list templates with their template type id and their corresponding feature id:

Type of list	TemplateId	FeatureId
Generic List	100	00BFEA71-DE22-43B2-A848-C05709900100
Document Library	101	00BFEA71-E717-4E80-AA17-D0C71B360101
Survey	102	00BFEA71-EB8A-40B1-80C7-506BE7590102
Links List	103	00BFEA71-2062-426C-90BF-714C59600103
Announcements List	104	00BFEA71-D1CE-42de-9C63-A44004CE0104
Contacts List	105	00BFEA71-7E6D-4186-9BA8-C047AC750105
Events List	106	00BFEA71-EC85-4903-972D-EBE475780106
Tasks List	107	00BFEA71-A83E-497E-9BA0-7A5C597D0107
Discussion List	108	00BFEA71-6A49-43FA-B535-D15C05500108
Picture Library	109	00BFEA71-52D4-45B3-B544-B1C71B620109
Data Sources	110	00BFEA71-F381-423D-B9D1-DA7A54C50110
Site template gallery	111
User Information List	112
Web Part gallery	113
List Template gallery	114
XML Form Library	115	00BFEA71-1E1D-4562-B56A-F05371BB0115
Master Pages gallery	116
No-Code Workflows	117	00BFEA71-F600-43F6-A895-40C0DE7B0117
Custom Workflow Process	118	00BFEA71-2D77-4A75-9FCA-76516689E21A
Wiki Page Library	119	00BFEA71-C796-4402-9F2F-0EB9A6E71B18
Grid List	120	00BFEA71-3A1D-41D3-A0EE-651D11570120
Data Connection Library	130	00BFEA71-DBD7-4F72-B8CB-DA7AC0440130
Workflow History	140	00BFEA71-4EA5-48D4-A4AD-305CF7030140
Gantt Task List	150	00BFEA71-513D-4CA0-96C2-6A47775C0119
Meeting Series List	200
Meeting Agenda List	201
Meeting Attendees List	202
Meeting Decision List	204
Meeting Objectives List	207
Meeting Things to Bring List	211
Meeting Workspace Pages List	212
Blog Posts List	301
Blog Comments List	302
Blog Categories List	303
Status Indicator (KPI) List	432	7ED6CD55-B479-4EB7-A529-E99A24C10BD3
Report Library	433	6E53DD27-98F2-4AE5-85A0-E9A8EF4AA6DF
Publishing Pages Library	850
Issue Tracking List	1100	00BFEA71-5932-4F9C-AD71-1557E5751100
Administrator Tasks List	1200
Translation Management Library	1300	29D85C25-170C-4df9-A641-12DB0B9D4130
Translation List	1301	29D85C25-170C-4df9-A641-12DB0B9D4130
Slide Library	2100

0BE49FE9-9BC9-409d-ABF9-702753BD878D

• SharePoint jQuery Deployment Feature
• SharePoint + jQuery = Stay Here Feature
• SharePoint Slideshow Web Part

After figuring out how to package jCarousel and jQuery using SharePoint delegate controls, I was ready for business with the implementation of the web part.

The web part itself was nothing fancy. I used a Repeater control to generate the list item (LI) elements with the content I needed in the carousel. I wrapped the Repeater in an unordered list (UL) which was wrapped in a DIV tag that had the runat attribute set to server. So basically, I just followed the mark up instructions provided in the jCarousel documentation.

The wrapping DIV tag was used in my webpart code to initialize jCarousel. The code snippet below shows how I implemented it:

protected override void OnLoad(EventArgs e)
{
  if (!Page.ClientScript.IsStartupScriptRegistered(this.GetType(), this.ClientID))
  {
    Page.ClientScript.RegisterStartupScript(this.GetType(), this.ClientID, @"
      <script type=""text/javascript"">
        jQuery(document).ready(function() {
          jQuery('#" + carouselDiv.ClientID + @"').jcarousel({
            // Configuration goes here
            vertical: true,
            scroll: 2,
            visible: 4
          });
        });
      </script>
    ");
  }
}

SP2 for WSS 3.0: http://www.microsoft.com/downloads/details.aspx?FamilyId=79BADA82-C13F-44C1-BDC1-D0447337051B&displaylang=en

SP2 for MOSS 2007: http://www.microsoft.com/downloads/details.aspx?FamilyId=B7816D90-5FC6-4347-89B0-A80DEB27A082&displaylang=en

I love finding a good and useful blog post and this morning I did just that. The post from Joel Oleson regading SharePoint test driven development is great. It has a quick exerpt from his twitter conversation with other SharePoint pros regarding this topic, a summary of what he learned, and list of useful resources with descriptions. If you follow or practice test driven development (TDD) and are involved with SharePoint development, then this post will be a good resource for you too.

So… if the debate is not new, what’s all the fuss about?

Regardless of the stance that you take about allowing SPD to be used in a production SharePoint deployment or not, the real cause of concern is how SPD can impact production environment when used by untrained/uninformed users with appropriate rights. This reminds me of the quote – with great power comes great responsibility… or something like that. I don’t see the need for huge concern. That is assuming people with those rights have already been trained and informed. For the most part, people with contributor or higher permission role assignments can already do plenty of damage to a production environment with only the web browser at hand. Hence, the need and argument for appropriate training, content approval (and publishing) planning and enforcement, and governance plans (especially in Extranet/Internet facing deployments).

Okay… so what should we do?

There shouldn’t be too much to do (assuming training, content approval, governance, etc. has already been addressed). Professionally, I will be making sure to emphasize the role of SPD in SharePoint projects. I will also make sure to encourage the inclusion or addition of SPD training for existing and new SharePoint users (especially “power” users), administrators, and developers.