Event Receivers and Content Deployment Jobs

November 23, 2010 by Joel Jeffery

SharePoint 2010 has many wonderful improvements over previous versions. One of which is a vastly improved Content Deployment mechanism and API.

If your application makes use of Event Receivers or Feature Receivers, these can, depending upon what they do, cause problems during a Content Deployment job. If you have code that you’d rather not execute when your event is triggered as a side effect of a Content Deployment job, you can use the SPImportContext object to find out if a job is running, and if so, to take alternative action.

Here’s an example on an ItemAdding Event Receiver (you’ll also need a using statement referring to the Microsoft.SharePoint.Deployment namespace)

/// <summary>
/// An item is being added.
/// </summary>
public override void ItemAdding(SPItemEventProperties properties)
{
    if (!SPImportContext.Current.IsRunning)
    {
        //TODO: add event receiver code here
        base.ItemAdding(properties);
    }
}

If you miss this out this check in an Event Receiver or Feature Receiver, you might cause deadlocks or spurious List Items that you did not intend.

#spthingaday

#spthingaday 001 - Governance. Avoid death by file

#spthingaday 001 - Governance. Avoid death by fileshare #SharePoint, Teams, Planner and #Office365 projects need executive sponsorship.

#microsoft #microsoftoffice #microsoftsharepoint #microsofttraining #officetraining #freetraining #trainingvideos #contentmanagement #enterprisecontentmanagement

#spthingaday 001 - Governance. Avoid death by fileshare #SharePoint, Teams, Planner and #Office365 projects need executive sponsorship.

#microsoft #microsoftoffice #microsoftsharepoint #microsofttraining #officetraining #freetraining #trainingvideos #contentmanagement #enterprisecontentmanagement ...

15 0

#spthingaday 003 - Information Architecture. Folde

#spthingaday 003 - Information Architecture. Folders are evil. Use metadata. #SharePoint, #Office365..
On a fileshare, all you have is path and filename. That's the only axis by which you can classify your stuff. So you nest folders, within folders, within folders. Then you pack the filename with extra bits of information - like the initials of the last editor, or the version number.
You don't need to do this in SharePoint. Use metadata.
Add columns to your libraries. Text columns, number columns, choice columns, managed metadata columns. Each file can have several of these values simultaneously. But a file can only live in one folder at a time.
Use metadata.

#microsoft #microsoftoffice #microsoftsharepoint #microsofttraining #officetraining #freetraining #trainingvideos #contentmanagement #enterprisecontentmanagement

#spthingaday 003 - Information Architecture. Folders are evil. Use metadata. #SharePoint, #Office365..
On a fileshare, all you have is path and filename. That's the only axis by which you can classify your stuff. So you nest folders, within folders, within folders. Then you pack the filename with extra bits of information - like the initials of the last editor, or the version number.
You don't need to do this in SharePoint. Use metadata.
Add columns to your libraries. Text columns, number columns, choice columns, managed metadata columns. Each file can have several of these values simultaneously. But a file can only live in one folder at a time.
Use metadata.

#microsoft #microsoftoffice #microsoftsharepoint #microsofttraining #officetraining #freetraining #trainingvideos #contentmanagement #enterprisecontentmanagement ...

14 0

#spthingaday 006 - Information Architecture. Site

#spthingaday 006 - Information Architecture. Site Columns. #SharePoint, #Office365, #InformationArchitecture.. Once you've chosen a column type, you can create that column again and again, on as many Lists and Libraries as you like. But each time you do that, you run the risk of introducing a typo or getting a setting wrong.

Cut down on the typing and the typos by using Site Columns instead. You can create a Site Column once, and reuse it on as many Lists and Libraries as you like. Once created, you can use your Site Column within the current site and below. For maximum reuse, create Site Columns at the root web or top-level site in your Site Collection.

When naming your Site Column, don't put spaces in the title. The internal name of a Site Column has spaces replaced with the ungainly string "_x0020_". This causes developers lots of headaches later. By all means rename/retitle your Site Column with proper spaces, if you want to, after you've created it.

Site Columns help with consistency, but for the biggest return on investment, use them with Content Types.

We'll talk about that those tomorrow.

#microsoft #microsoftoffice #microsoftsharepoint #microsofttraining #officetraining #freetraining #trainingvideos #contentmanagement #enterprisecontentmanagement

#spthingaday 006 - Information Architecture. Site Columns. #SharePoint, #Office365, #InformationArchitecture.. Once you've chosen a column type, you can create that column again and again, on as many Lists and Libraries as you like. But each time you do that, you run the risk of introducing a typo or getting a setting wrong.

Cut down on the typing and the typos by using Site Columns instead. You can create a Site Column once, and reuse it on as many Lists and Libraries as you like. Once created, you can use your Site Column within the current site and below. For maximum reuse, create Site Columns at the root web or top-level site in your Site Collection.

When naming your Site Column, don't put spaces in the title. The internal name of a Site Column has spaces replaced with the ungainly string "_x0020_". This causes developers lots of headaches later. By all means rename/retitle your Site Column with proper spaces, if you want to, after you've created it.

Site Columns help with consistency, but for the biggest return on investment, use them with Content Types.

We'll talk about that those tomorrow.

#microsoft #microsoftoffice #microsoftsharepoint #microsofttraining #officetraining #freetraining #trainingvideos #contentmanagement #enterprisecontentmanagement ...

14 0