Adding ribbon buttons can be a frustrating process. I show how to do it the fast way during development, for easier troubleshooting.
We create an application which searches the SharePoint log for events matching correlation guids it finds on the clipboard. I.e. copy the correlation ID SharePoint gives you, switch to this application, and enjoy.
This post explains how you can run a (SharePoint) Powershell command from C#/SharePoint.
In this second part, we show how we can build an xml structure from information we get from SharePoint. This xml can later be edited, and used as input to the SharePoint creator from part i.
By default, SharePoint 2010 will not let you show html pages in the browser. If you add them to your site, either using upload or SharePoint Designer, the browsers will prompt you to save the file. It is easily remedied; open central admin, manage web applications, select web application, general settings, and change "Browser file handling" to permissive. Ah, but what if you do not have access to CA - like in Office 365? The official answer is simple: "Not supported" If you can rename the files, ......
In this two-part series, we show how we can (easily) create large SharePoint structures using Powershell and xml - and hashtables(!?)
Ok, perhaps not the most meaningful post today, but I haven’t seen it mentioned anywhere else. Crank open a SharePoint web.config, and scroll down to the "action" elements. <Action id="0ff1ce14-0001-0002-0000... <Action id="0ff1ce14-0001-0003-0000... <Action id="0ff1ce14-0001-0004-0000... <Action id="0ff1ce14-0001-0005-0000... <Action id="0ff1ce14-0001-0006-0000... etc. Cute ......
So you've already checked that you have the necessary rights.
Did you install Powershell 3.0 CTP?
Powershell 3.0 CTP seems to have some issues with the SharePoint snapin, and will not give you the above error. Uninstall it, and things start working again.
It is frequently useful to create / delete web applications in a development environment. If you need to create a structure, this can quickly become tedious. Enter Powershell, xml and recursive functions. Create the structure in xml. Something like: <Sites> <Site Name="Test 1" Url="Test1" /> <Site Name="Test 2" Url="Test2" > <Site Name="Test 2 1" Url="Test21" > <Site Name="Test 2 1 1" Url="Test211" /> <Site Name="Test 2 1 2" Url="Test212" /> </Site> </Site> ......
In which I show how you can write CAML queries that are understandable, and show how you can query from Powershell.