SharePointers

The latest discovered ASP.Net vulnerability affects SharePoint 2007 & 2010.  The SharePoint Team's blog has the instructions for the temporary fix here: http://blogs.msdn.com/b/sharepoint/archive/2010/09/21/security-advisory-2416728-vulnerability-in-asp-net-and-sharepoint.aspx

We had a lot of sites that needed to have versioning turned on, here's a simple console app I wrote to do this, you just pass the url of the web as an argument: using System; using System.Collections.Generic; using System.Linq; using System.Text; using Microsoft.SharePoint; namespace Mirant.Utilities.SiteVersioningActivator {     class Program     {         static void Main(string[] args)         {             if (args.Length != 1)                 throw new Exception("URL of the site is required as a parameter");             string webUrl = args[0];             using (SPSite site = new SPSite(webUrl))             {                 using (SPWeb web = site.OpenWeb())  ...

This is definitely from the "I can't believe I hadn't blogged this already department". When you try to use the SPListItem.Url property you wind up getting a url that's relative to the site (even though it starts with a '/'). I've written this method that will return a list item url and takes into account the fact that the urls differ when they're lists or document libraries: private string GetItemUrl(SPListItem listItem)         {             string result;             string itemUrlTemp = listItem.Url.Replace("Lists/", "");             string siteRelativeListUrl = itemUrlTemp.Substring(0, itemUrlTemp.IndexOf('/'));             if (listItem.ListItems.List.BaseTemplate == SPListTemplateType.DocumentLibrary)                 result = SPEncode.UrlEncodeAsUrl(String.For...

I spent a few hours this weekend creating a SharePoint 2010 Developer environment using the RTM. For now, I'm approaching my dev build the same way I had my MOSS 2007 VM set up - a standalone MOSS install with Visual Studio installed. Because I wanted to use a 64bit guest OS (64bit Server 2008), I decided to use VirtualBox as my VM solution, if you want to use VirtualBox, you can get it here . I should note that when I set up my VirtualBox VM I gave it 20GB of hard drive space which was not enough so I had to expand the drive ( described later orange text ). I'd suggest going to 40 or more if you can because Windows,SP2010, SQL, and Visual Studio take up about 18GB (and setting it up right the first time will save you from having to do this . Once I had Server 2008 installed on a VirtualBox VM I downloaded the RTM version of SharePoint from MSDN. I then attached the SharePoint 2010 .iso file to my VM, opened the mounted SharePoint 2010 image and ran the Prerequisite ...

I use virtual box as my SharePoint VM host because I want to be able to run 64bit Server 2008 R2 on my Windows 7 host machine.   When I first installed SharePoint 2010, the VDI (Virtual Disk for VirtualBox) I created was too small, so I had to expand it.   This is a bit of a challenge, but by doing some research I figured out how to do it. The process involves creating a new, larger disk and copying the original boot and main partitions to the newer disk.   This can be done with gparted .  and the steps to do so are well documented here However there are a few more steps you'll need to follow because you are using 64bit Server 2008 R2: After you've followed the above instructions, mount the newer larger drive as the Primary Master and mount the Server 2008 R2 ISO. Boot to the ISO (hitting any key when prompted) Choose your language then on the next screen select repair Select the partition and click ok Choose the command line option Switch to your c: drive ...

This, surprisingly, took a lot of digging to come up with, but the solution is simple. 1. Go to your search results page 2. Click Site Actions > Edit Page 3. On the search Core Results web part choose 'Modify Shared Web Part' 4. Expand the Miscellaneous section. 5. Type your scope name in the 'Scope' box, then click apply. 6. Test your Search

Recently we needed to integrate Milkbox (Lightbox that supports Flash and other things) to our SharePoint-based Intranet Site. In order to do this you need to do the following to your master page. Download the Milkbox Code . Depending on how you plan to implement this solution you can store the files in a number of places, either in a doc library or on the file system in the 12 hive. In this example I created an STSDEV solution and added the downloaded files into the solution so they would deploy to the TEMPLATE/LAYOUTS directory in the 12 hive. If you choose to save it to another location, be sure to update your references from the '_layouts/...' references I gave to the .js and .css files.   Ensure the following DOCTYPE declaration is at the top of your masterpage: <!DOCTYPE HTML PUBLIC “-//W3C//DTD HTML 4.01 Transitional//EN”> Ensure the following assembly registration is in the top of your master page: <%@ Register Tagprefix="PublishingWebControls...