SharePoint

Microsoft announced yesterday that the Office and SharePoint teams have released the 2013 RTM version.

Availability for Volume Licensing (VL) customers as well as those with an MSDN or Technet account should be available by mid-November (Just in time for the SharePoint Conference). General availability is expected by early December.

Office 365 should also be updated by mid-November to take advantage of the new features.

Four colleagues at Alcero and me have register a team (Hot Box) for this year IRON SharePoint competition at SharePoint Summit in Toronto. We will be building a SharePoint solution in less than three during the summit (May 14-16) and present to the judges our solution.

Beyond the 5000$ price for the winning team, as per the IRON SharePoint page:

The winners will also enjoy IRON SharePoint immortality and be the envy of their peers.

[Read More]

Microsoft has launched the Windows PowerShell Command Builder for Microsoft SharePoint 2010 Products and Microsoft Office 365 allowing you to create PowerShell commands graphically and more easily than if you had to type them yourself.

It is a simple Silverlight application but it allows you to make queries (SharePoint Server 2010, Foundation 2010, and Office 365) that can be more complex:

The documentation is here!

Happy PowerShell

Next week, I will be at the SharePoint Conference 2011 in Anaheim. This Microsoft event is dedicated to SharePoint and related technologies.

If you attend this event, meet me at the Alcero booth, which will be an exhibitor all week. It will be my pleasure to discuss with you!

When you want to make changes to the web.config file of your SharePoint 2010 application, you can use two methods:

• Create a webconfig.<your_name>.xml file that you add to the \CONFIG directory (Source on MSDN)
• Do it programmatically and use the SPWebConfigModification and SPWebApplication.WebConfigApplication objects (Source on MSDN).

However, when you use the second method and remove the changes from the file using Remove(), the changes are not removed. Even if you use .Update() and .ApplyWebConfigModifications(). This may only result in your modification appearing multiple times in the web.config file, but if you insert more sensitive modifications to uniqueness, such as for an HttpModule, it creates an error that prevents the site from functioning (Error 500).

Context

You are developing a SharePoint 2010 application using Visual Studio 2010 on a Windows 2008 64-bit server. You want to run a post-deployment script (PowerShell for example) for debugging:

The Problem

When you add a script, for example: powershell $(ProjectDir)\PowerShellScript\MySuperPowerShellScript.ps1

You always get an error when running the script:

Error occurred in deployment step ‘Run Post-Deployment Command’: The command "powershell $(ProjectDir)\PowerShellScript\MySuperPowerShellScript.ps1" exited with error code: 1.

This error is due to the fact that VS2010 runs in 32-bit mode, as well as its post-deployment scripts, and the SharePoint 2010 APIs run in 64-bit mode. This creates errors when executing the script.

As I mentioned previously, SharePoint Overflow has now reached the beta stage. So you can find the Stack Overflow environment you know but specialized in everything related to SharePoint.

Go consult the experts!

If you develop/configure for SharePoint and also use Stack Overflow (if not, go check it out!), support the cause of SharePoint Overflow: Happy supporting!

When using Silverlight to develop web parts for SharePoint 2010, you might use the Silverlight Client Object Model to access SharePoint data. But what happens if you try to move out of the Silverlight web part and, for example, put Silverlight in a SharePoint dialog box? Answer: Unhandled Error in Silverlight Application Object reference not set to an instance of an object at ClientContext.Current.

The problem arises because the Silverlight web part injects the SharePoint context into the HTML object parameter for the proper functioning of the Client Object Model. Therefore, you need to inject the SharePoint site URLs where the Silverlight is currently displayed into the initParams (MS.SP.url):

I will be present at the SharePoint Summit in Québec (April 11 and 12) as a speaker and exhibitor with Alcero.

Come see my session titled How to Extend Search Capabilities in SharePoint 2010 or you can simply meet me on site.

An excellent way to meet experts and other SharePoint users.