Wednesday, November 30, 2011

SharePoint 2010 calendar's "Add" button issues after fixing the scrolling bug

What?

How to fix SharePoint 2010 calendar's "Add" button issues after fixing the scrolling bug

Why?

Every SharePoint designer must have bumped across the scrolling issue with SharePoint 2010 master pages.

Kyle Schaeffer & Greg Galipeau have already written excellent post 1 & excellent post 2 about this issue and how to fix it and so I am not going into details of the issue and how to fix it.

Of course, with any solution that changes the core way a system works, there is bound to be issues. One such issue is with the OOB calendar web part's "Add" button.

Wednesday, November 16, 2011

SharePoint 2010 - How to deactivate and delete a sandbox solution (site template) that throws exception from UI?

What?


How to deactivate and delete a sandbox solution (site template) that throws exception from UI?

Why?


Created a SharePoint 2010 team site (web) and saved it as a site template.
Created a new site using the newly created site template.
Delete the site with which the site template was created.

Attempted to deactivate the site template and it fails with the below exception:

Unable to access web scoped feature (Id: GUID) because it references a non-existent or broken web (Id: GUID) on site 'url'.  Exception: System.ArgumentException: Value does not fall within the expected range. 
   at Microsoft.SharePoint.SPWebCollection.get_Item(Guid id)
   at Microsoft.SharePoint.SPFeatureEnumeratorBase.GetCachedWeb(SPSite site, Guid  webId, Guid featureId)

Friday, November 11, 2011

How to fix the Visual Studio Exception: "Attempted to read or write protected memory. This is often an indication that other memory is corrupt."

What?


How to fix the Visual Studio Exception: "Attempted to read or write protected memory. This is often an indication that other memory is corrupt."

Why?

Visual Studio (2010 in my case) throws an exception: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

I received this exception whenever I tried to debug even a basic solution. That means an empty Visual Studio solution using "ASP.NET 3.5 Website Project" template.