GEMSolution Blog

Displaying a User field in a Content Query Web part (CQWP)

2011-09-28T18:18:00.000+01:00

Well it has been a little while since i have posted but hopefully now i will pick up where i left off with the addition of the SharePoint 2010 world too.

I have been working on a 2007 environment recently and in particular a content query web part which is being used to display document information across an entire site collection based on a hierarchy of content types, so i set about the normal method of adding the CQWP to a page, exporting it, customising, adding in the custom xsl (ItemStyle, ContentQueryMain and Header) and then uploading to the webpart gallery and adding to a page.

All pretty easy stuff really…………….well.

A problem came about when i tried adding in a Site Column called “Document Owner” which was of type User. I went about adding in the column to the CommonViewFields section of the .webpart, adding in a reference to Document_x0020_Owner,User;. This caused the webpart to throw an error and fail completely. I then searched many forums and blogs and tried a multitude of “solutions” including setting CommonViewFields reference to Document_x0020_Owner,Text; also trying the viewfieldsoverride property which turned out to be too restrictive, and nothing worked for me.

After some more frustrating investigation and trials and errors, the answer as unbelievably simple. Omit the identifier from the CommonViewFields property so it only looks like this.

<property name="CommonViewFields" type="string">Document_x0020_Owner;</property>

I also put in an entry into the DataColumnRenames property too, like so to make it easier to pick up in the xsl

<property name="DataColumnRenames" type="string">Document_x0020_Owner,DocumentOwner;</property>

then in your ItemStyle.xsl file, make reference to this field as follows (I setup a variable to achieve this), this removes the ID from the output which normally appears as 1;#morgan,gavin

<xsl:variable name="DocumentOwner">
<xsl:value-of select="substring-after@DocumentOwner, ';#')" /></xsl:variable>

<xsl:value-of select="$DocumentOwner" />

Hope that saves some others pain…….

SharePoint Designer 2007 workflow SendEmail notification failed for SharePoint Groups

2010-05-13T09:04:00.000+01:00

Came across a problem the other day where i had a SharePoint Designer workflow which sent a notification out to a SharePoint Group but failed. The workflow was fine sending out notifications to individuals, it just wouldn’t send out to a group, it would report an error “The e-mail message cannot be sent. Make sure the outgoing e-mail settings for the server are configured correctly” which is a bit of a red herring as there is nothing wrong with the email settings.

After a bit of digging around, i found the following fixes which resolved the issue. It was actually to do with some of the permissions of the group I was using to send the email to, so you need to amend some of the settings on the group.

Firstly, Navigate to the site in question, click on Site Actions -> Site Settings -> People and Groups. Select the group that you are using to send the email to from the left navigation. Then click on Settings -> Group Settings.

Secondly, make sure that the group that you are using to send an email to has at least “Read” permissions on the Site where you created your SharePoint designer workflow.

Finally, within the Group settings section, make sure that “Everyone” can view the membership of the group.

hope that helps a few people out….

Recurring Meeting Workspace date picker JavaScript error

2010-04-22T09:40:00.000+01:00

If you have a custom master page on your meeting workspaces (replaced MWSDefault.master), then you may encounter a JavaScript error for selecting a data from the left navigation if you setup a recurring meeting for that workspace.

To fix this issue open the custom master page (in SharePoint Designer if need be) and insert the following line below all of the other Register Tags and before the HTML tag starts

<%@ Register Tagprefix="Meetings" Namespace="Microsoft.SharePoint.Meetings" Assembly="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>

next insert the following line directly below the <Body> tag.

<Meetings:PropertyBag runat="server"/>

After this publish your master page and all meeting workspaces should now work.

GEMSolution Blog has Switched to Google Blogger

2010-03-08T17:06:00.001Z

GEMSolution Blog “Share”….that’s the “Point” has now moved to Google’s Blogger tool.

I will shortly be uploading all historic blogs from the old blog site and putting a redirect in place on the old blog site so people are redirected here automatically.

Contains operator missing in Advance Search Web Part

2010-01-20T10:08:00.001Z

This is an old topic, and i know it has been covered by some other people, but it is one i keep having to rectify in various client environments, so thought i would give myself an easy reference point for it rather than keep trawling the web each time.

So you have added the advance search Web Part to a page and the only two options which exist in the operator drop down (see below) are “Equals” and “Does not equal”. So where has the “contains” and “does not contain” operator gone.

The explanation of why it has disappeared could be due to an MS infrastructure update to increase performance for search.

Well, to restore this follow the instructions below.

1. If the page is not already in Edit mode, click on Site Actions and then Edit Page.

2. On the Advanced Search Web Part click on the Edit and then Modify Shared Web Part

3. From the Web Part property section on the right, Scroll down to the properties section and then click on the … button next to the properties section

4. At the top of the Dialogue box, you may have one of 2 scenarios. Either the following appears

or there is no Element for the AllowOpContains. If you have the Element, then simply change the False value to True.

if you do not have the element at all paste the following directly inside the root element.

  1: <Option Name="AllowOpContains" Value="True"/>

It should then look like this.

5. Now click ok and then Apply or Ok on the Web Part properties panel, and check you have the options as shown below.

Happy New Year

2010-01-04T09:42:00.000Z

Just thought I'd send a quick post to wish everyone who reads my Blog a very Happy New Year. I am looking forward to an exciting 2010 with plenty of new technologies to dive into with SharePoint 2010 and Visual Studio 2010 at the top of my list.

Over the Christmas period i managed to get a SharePoint 2010 beta server up and running so i will be putting up some posts on my findings whilst playing around.

I Will also be looking into Visual Studio 2010 and how well it integrates and caters for SharePoint development.

Watch this space………..

Setting ModerationInformation.Status back to pending removes author/creator permissions

2009-11-13T08:26:00.001Z

Here’s the scenario – I have a visual studio sequential workflow on a list (not document library) which has a 2 stage approval process. The request was to use the standard OOB approve/reject mechanism rather than tasks, so for the first stage of approval, the approver would select Approve/Reject from a list item. Once the first stage approver approves the item, the item should NOT be approved and live, but still pending and an email sent to the 2nd level approver to make the ultimate decision of making the item live. Once the 2nd stage approver approves the item the item then becomes Approved and Published for all to see.
I created a Visual Studio Sequential Workflow and created separate routes through workflow based on who updated the List Item.

In code, if the item was approved by the 1st stage approver i would reset the ModerationInformation.Status back to pending, my code was simple and as follows;

1: this.workflowProperties.Item.ModerationInformation.Status = SPModerationStatusType.Pending;
2: this.workflowProperties.Item.Update();
3: 
4:

To troubleshoot this, i took to using Powershell and SharePoint Manager from codeplex to see what was happening to my list item. Throughout, the creator and author field was not changed from the person that created, yet as soon as i set the moderationinformation.status back to pending, the creator of the item lost ALL permissions to even view the item.

I had tried the following to rectify this but none worked;

I have tried all combinations of Update(), SystemUpdate(), SystemUpdate(false), SystemUpdate(true), UpdateOverwriteVersion() when saving the list item and none of them had any effect.
I tried to up the version number so that the version of the list item that was being approved and set back to pending was version 2.0 to ensure that the Creator/Author was preserved.

I have only found one way in which to rectify this problem and that is to re-assign the roledefinitionsbinding for that user to a level which allows them to edit/update the item again. I did this using the following code. Just one more thing, i had also disabledeventfiring in my workflow so i can be sure that events dont keep firing and updating the item. This is how i did that in code;

1: SPListItem currentItem = this.workflowProperties.Item;
2: //Get the Full Control Role Definition
3: SPRoleDefinitionCollection roleDefs = this.workflowProperties.Web.RoleDefinitions;
4: SPRoleDefinition roleFullControl = roleDefs["Full Control"];
5: //Get the current items role assignments
6: SPRoleAssignmentCollection rolesInList = currentItem.RoleAssignments;
7: //iterate through and find the creator users role assigment
8: foreach(SPRoleAssignment role in rolesInList)
9: {
10:   string createdByString = currentItem["Created By"].ToString();
11:   int indexOfSemiColon = createdByString.IndexOf(";");
12:   int createdById = Int32.Parse(createdByString.Substring(0, indexOfSemiColon));
13:   if(role.Member.ID == createdById)
14:   {
15:     try
16:     {
17:       //firstly remove any role bindings the add in whatever level you require
18:       role.RoleDefinitionBindings.RemoveAll();
19:       role.RoleDefinitionBingings.Add(roleFullControl);
20:       role.Update();
21:     }
22:     catch{}
23:   }
24: }

This solved my problem, but i am not saying this is the correct solution in all cases.

If anyone comes up with an answer as to why this happens, feel free to post a reply to this.

SPDisposeCheck Error workaround

2009-10-31T09:39:00.001Z

I use the very useful SPDisposeCheck tool to check my assemblies using the SharePoint API to make sure i have not left any SharePoint objects open which could cause potential memory leaks.
I encounter issues using the output to xml file “–xml” switch on the tool where it simply crashes at the point of “Processing Method Traces”. I am not sure if there is an updated version out there to fix this but should you want to get the output to a file rather than the command window, i use a workaround to which outputs (pipes) the command window to a file by using the > command, so your command should look something like this.
SPDisposeCheck “<mydllFileOrDirectory>” –debug >”<outputdirectory>outputtfile.txt”
Hope that helps if people want to save the output.

Finally got round to taking the 70-541 MCTS WSS 3.0 Developer Exam

2009-09-14T10:32:00.000+01:00

I finally got round to taking the 70-541 MCTS Microsoft Windows SharePoint Services 3.0 – Application Developer exam today and passed with a score of 895.

The exam content was pretty much what everyone out there is blogging about with some added questions which apparently do not contribute to your score in order for Microsoft to test out some new questions. Completed it in just over an hour.

Having worked with SharePoint since its Beta days back in October 2006, i didn't think it really tested or was a reflection on my real world experience of development within the WSS space.

I used the Inside Microsoft SharePoint Services 3.0 book (Ted Pattison), which i did find useful and then a number of Visual Cert Exams from various places out on the web. All pretty useful for passing the exam.

Fun with SPFieldUserValueCollection

2009-04-07T10:30:00.000+01:00

I have been searching around to see the various ways in which people are retrieving Users and Groups objects or the string value from relevant SPField object when retrieving ListItems from a SharePoint List, and I have found that there are quite a few blog posts on this subject, all with differing code and views.

Having now tested nearly all of them, i have used 2 approaches that have helped me and the are

Retreiving an SPUser or SPGroup object – perhaps for validation purposes or to gain other information about the user of group
Retrieving a User friendly string representation of the User or Group – perhaps for simple display purposes.

The code below show the retrieval of the SPUser/SPGroup objects

Code Snippet
 using (SPSite site = new SPSite("http://mysite.com/sitecollection"))
{
    using (SPWeb web = site.OpenWeb("mysitename"))
    {
        SPList oList = web.Lists["ListName"];
        SPListItemCollection oListItems = oList.Items;
        foreach (SPListItem oListItem in oListItems)
        {
            //Gets a collection of all the User and Group objects from the UserGroup Field
            SPFieldUserValueCollection oFieldUserValueCollection =
                new SPFieldUserValueCollection(web, oListItem["FieldName"].ToString());
 
            //Next, loop through the Values in the Collection
            foreach (SPFieldUserValue oFieldUserValue in oFieldUserValueCollection)
            {
                //now we need to test if the SPFieldUserValue is a
                //User or a  Group, because if we simply assign a user
                //we will get a Null Reference Exception if it is a Group
 
                //It is a Group
                if (oFieldUserValue.User == null)
                {
                    //Create and assign a new SPGroup object by using the
                    //Lookup value to return a Group from the current Site(SPWeb)
                    SPGroup oGroup = web.Groups.GetByID(oFieldUserValue.LookupId);
                }
                //It is a User
                else
                {
                    //Create and assign a new SPUSer object by using the User
                    //property of the SPFieldUserValue object
                    SPUser oUser = oFieldUserValue.User;
                }
            }
        }
    }
    
}
 

and the code below here shows the retrieval if the simple string representation.

Code Snippet
 SPList oList = web.Lists["ListName"];
SPListItemCollection oListItems = oList.Items;
foreach(SPListItem oListItem in oListItems)
{
    SPFieldUserValueCollection oFieldUserValueCollection
        = SPFieldUserValueCollection(web, oListItem["FieldName"].ToString());
 
     foreach(SPFieldUserValue oFieldUserValue in oFieldUserValueCollection)
    {
        //simply retrieve the string value from the SPFieldUserValue object
         string sFieldValue = oFieldUserValue.LookupValue;
    }
}
 

If anyone else has any more thoughts on this please let us know.

SPList.GetItems(SPQuery query) does not search recursively through sub folders in a List by default

2009-02-09T09:17:00.000Z

I developed a custom WebPart which allowed a user to select a list from a site and then execute an advanced search within the selected list. The advanced search functionality provided various options to select which fields to filter on, sort and display, using the SPField properties.

The search execution code was created using the SPList.GetItems(SPQuery query) search function.

Testing was going great until i came across a problem when searching on items in subfolders within a list, the test failed as No items in subfolders were returned.

I came across this in the SDK which wasn’t obvious to me, so thought I'd ease other people’s pains quickly if it isn’t obvious to you either.

There is a property called ViewAttributes on the SPQuery object which accepts a string value. The following code shows how to use the property to search recursively through subfolders

Code Snippet
 using (SPSite site = new SPSite("http://mysite.com/sitecollection"))
{
    using (SPWeb web = site.OpenWeb("mysitename"))
    {
        SPList list = web.Lists["mylist"];
        SPQuery query = new SPQuery();
        query.ViewAttributes = "Scope=\"Recursive\"";
        query.Query = string.Format("<Where><Eq><FieldRef Name={0} /><Value Type='{1}'>{2}</Value></Eq></Where>", "myfieldname", "text", "searchstring");
        SPListItemCollection itemsReturnedFromQuery = list.GetItems(query);
    }
}
 

Adding Groups and Users to a SharePoint Site in code

2008-09-02T08:40:00.000+01:00

There are plenty of blogs around about adding users to groups, but i have found there are not many explaining the end to end code for the creation of a new group in a site, assigning the permissions then adding of users to that group, so here goes.

Firstly, when you add a group to a site, it is not just the simple case of using the SPGroupCollection add method of the SPWeb object, you need to follow this up by setting the RoleAssignments and RoleDefinitionsBindings.

The code below is using an application page, therefore using the LayoutsPage context to get the SPWeb object using this.Web. If you are using this in a web part or other code, then you would wrap this inside a using(SPWeb) or a try catch scoped SPWeb object.

We start by checking to see if the site is inheriting its permissions and breaking if required. In this example, the existing inherited group permissions are copied across when breaking the inheritance by using the true parameter.

Code Snippet
 using (SPSite site = new SPSite("http://mysite.com/sitecollection"))
{
    using (SPWeb web = site.OpenWeb("mysitename"))
    {
        if (!web.HasUniqueRoleAssignments)
        {
            //use the true parameter to copy the permissions
            //when breaking inheritance
            web.BreakRoleInheritance(true);
        }
    }
}
 

Then we need to create the new group by adding in a site owner and default member. Note: this alone will not create the group in the site, the RoleAssignment and RoleDefinitions need to be added below.

Code Snippet
 PeopleEditor peApproversGroup;
using (SPSite site = new SPSite("http://mysite.com/sitecollection"))
{
    using (SPWeb web = site.OpenWeb("mysitename"))
    {
        if (!web.HasUniqueRoleAssignments)
        {
            //use the true parameter to copy the permissions
            //when breaking inheritance
            web.BreakRoleInheritance(true);
            //Create the group then get a Group Object reference to the created group
            web.SiteGroups.Add("Group Name", web.CurrentUser, web.CurrentUser, "Site Group Description");
            SPGroup newGroup = web.SiteGroups["Group Name"];
            //Set properties of the group settings
            newGroup.AllowMembersEditMembership = true;
            //Add in the role assignment and definition
            SPRoleAssignment roleAssignment = new SPRoleAssignment(newGroup);
            //Create object based on Approval role definition
            SPRoleDefinition roleDefinition = web.RoleDefinitions["Approve"];
            roleAssignment.RoleDefinitionBindings.Add(roleDefinition);
            //finally add the role assignment
            web.RoleAssignments.Add(roleAssignment);
            foreach (PickerEntity user in peApproversGroup.Entities) 
            { 
                SPUser userToAdd = web.SiteUsers[user.Key]; 
                newGroup.AddUser(userToAdd); 
            }
            newGroup.Update(); 
 
 
        }
    }
}
 

the group should be created, owner assigned and users added, hope this helps.

Create Calendar View filtering on Start Time/End Time

2008-08-07T08:38:00.000+01:00

There is a really annoying problem within the UI with Calendars whereby when you create a new view on a Calendar list it does not expose the Start Date or End Date to filter on so you cannot create a view for upcoming Events, or events between dates !

Here is a quick workaround to solve this issue.

Go into the calendar list settings and create a new column, give it a name, then make it a calculated column type and then select the [created] in the Formula box. Select DateTime from the data type and un-tick add to default view.

Now create a new view, and in the filter section, the new field will appear in the drop down and you can now filter on start date.

Retrieving values from SPField objects, not item.ToString()

2008-04-24T09:27:00.000+01:00

When providing interaction with lists, whether it be via List Event Handlers or Web Parts, it helps to use the casting methods for the fields that you are going to be interacting with when both retrieving and setting values.

The most widely used scenario where this feature is best used is in Lookup, Choice, URL and User Fields, as the actual value that is stored by accessing the ListItem["name"].toString() is not always what may be expected. Lookup Fields usually store values in this format, Id, #, ;, text. which can amount to returning "1#;Title", when you were expecting "Title", and SPUser fields store a userid followed by the name, e.g. 16#:GavinMorgan

Below is a piece of code using some of the more widely used field types which casts the field value retrieved to its native type where more information can be accessed.

Something else to note here is that we consistently use the internal field.GetByInternalFieldName method to retrieve the field which ensures we always use the internal field name rather than than the title, as this is subject to change.

This example is from and ItemAdded event handler.

Code Snippet
 SPListItem item = properties.ListItem;
//SPUser fields
SPFieldUser userField = item.Fields.GetFieldByInternalName("UserInternalFieldName") as SPFieldUser;
SPFieldUserValue userFieldValue = userField.GetFieldValue(item[userField.Title].ToString()) as SPFieldUserValue;
SPUser user = userFieldValue.User;
//Choice Fields
SPFieldChoice choiceField = item.Fields.GetFieldByInternalName("ChoiceInternalFieldName") as SPFieldChoice;
//To access the value
string selectedChoice = choiceField.GetFieldValueAsText(item[choiceField.Title]);
//To access list of choices in field
foreach (string choice in choiceField.Choices)
{
    if (choice == "choice 1")
    { 
        //do something with choices
    }
}
//To add a new choice
choiceField.Choices.Add("New Choice");
choiceField.Update();
//URL Fields
SPFieldUrl urlField = item.Fields.GetFieldByInternalName("URLInternalFieldName") as SPFieldUrl;
SPFieldUrlValue urlFieldValue = urlField.GetFieldValue(item[urlField.Title].ToString()) as SPFieldUrlValue;
string url = urlFieldValue.Url;
string desc = urlFieldValue.Description;
 

I will try to add more Field Types as i use them.

Accessing BeforeProperties and AfterProperties on List Item Event Handler

2008-03-20T08:07:00.000Z

I have had numerous occasions during event handler development where i have needed to access the BeforeProperties and AfterProperties of a list item which is being used to compare or retrieve values.

You can attack this by either accessing the property directly or looping through the HashTable collection of properties using the Key/Value pairing. The key thing to note here is that it is solely meta data you are returning, and there is no opportunity to cast to an SPField type.

Accessing Property Directly

Code Snippet
 string valueOfBeforeField = properties.BeforeProperties["fieldname"].ToString();
string valueOfAfterField = properties.AfterProperties["fieldname"].ToString();
 

Looping through property Collection

Code Snippet
 foreach(DictionaryEntry de in properties.AfterProperties)
{
    if(de.Key.ToString() == "fieldname")
    {
        string valueOfField1 = de.Value.ToString();
    }
}
 

Retrieving an SPUser object from an SPListItem

2008-02-19T17:30:00.000Z

Whilst coding a Timer Job I came across a requirement to extract the user's email address from a User Type column in a SharePoint list item. I must admit, naively I thought it would be as simple as casting the ListItem["user"] as SPUser, but to my surprise this produced a lovely error.

Finally after dredging through the SDK and other blogs/forums and my determination not to have to use the SPSite.AllUsers, I cam up with this solution which seems to work nicely

Simple and effective.

Code Snippet
 SPFieldUser userField = listItem.Fields.GetFieldByInternalName("InternalFieldName") as SPFieldUser;
SPFieldUserValue userFieldValues = listItem[userField.Title] as SPFieldUserValue;
SPUser userFromListItem = userFieldValues.User;
string userEmailAddress = userFromListItem.Email;
 

CAML Queries with DateTime values

2008-02-01T15:26:00.000Z

I came across an interesting problem whilst using the SPQuery object, CAML and DateTime Fields (at the time I was using them in a Timer Job, but it is not specific to that)

Firstly I found that if you have any problems with the CAML query,

the first you know about it is when you try to use the SPList object or SPLIstItemCollection objects on which you based the query.

The only error message you are likely to get is "Cannot complete this action, please retry"

One bit that they fail to tell you is that if you are using a DateTime in a CAML query and you are comparing lets say today's date against a Date field in your list, you need to include the property "IncludeTimeValue" and set it to TRUE on the "<Value>" element, so the XML looks like this

  1: <FieldRef Name="MyDate" />
  2: <Value Type="DateTime" IncludeTimeValue="TRUE"> 
  3: </Today> 
  4: </Value>

If you don’t use it then you will get the "Cannot complete this action" error when using the SPListItemCollection object.

Additionally, you need to bear in mind the following when using CAML from your C# code.

You need the internal names of your fields when using them in the CAML Code.

When using a both a string/choice/lookup field and a DateTime field in your query using the AND clause, you need 2 AND clauses in there.

Calculated Column using [Today]

2008-01-04T15:22:00.000Z

SharePoint has many niggling frustrations where you think functionality should be readily available, only to find that for some reason the Microsoft team have decided to make life a little harder and not include it. So more and more we find ourselves having to find yet another work around..

Here, SharePoint complains about including the [Today] field in a Calculated column. Thankfully there is a work around, and it seems as though we are tricking SharePoint with this one.

Create a new column in your list and call it "Today", for now just use a single line text and leave all defaults, click ok to save.
Now create your calculated column, and in your calculation, you can select the column created above, named "Today". so you may have a calculation which looks like the following. =DATEDIF([Created], [Today], "d") which will calculate the number of days between the created date and the current date. Click OK to save the column.
Now delete the column you created in section 1. Your calculation should now work.

You need to bear in mind that if you change the calculation and you are still using [Today] in the calculation, you will have to recreate the "Today" column as in step 1 as SharePoint will attempt to re-parse the calculation and complain about basing it on a [Today] field.

Disposing of SPSite and SPWeb Objects

2007-06-15T23:43:00.000+01:00

Wherever you use the SPWeb and SPSite objects, you must always dispose them after use. You can do this by either explicitly disposing of the by calling the dispose method, or encasing them in a "using" statement, "scope". .If you do not dispose of the objects then memory can quickly be consumed and eventually, dependent on the scale of your architecture, your environment will grind to a halt.

So how do we Dispose or Scope ? Bear in mind that both of these methods are as efficient as each other.

Dispose SPSite and SPWeb

There are 2 scenarios where you must be disposing of the SPSite and SPWeb objects. The first is a general assignment scenario, which is disposing of the SPSite and SPWeb objects directly. The second is the one that is usually missed and more critical in causing memory leaks which involves the use of the SPWeb object within a Foreach loop. both are documented below.

General dispose after use, I have been also enclosed this in a try, catch, finally statement to enable greater exception handling.

Code Snippet
 SPSite site = null;
SPWeb web = null;
try
{
    site = new SPSite("http://mysite.com/sitecollection");
    web = site.OpenWeb("mysitename");
 
    //other code here
}
finally
{
    web.Dispose();
    site.Dispose();
}
 

Disposing of SPWeb in foreach loop. the subWeb object in the code below is explicitly disposed of.

Code Snippet
 SPSite site = new SPSite("http://mysite.com/sitecollection");
SPWebCollection allWebs = site.AllWebs;
foreach (SPWeb web in allWebs)
{ 
    //other code here
    web.Dispose();
}
 
site.Dispose();
 

Scope SPSite and SPWeb

Within your assignment of the SPSite and SPWeb objects, encase them in a using statement. This will dispose of the objects once the scope of the code runs outside the using scope.

Code Snippet
 using (SPSite site = new SPSite("http://mysite.com/sitecollection"))
{
    using (SPWeb web = site.OpenWeb("mysitename"))
    { 
        //other code here
    }
}
 

if you use a foreach loop within the using statement, the subwebs will still have to be disposed of explicitly.

Welcome

2007-06-01T10:13:00.000+01:00

Welcome to the GEMSolution Blog Site.

This Blog will be geared towards the SharePoint development and customisation world, and the problems and fun that this brings to people's lives.

Please feel free to register and add posts to this blog site with your problems, questions and comments and hopefully this can build up to be another source of information for people venturing into the world of SharePoint.

happy SharePoint'ing