SharePoint Blog - René Hézser

Anmelden RSS Feed RSS Feed
Startet die SucheErweiterte Suche

Archive

Kategorien

Links

Andere Blogs



Add to Technorati Favorites

Jun 262009

SharePoint SP2 and expired license update

If you ran into the expired license issue after applying the Service Pack 2, you will be happy to know Microsoft has released an update to resolve the issue.

Quote from the SharePoint Team Blog:

The update can be applied before or after Service Pack 2 installation.  If the update is applied prior to installing Service Pack 2 it will prevent the expiration date from being improperly activated during installation of Service Pack 2, if it is applied after Service Pack 2 it will remove the expiration date incorrectly set during installation of Service Pack 2.

Here is the link to the Knowledge Base article: http://support.microsoft.com/kb/971620 (“When you install the 2007 Microsoft Office servers Service Pack 2, the product expiration date is activated incorrectly”)


Published: 6/26/2009  11:55 AM | 0  Comments | 0  Links to this post
Tagged as: SharePoint

Jun 242009

.NET 3.5 and Silverlight

Using AJAX or Silverlight from within SharePoint in Webparts requires you to modify the web.config to support the technology. I don’t mention that you have to install the .NET Framework 3.5 SP1 and Silverlight to be able to use it…

Instead of changing the web.config manually (.NET Framework 3.5 AJAX und Silverlight in SharePoint registrieren von Fabian Moritz), you can use my features. They do all the necessary changes for you. The Silverlight feature requires the .Net 3.5 feature.

image

Installation

  1. Add the solution to your farm “stsadm -o addsolution -filename RH.Net35WebConfig.wsp”
  2. Deploy the solution “Central Administration > Operations > Solution Management”
  3. Activate the features on a web application “Central Administration > Application Management > Manage Web Application Features”

Uninstall the solution

After you’ve deactivated the feature(s), you might get an exception (if you have set your customErrors to Off, or visit the site from your SharePoint Server):

image

This exception is thrown, because the IIS does not like the empty XML Nodes:

<system.web.extensions>
  <scripting>
    <webServices>
    </webServices>
  </scripting>
</system.web.extensions>

You can safely delete the empty nodes from your web.config.

Update 22. Aug 2009

Add section configuration/system.web/pages if it does not exist.

Download

Download RH.Net35WebConfig.wsp

Download Source RH.Net3.5WebConfig-Source


Published: 6/24/2009  7:13 PM | 0  Comments | 0  Links to this post
Tagged as: Development, SharePoint, Solution

Jun 232009

CKS:EBE on sharepoint.microsoft.com

Blogs on the SharePoint sites from Microsoft are using the CKS:EBE.

The first one to move is Yvonne M. Harryman, who is moving her blog from Wordpress to http://sharepoint.microsoft.com/blogs/SharePointBeacon. I am sure other blogs will use the Enhanced Blog Edition soon.

It is great to see that your own work is useful :-)


Published: 6/23/2009  9:36 PM | 0  Comments | 0  Links to this post
Tagged as: CKS EBE, SharePoint

Jun 042009

SPQuery with lookup columns returns no data

An SPQuery for lookup columns should be easy. Start the famous U2U Caml Editor, configure your query, and query the list.

image

This query will get a result if the lookup column stores something like “1;#1”. But if its value is e.g. “1;#Title”, the query will not return an item.

So what can we do about it?

Add a LookupId='TRUE' to your query, so it will look like this:

   1:  <Where>
   2:     <Eq>
   3:        <FieldRef Name='LookupField' LookupId='TRUE'/>
   4:        <Value Type='Lookup'>2</Value>
   5:     </Eq>
   6:  </Where>

Remember to omit the Query tags from the U2U Caml Editor when pasting the query into your Visual Studio source code!


Published: 6/4/2009  8:21 PM | 1  Comment | 0  Links to this post
Tagged as: Development, SharePoint, SPQuery