SharePoint Development Blog by Jeremy Thake in Perth, Australia - Solution Development in SharePoint 2007 Part 3

Solution Development in SharePoint 2007 Part 3

June 4, 2008

Part 1 - Part 2 - Part 3 - Part 4 - Part 5 - Part 6 - Part 7 - Part 8

As promised I've uploaded the 3^rd webcast to show how Chapter 3 is implemented. I've also posted the sample code below for you guys to pick and chose as you please. Click here to watch the webcast (NEW 32MB swf - 40mins) .

The .zip of the solution can be downloaded here.

Site Collection Feature.xml

<?xml version="1.0" encoding="utf-8"?>

<Feature

Id="AE49F2FB-1B45-483A-A8C4-DFD698780ACA"

Title="A sample feature: jeremythake.tvshowschedule"

Description="This SharePoint solution was created by the STSDEV utility (http://codeplex.com/stsdev)"

Version="1.0.0.0"

Scope="Site"

Hidden="false"

ImageUrl="jeremythake.tvshowschedule\AfricanPith32.gif"

ReceiverAssembly="jeremythake.tvshowschedule, Version=1.0.0.0, Culture=neutral, PublicKeyToken=8eb9a930004f2f1a"

ReceiverClass="jeremythake.tvshowschedule.FeatureReceiver" xmlns="http://schemas.microsoft.com/sharepoint/">

<ElementManifest

Location="elements.xml" />

<ElementManifest

Location="schedule\listdefinition.xml" />

</ElementManifests>

</Feature>

Things to note:

I manually added the <ElementFile>'s for the ListTemplate generated by Solution generator.
I also added the <ElementManifest> for the ListTemplate also

Site Collection Elements.xml

<?xml version="1.0" encoding="utf-8"?>

</Field>

</Field>

</Field>

</FieldRefs>

</ContentType>

</Elements>

Things to note:

This was a simple case of adding the <Field>'s and <ContentType> generated from the Feature Generator application

Site Collection ListDefinition.xml

<?xml version="1.0" encoding="utf-8"?>

</Elements>

Things to note:

This was a auto generated by the Solution Generator tool (with VSeWSS)

Site Collection Schema.xml

<?xml version="1.0" encoding="utf-8"?>
<List Name="Schedule" Title="Schedule" Description="" Direction="0" BaseType="0" Url="Lists/Schedule" FolderCreation="FALSE" EnableContentTypes="TRUE" Type="100" Id="ebc1f1f6-5f70-4771-ab22-608c6e0ae005" xmlns="http://schemas.microsoft.com/sharepoint/">

<Views>

...

</Views>

</Fields>

...

</Fields>

</ContentTypes>

<Forms>

</Forms>

</MetaData>

</List>

Things to note:

This was a auto generated by the Solution Generator tool (with VSeWSS)
Had to delete <ContentType> and add <ContentTypeRef>

Web Feature.xml

<?xml version="1.0" encoding="utf-8"?>

<Feature

Id="5FF56A65-A901-4C4B-AFA8-BA721C98712B"

Title="A sample feature: jeremythake.tvshowscheduleweb"

Description="This SharePoint solution was created by the STSDEV utility (http://codeplex.com/stsdev)"

Version="1.0.0.0"

Scope="Web"

Hidden="false"

ImageUrl="jeremythake.tvshowschedule\AfricanPith32.gif"

ReceiverAssembly="jeremythake.tvshowschedule, Version=1.0.0.0, Culture=neutral, PublicKeyToken=8eb9a930004f2f1a"

ReceiverClass="jeremythake.tvshowschedule.WebFeatureReceiver" xmlns="http://schemas.microsoft.com/sharepoint/">

<ElementManifest

Location="elements.xml" />

</ElementManifests>

</Feature>

Web Elements.xml

<?xml version="1.0" encoding="utf-8"?>

<ListInstance

Title="Schedule"

FeatureId="AE49F2FB-1B45-483A-A8C4-DFD698780ACA"

OnQuickLaunch="TRUE"

TemplateType="100"

Url="Schedule" />

</Elements>

Things to note:

This was manually written and they're all pretty similar. The intellisense with VSeWSS will make this easier.

Web FeatureReceiver.cs

using System;

using System.Web;

using System.Web.UI;

using System.Web.UI.WebControls;

using System.Web.UI.WebControls.WebParts;

using Microsoft.SharePoint;

using Microsoft.SharePoint.WebControls;

using Microsoft.SharePoint.WebPartPages;

using Microsoft.SharePoint.Navigation;

using Microsoft.SharePoint.Administration;

using System.Globalization;

using Microsoft.SharePoint.Publishing.WebControls;

namespace jeremythake.tvshowschedule {

public class WebFeatureReceiver : SPFeatureReceiver {

public override void FeatureActivated(SPFeatureReceiverProperties properties) {

//Add CQWP

using (SPSite site = new SPSite("http://jt-asuslaptop/"))

{

using (SPWeb web = site.AllWebs["Test"])

{

SPFile file = web.GetFile(web.Url + "/default.aspx");

SPLimitedWebPartManager webpartsMng = file.GetLimitedWebPartManager(PersonalizationScope.User);

ContentByQueryWebPart contentByQueryWebPart = new ContentByQueryWebPart();

contentByQueryWebPart.Title = "Schedule";

contentByQueryWebPart.WebUrl = web.Url;

SPListTemplateCollection listTemplates = web.Site.RootWeb.ListTemplates;

SPListTemplate template = listTemplates["Schedule"];

contentByQueryWebPart.BaseType = string.Empty;

contentByQueryWebPart.ServerTemplate = Convert.ToString((int)template.Type, CultureInfo.InvariantCulture);

contentByQueryWebPart.CommonViewFields = "Air_x0020_Date,AirDate;Episode_x0020_Number,Episode;Season_x0020_Number,Season";

contentByQueryWebPart.ItemStyle = "ScheduleStyle";

webpartsMng.AddWebPart(contentByQueryWebPart, "Right", 0);

}

public override void FeatureDeactivating(SPFeatureReceiverProperties properties) {

/* no op */

}

public override void FeatureInstalled(SPFeatureReceiverProperties properties) {

/* no op */

}

public override void FeatureUninstalling(SPFeatureReceiverProperties properties) {

/* no op */

}

Things to note:

This was manually written. But you can use this as a start and modify it from here. I'll be writing more complicated ones in future posts.

Comments

Wednesday, 4 Jun 2008 10:58 by Rich Finn
Out of curiousity, are you adding the CQWP to the default page of the web you're activating the Feature on? If so, you can retreive the SPWeb object by using the properties param on the FeatureActivated method like 'SPWeb currentWeb = properties.Feature.Parent as SPWeb;'. The properties.Feature.Parent object will always be the item to which the Feature is scoped to... Good series of posts, btw... -Rich

Wednesday, 12 Nov 2008 07:40 by Gabriel Jones
a7n3w1kblwksjyn0