Recently we have seen how to Delete Web parts in SharePoint 2010 and 2013 with Windows PowerShell. A logical next step would be to add Web Parts also with Windows PowerShell. So we would have two scripts with which we may replace a given Web element by another. An example of use?
Recently, I have had the need to remove all the web parts of the welcome page of a large number of sites. The number of sites was so big that the option of doing it manually was out. It is in these cases where we can always rely on Windows PowerShell, because the time invested in developing a script is profitable, plus we are learning along the way.
Here it is! At last the most expected version of SharePoint has been made publicly available as public beta build.
The other day when I tried to access https sites from my loved SharePoint soap web services, I got stuck because of a security exception, that said something like “Connection was terminated” there is no trusted relationship.
While I keep working on migration contents from old SharePoint versions to current versions (2010, Online), I’m discovering new little tricky things on the SharePoint Object Model (primarily .net client object model).
The last tricky thing I discovered is that EndDate field for Event List items cannot be updated for existing items (already created).
I’ve been working on accessing SharePoint data remotely (2007, 2010 and Online) in the last months and I found a couple of months ago a breaking point in my developments. The Events List (also known as SharePoint Calendar list).
When I tried to get list items fro this kind of list using this line of code
listsWs.GetListItems(listGUID, "", query, viewFields, rowLimit, queryOptions,
See Beyond The Numbers: Data Visualization with Status Lists in Sharepoint 2010 – part 1 Sharepoint List based Status Indicator and Excel based Status Indicator
Sharepoint 2010 is the IWs place of predilection for creating, authoring and sharing insights using a palette of tools like Excel Services, Performance Point Services, Access services, Power View, Visio services, 3rd party visualization tools and so on.
SharePoint Best Practices: Creating and Configuring Service Applications With (and Without) PowerShell – Part 2
This article pursues the goals of the first part, pointing out the ways to create and configure another interesting service application available in SharePoint 2010—the Web Analytics service application. As usual, I’ll introduce this topic with a general and architectural overview of the Web Analytics functionality, once again paying attention to its scalability and effectiveness. (more…)
In this article is going to be explained the differences between the Windows PowerShell console and the SharePoint Management Shell in SharePoint manage. SharePoint 2010 Management Shell loads a Windows PowerShell profile located in the SharePoint root. The profile’s path is: SharePointRoot CONFIG POWERSHELL Registration SharePoint.ps1.
This script configures the initial user environment for Windows PowerShell. The three things that the profile does are the followings:
I’m developing a custom desktop solution in Windows Presentation Foundation (WPF) that has to access a SharePoint Online contents and do some things with them.
The first thing I had to “fight” with was the Authentication method that is by default a bit different from the On-Premise version (programmatically too). When I started to look for the right documentation about that topic I found quite fast this great article from the MSDN library “Remote Authentication in SharePoint Online Using Claims-Based Authentication” by Robert Bogue. After read the article and download the Sample Code, I told myself “Yeah! This going to be a piece of cake!”.