Back from vacation. 1 week with an offline version of feeds is hard. So I read the postings I got closely 🙂 One post I do want to bring your attention to, is about SharePoint Controls.
My post about using the SharePoint Controls shows how to use the controls you see in forms (TextField, NumberField, LookupField…).
There are plenty of SharePoint controls, which you can use. Robin Meure has written a post “re-using SharePoint controls”.
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.
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.
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 🙂
An SPQuery for lookup columns should be easy. Start the famous U2U Caml Editor, configure your query, and query the list. 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: <Where> <Eq> <FieldRef Name='LookupField' LookupId='TRUE'/> <Value Type='Lookup'>2</Value> </Eq> </Where> Remember to omit the Query tags from the U2U Caml Editor when pasting the query into your Visual Studio source code!
My SharePointConsole has some new commands.
If you don’t know it, it is a command line utility which allows you to perform some common tasks. Currently the theese commands are implemented:
EnumContentTypes CreateContentType RenameContentType DeleteContentType DeleteAllListItems ShowInNewForm ShowInEditForm ShowInDisplayForm DeleteAllVersions RecycleAllVersions SetTitleWithFilename SetSearchCenterUrl SystemUpdate FeatureManager EmptyRecycleBin Download the SharePointConsole
Deploying a SharePoint solution (.wsp file) to a SharePoint farm should be easy. Even if the farm contains 4 SharePoint Servers.
Just stsadm –o addsolution –filename solution.wsp. Some waiting so the deployment is done on every server, and we should be happy.
Well, the result was an Error in the solution status. Additionally the ULS log showed
Updating SPPersistedObject SolutionOperationStatus Name=SolutionOperationStatus Parent=SPSolutionLanguagePack Name=0. Version: -1 Ensure: 0, HashCode: 38896601, Id: 87c32e71-13f0-4d85-a215-29f1d180d239, Stack: at Microsoft.
Auf der diesjährigen BASTA! in Mainz Ende September werde ich als Redner dabei sein.
Wie auch schon auf der SharePoint Konferenz in München, werde ich einen Vortrag über Webpart Entwicklung halten.
Wer kommen möchte, kann noch den Early Bird Rabatt bis zum 29. Juni mitnehmen.
Managed paths are great for creating many site collections under one URL. You should not forget to create a site collection at the root of the web application.
There is a KB article about this.
During the update, you can run into the following exception:
Exception: System.Data.SqlClient.SqlException: Address Windowing Extensions (AWE) is not supported in this edition of SQL Server.
Configuration option ‘show advanced options’ changed from 0 to 1. Run the RECONFIGURE statement to install.
To solve the issue and be able to install the SP2 to your SharePoint Servers, you will need to disable the AWE option in the SQL server properties. If you like, you can switch it back on after the update.
