Hello everybody. I have updated the “Net at Work CopyTool for SharePoint”. Some of the new features are: GUI: You can now interact with the program with a nice WPF GUI Copy Subareas: If you want to copy an Area with its Subareas, you can do so now Copy only selected lists: Now you can copy only certain lists, and not a whole Area as smallest part As always, you can find more information here.

It is a annoying that RSS feeds do not display images correctly, if your feedreader is offline. The problem is, that the links generated by the SharePoint RSS feed api returns relative links instead of absolute links. But there is a solution: –> Images Broken When Viewing Windows SharePoint Services RSS Feeds in Outlook Here is a small update if you want to make a regular link absolute as well:

Your custom field type can be added to a list in a browser easily. But how do you add a custom field type via code? Here is my way: add a new field with the field type from which your custom field type derived change the field type of the new field to your own custom field type In my case my custom field type derived from a SPFieldLookup. 1: // create new lookup field <pre>&lt;font size=2>&lt;span class=lnum> 2: &lt;/span>&lt;span class=kwrd>string&lt;/span> newFieldName = fields.

There is great tool on CodePlex. SharePoint Content Deployment Wizard. The SharePoint Content Deployment Wizard is a tool for SharePoint 2007 which provides the means to deploy the following content: – site collections – webs – lists – folders – list items (including files)

Do you have comments on your SharePoint blog activated? Anonymous users may leave comments which you have to approve for them to show up? Good. The problem is that there are plenty spam posts which I don’t want to sort out manually. Here comes my solution: The RH.NoBlogCommentSpam SharePoint solution. What does it do? Approve comments from non anonymous users (you can decide if logged in users, may post links) Recycle posts with comments in the subject / body (you can decide) Approve comments from anonymous if they do not contain links Requirements make sure you read them carefully!

Prerequisites: Microsoft strongly recommends installing the SP1 before you install the Infrastructure Update. In my opinion you should have done so much earlier, if your SharePoint Farm is still running RTM! Installation steps: Acknowledge the license to install the update The SharePoint Configuration Wizard will start automatically after the update has been installed Conclusion: Well, updating your farm is like installing a regular hot fix. Nothing more. Description of the Infrastructure Update for Windows SharePoint Services 3.

Since so many people asked for support to upload documents as well, I have implemented this functionality into my WikiWebpart. Now you can add pictures and files directly into your wiki by uploading them from the clients. As always, you have to install the solution, and activate the WikiWebpart feature for you Sitecollection as described in Updated WikiWebpart + Tool to install it. The Webpart will detect an existing picture and document library, and use it.

The sessionState allow you to store information not in the ViewState, but in the HttpSession object. See MSDN. To enable the sessionState, you will have to modify your web.config. All lines which need to be modified, are within the <system.web> tag: In the default settings, the httpModule for the session state is commented out. We will simply remove the “<!–” and “–>” around the line. 1: <httpModules> <pre style="padding-right:0px;padding-left:0px;font-size:8pt;padding-bottom:0px;margin:0em;overflow:visible;width:100%;color:black;border-top-style:none;line-height:12pt;padding-top:0px;font-family:consolas, 'Courier New', courier, monospace;border-right-style:none;border-left-style:none;background-color:#f4f4f4;border-bottom-style:none"><span style="color:#606060"> 2:</span> <span style="color:#0000ff">&lt;</span><span style="color:#800000">clear</span> <span style="color:#0000ff">/&gt;</span></pre> <pre style="padding-right:0px;padding-left:0px;font-size:8pt;padding-bottom:0px;margin:0em;overflow:visible;width:100%;color:black;border-top-style:none;line-height:12pt;padding-top:0px;font-family:consolas, 'Courier New', courier, monospace;border-right-style:none;border-left-style:none;background-color:white;border-bottom-style:none"><span style="color:#606060"> 3:</span> .

Sometimes even I forget what I have developed and blogged on my page. To give an overview I have created a page which lists all of them and helps you find what you want. You can find the overview of my developments here.

With this update the problem that SPContext.Current.Web.CurrentUser is sometimes null is solved. Additionally there are lots of information written to the ULS logs, if you have configured your farm to log information with the level “Monitorable” More and download…

I have updated my FileserverAccess Webpart. added danish language support (thx to Anja) performance tuning Original post

In many occasions you have to specify the class as fully qualified name. I always forget how to do so. [namespace].[classname], [assemblyname], Version=[version], Culture=[culture], PublicKeyToken=[token] Now I know where to look at, if I stumble across the fully qualified name 🙂

Ein wenig Werbung sei auch erlaubt. Ich habe ein Tool für die Migration von SPS 2003 nach MOSS 2007 geschrieben: Die Migrationswege von 2003 nach 2007 auf Basis der Herstellertools erweisen sich in der Praxis meist aus unterschiedlichen Gründen als unzureichend: Quell-und Zielsystem sollen unterschiedliche Strukturen aufweisen, MOSS 2007 wurde schon parallel in Betrieb genommen, die Migration soll nicht ad-hoc passieren, Migrationen von gesamten Datenbanken schlagen fehl oder sind komplex.

A nice feature of a SPWeb, SPSite or SPWebApplication is the Properties Property. You can save information to this Hashtable. e.g. webApplication.Properties[“MyProperty”] = “5”; After a change to the PropertyBag, you have to webApplication.Update() the changes. But here comes the problem. The account updating the Properties has to be a member of the “Farm Administrators” group to be able to save the changes to the SPWebApplication, because you change a SPPersistantObject of your farm!

In one of my solutions I wanted to add a SPTimerJob through a FeatureReceiver in the feature. The feature was scoped to “Web”. I got an “Access denied” when I tried to do so. The solution I found, was to create a second feature, which was scoped to “WebApplication”. From within this feature, I was able to create my timer job. But only in FeatureActivated. When I tried to add the job from FeatureInstalled, I got the error that SharePoint did not find the assembly, even if it was installed to the GAC.