moopoo.net » SharePoint

Required Field Validation Group on PeopleEditor control

Matt — Wed, 09 Jun 2010 11:34:08 +0000

Very similar to my post on validation of the DateTimeControl, a PeopleEditor (people picker) control I was using was validating on each postback.
I created a required field validator with a ValidationGroup and to get the validator to look at the correct people editor field use the following code.

myRequiredFieldValidator.ControlToValidate = string.Format("{0}$downlevelTextBox", myPeopleEditor.ID);

Removing element from web.config on feature de-activation

Matt — Mon, 15 Mar 2010 11:18:09 +0000

public override void FeatureDeactivating(SPFeatureReceiverProperties properties) {
 
            SPSite site = (SPSite)properties.Feature.Parent;
 
            SPWebConfigModification controlsSection = new SPWebConfigModification("controls", "configuration/system.web/pages");
            controlsSection.Owner = "My.Menu";
            controlsSection.Sequence = 20;
            controlsSection.Type = SPWebConfigModification.SPWebConfigModificationType.EnsureSection;
            controlsSection.Value = "";
 
            SPWebConfigModification addElement = new SPWebConfigModification(
                @"add[@tagPrefix=""SharePoint""][@namespace=""My.Menu""][@assembly=""My.Menu, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd3368f0ff736bff""]", 
                "configuration/system.web/pages/controls");
            addElement.Owner = "My.Menu";
            addElement.Sequence = 40;
            addElement.Type = SPWebConfigModification.SPWebConfigModificationType.EnsureChildNode;
            addElement.Value = @""SharePoint"" namespace=""My.Menu"" assembly=""My.Menu, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd3368f0ff736bff"" />";
 
            site.WebApplication.WebConfigModifications.Remove(controlsSection);
            site.WebApplication.WebConfigModifications.Remove(addElement);
            site.WebApplication.Update();
            site.WebApplication.WebService.ApplyWebConfigModifications();
 
    }

Adding element to web.config on feature activation

Matt — Mon, 15 Mar 2010 11:16:17 +0000

public override void FeatureActivated(SPFeatureReceiverProperties properties) {
 
            SPSite site = (SPSite)properties.Feature.Parent;
 
            SPWebConfigModification controlsSection = new SPWebConfigModification("controls", "configuration/system.web/pages");
            controlsSection.Owner = "My.Menu";
            controlsSection.Sequence = 20;
            controlsSection.Type = SPWebConfigModification.SPWebConfigModificationType.EnsureSection;
            controlsSection.Value = "";
 
            SPWebConfigModification addElement = new SPWebConfigModification(
                @"add[@tagPrefix=""SharePoint""][@namespace=""My.Menu""][@assembly=""My.Menu, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd3368f0ff736bff""]", 
                "configuration/system.web/pages/controls");
            addElement.Owner = "My.Menu";
            addElement.Sequence = 40;
            addElement.Type = SPWebConfigModification.SPWebConfigModificationType.EnsureChildNode;
            addElement.Value = @""SharePoint"" namespace=""My.Menu"" assembly=""My.Menu, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cd3368f0ff736bff"" />";
 
            site.WebApplication.WebConfigModifications.Add(controlsSection);
            site.WebApplication.WebConfigModifications.Add(addElement);
            site.WebApplication.Update();
            site.WebApplication.WebService.ApplyWebConfigModifications();
 
    }

Securing custom application pages in _layouts directory

Matt — Fri, 26 Feb 2010 12:04:22 +0000

I had a need to be able to only allow site collection admins to see some custom pages I had deployed into the _layouts directory.
Create a custom code behind class for your aspx that inherits from LayoutsPageBase.
Next, override the OnLoad method in your code behind and add the following code

if (!SPContext.Current.Web.UserIsSiteAdmin)
              SPUtility.HandleAccessDenied(new Exception("You need to be a site administrator to access this page."));

This will redirect the user to the built in SharePoint Access denied page, for consistency.

Validation Group with SharePoint DateTimeControl

Matt — Tue, 16 Feb 2010 10:57:30 +0000

The SharePoint DateTimeControl has a property called IsRequiredField, which will act like a RequiredFieldValidator for the control. The problem is when working with web parts in SharePoint calling Page.Validate in your web part can have unexpected results. It often ends up firing validators elsewhere on the page, particularly if the web part is used on a list form for example.
One answer of course is to use a validation group in your web part, this is where the DateTimeControl falls down as it doesn’t have this property.

The answer to this to create a validator in your webpart and hook it into the TextBox element of the DateTimeControl, which will then allow you to set the validation group on it.

To do this use the following code when you create your validator.

valReviewDate.ControlToValidate = string.Format("{0}${0}Date", dteReview.ID);

This post, describes how to do it from code in front.

Disable Web Part button after clicking

Matt — Tue, 16 Feb 2010 10:24:40 +0000

Not sure how, I got to the end point of this so there may be other ways of doing it.
Basically I had a web part the when the button was clicked I needed to disable it.
Adding .Attributes["onclick"] didn’t seem to work, and after trying a few things I managed to get it working this way.
Add the following code into OnPreRender of the web part, assuming cmdGenerate is the name of your button.

cmdGenerate.Attributes.Add("onclick", Page.ClientScript.GetPostBackEventReference(cmdGenerate, "") + ";this.value='Please wait...';this.disabled = true;");

Using Custom Masterpage in _layouts directory

Matt — Mon, 24 Aug 2009 10:19:52 +0000

To use a custom or the default masterpage in custom aspx pages located in your _layouts directory use the following code in the code behind for the page.
N.B I didn’t declare any masterpage useage in the actual aspx file.

protected override void OnPreInit(EventArgs e)
{
    base.OnPreInit(e);
    // Set the masterpage to the default.master.
    using (SPWeb webCurrent = SPControl.GetContextSite(Context).OpenWeb())
    {
        string strUrl = webCurrent.ServerRelativeUrl + "/_catalogs/masterpage/default.master";
        // custom.master is your same default or main master page 
        // being used for main portal pages. Change that path according to your need
        this.MasterPageFile = strUrl;
    } 
}

CAML Querying using DateTime.

Matt — Tue, 13 Jan 2009 11:45:47 +0000

Caml queries on DateTime fields by default do not use the Time portion of the field. To overcome this use the attribute IncludeTimeValue=’TRUE’ in the value tag. For example:

SharePoint Web Part Properties

Matt — Wed, 03 Dec 2008 15:08:03 +0000

When creating a WebPart inheriting from System.Web.UI.WebControls.WebParts.WebPart, use the following code to add a custom Integer property that will sit in it’s own Category when you modify the properties of the web part.

private const int _intMaxShiftsPerDay = 0;
private int IntMaxShiftsPerDay = _intMaxShiftsPerDay;
[Category("Custom Properties")]
[DefaultValue(_intMaxShiftsPerDay)]
[Personalizable(PersonalizationScope.Shared)]
[WebDisplayName("Maximum Shifts Allowed Per Day")]
[WebDescription("Type in the maximum allowed shifts per day for each person")]
[WebBrowsable(true)]
[XmlElement(ElementName = "intMaxShiftsPerDay")]
public int intMaxShiftsPerDay
{
    get
    {
        return IntMaxShiftsPerDay;
    }
    set
   {
        IntMaxShiftsPerDay = value;
    }
}

Deploy a sharepoint solution with stsadm

Matt — Fri, 31 Oct 2008 11:02:25 +0000

First off we need to add the solution to SharePoint

stsadm -o addsolution -filename c:\path-to\filename.wsp

Next, we deploy the solution to the site

stsadm -o deploysolution -name filename.wsp -url http://myurl -immediate Optionally if you use Code Access Security add the following to the above

-allowcaspoliciesand if you have assemblies that deploy to the GAC, add this line to the deploysolution statement above

-allowgacdeploymentThis will create a timer job, we then simply need to execute this job

stsadm -o execadmsvcjobs