Finding the solution id from a wsp is quite difficult if you do not have access to the manifest.xml used to create it. I’m using SharePoint installer to install wsp files to client environments, as they think it is a lot safer, than batch files or typing in stsadm commands.

There’s one wsp that I needed to package using SharePoint installer but does not have the source code for it, SharePoint installer requires the solution id. But I don’t have the source code anymore.

In this case a quick and easy way was to login to your development server and deploy your solution package if its not there yet. Then run this stsadm command:

stsadm -o enumsolutions > C:\Temp\solutions.txt

This will list all solutions that is added on your farm, just look for the name of your solution and underneath it is the solution ID.

Popularity: 3%

Audience targeting is a nice feature available in SharePoint Server to allow an administrator to hide and show webparts based on user permissions. A web part can be targeted to certain groups and be hidden for others. If you’re using SharePoint Server and the audience targetting box is missing when you edit a web part. You need to check the following.

1. If you’re using a list web part, for example, a document library web part, make sure that Audience Targetting is enabled on that list. You can go to list settings and click audience targetting.

2. Make sure that you properly configured Shared Services Provider on your Central Administration Site, otherwise it will not be shown.

NOTE: This is only applicable for SharePoint Server 2007, audience targeting for web parts are not available in WSS.

Popularity: 3%

If your SharePoint page turns blank after an ajax request, look no further.
Below is how you can fix it on your SharePoint deployment.

This issue is encountered if you are doing any asynchronous (ajax) request on your SharePoint page, and it appears that this issue does not affect all site templates but only publishing sites.

The fix is very simple, you just need to modify how SharePoint renders the title tag. Unfortunately the default masterpages in SharePoint look like this:

<title id=”onetidTitle”>
<asp:ContentPlaceHolder id=”PlaceHolderPageTitle” runat=”server”/>
</title>

And change it to this, make sure it is all contained within a single line.

<title id=”onetidTitle”><asp:ContentPlaceHolder id=”PlaceHolderPageTitle” runat=”server”/></title>

Deploy the masterpage, and that should be enough to fix this issue.

Popularity: 6%

With SharePoint 2010, “after” events or those ending with -ed such as ItemAdded, ItemDeleted, are exlusively asynchronous events. Most of the time, these would be fine and in case we needed the event to be synchoronous, then we use the -ing events such as ItemAdding or ItemDeleting. But what if we want to do some cleanup after the event has been completed? A scenario that came up to my mind is if we want to redirect the user to another page after a new item has been added or deleted to a list.
Post Synchronous events are now supported with the addition of the “Synchronization” property in the SPEventReceiverDefinition class.
SPEventReceiverDefinition myReceiver = eventReceivers.Add();
myReceiver.Synchronization = SPEventReceiverSynchronization.Sychronous;

Popularity: 11%

Microsoft has released the RTM version of its virtual machine images for evaluation environment. It contains two VHDs with pre-configured Windows Server 2008 R2 and SharePoint 2010, together with other software.

These virtual machines are Hyper-V images, so it requires your host OS to be Windows 2008 Server  R2 with the Hyper-V role enabled. In my case, I’m running Windows 7 as my host OS, so I convert the images to VMware Workstation images using WinImage Tool.

Continue reading →

Popularity: 7%