Author: Gerald de Run

I have been implementing workarounds since SharePoint 2007 to overwrite an unghosted (or customized) file that already exists at a specified URL for a File element within a Module element of a Feature element manifest (or site definition which I stopped using extensively in SharePoint 2010 preferring web templates).

Updating existing files when upgrading our SharePoint custom Features can be accomplished by provisioning ghosted files using the Type attribute set to Ghostable or GhostableInLibrary. For unghosted (or customized) files a common trap is setting IgnoreIfAlreadyExists=”TRUE” expecting existing files to be overwritten.… [Keep reading] “File Element OverwriteIfAlreadyExists=”TRUE””

During a recent technical interview I asked the candidate which tools they used to review code quality for their SharePoint custom solutions.
This blog post describes the process and tools we use to check SharePoint code quality for a SharePoint Online 100K user deployment I have been working on.

Our project team uses Team Foundation Service (TFS) Cloud for source code management and continuous integration.  We perform code quality checks as part of TFS Team Build and Release Management processes.… [Keep reading] “SharePoint Code Quality”