Category: Sonstiges

Das neue Jahre bringt neue Aufgaben

Nach fast 8 Jahren bei der Firma Net at Work, startet für mich ein neues Kapitel. Auch auf diesem Wege möchte ich mich noch einmal bei allen Kollegen und Kunden für die Zusammenarbeit bedanken.

Ab heute hat es mich beruflich nach Berlin verschlagen. Dort habe ich bei der ITaCS angedockt. Ich freue mich auf neue Projekte und Herausforderungen.

Ach ja. Ich wünsche allen Lesern ein Frohes Neues Jahr!


You might have noticed, that my website has been offline for a few days.

The telephone line has been cut last week. It has not been activated at our new house, as planed. Today the line was switched on, an the blog is available again 🙂

Turning a Windows 7 DVD or ISO into a Bootable VHD Virtual Machine

With Windows 7 you will be able to boot a VHD.

Scott Hanselman has posted an article about creating a VHD from the Windows 7 installation bits. Cool stuff 🙂 Read about it on his blog.

A quickly set up development box on your desktop/notebook without the overhead of VMWare or Virtual PC.


Here is a similar post in German:

Stefen Krause hat über seine Demo Umgebung geschrieben. Auch er benutzt eine VHD, die dann gebootet wird.

Da normalerweise solche VHDs automatisch auf die eingestellte Größe vergrößert werden, zeigt er wie diese Einstellung mit einer Änderung der Registry umgangen werden kann.

Microsoft Blog – Fix It

How often are you asked by family members or friends “I have a problem with my computer. Can you take a look at it?”

A couple of times I’ve been asked to fix a CD-Rom, which has disappeared from the explorer. In the device manager it had an error code 39. Instead of letting the other fiddle with registry settings, you can tell them to install the fix “CD drive or DVD drive is missing in Windows XP or Vista”.

More fixes are available on the “Microsoft Fix it BLOG

SharePoint Konferenz 2009

Die SharePoint Konferenz 2009 findet am 11. und 12. Februar in München statt.

Auf der Konferenz werde ich einen Vortrag “Best Practices in der Webpart-Entwicklung” halten.

Voraussichtlich werde ich die folgenden Themen behandeln:

· Fallen umgehen und Probleme vermeiden

· Logging in das SharePoint Log

· Webparts mit eigenen ToolParts

· Nutzung “ToHtml” Funktionen

· Berechtigungsprüfung

· Code Ausführung mit erweiterten Berechtigungen

· SharePoint Webcontrols

· SPContext – wo bin ich

· Extension Methods

· Webpart Feature inkl. FeatureReceiver

Great Sourcecontrol

Are you looking for a Sourcecontrol for your projects? Well, I was. Here is where I ended up: SourceGear Vault. It will store the your sourcecode in a SQL table, use the IIS for access, and brings along a client and Visual Studio integration. What could you want more?

And the best of it, it is free!



Somebody said that Vault is free for a single user. Is this true?

Yes. Both Fortress and Vault are free for use by a single user. Simply install the product and do not enter any serial numbers at all. When no serial numbers are present, Fortress and Vault behave as if there is exactly one user license. Note that this free license does not apply when the product is used by more than one person. If you have two people who need to use Vault, you will need to purchase two initial licenses. If you enter a serial number containing only one license, then the product will still have exactly one license present.

So don’t waist your time anymore hassle around with different version of you projects (which are of coarse SharePoint projects 😀 )

Technorati Tags: ,,

Team Foundation Server 2008 and the SP1


Setting up the TFS is not an easy task. In our environment we have the Reporting Services and WSS installed on the TFS server. The TFS and SharePoint databases are on a separate SQL Server. Reporting Services databases are locally stored.

If you now try to install the SP1, it will reconfigure your Reporting Services so that the databases are on the remote SQL Server. Of course that won’t work! So the upgrade fails with an error

Returning IDOK. INSTALLMESSAGE_ERROR [Error 29112.Team Foundation Report Server Configuration: Either SQL Reporting Services is not properly configured, or the Reporting Services Web site could not be reached. Use the Reporting Services Configuration tool to confirm that SQL Reporting Services is configured properly and that the Reporting Service Web site can be reached, and then run the installation again. For more information, see the Team Foundation Installation Guide.]

So what. We will continue with RTM and without the SP1. At least I was thinking that way. Well, obviously the TFS did otherwise. The TFS was completely offline!

To fix the problem I had to do a repair installation through Add/Remove Software. During that process I had 4 or 5 warning that the Reporting Services are not configured, because the database server was changed again to the remote SQL Server! But you can reconfigure the Reporting Services to use the local databases and then continue the wizard.

To be short: If you have a non default installation of your Team Foundation Server 2008, think carefully about applying the SP1.

Technorati Tags:

CopyTool for SharePoint – Update

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.

Technorati Tags: ,,,

Flexible Migration – SharePoint 2003 nach 2007

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.

Net at Work bietet zur Darstellung einer „schleichenden“ Migration von SPS nach MOSS das Net at Work® CopyTool for SharePoint an. Diese Lösung ist auf Basis einer Vielzahl von Migrationsprojekten entstanden und erhöht die Flexibilität in der Planung eines Migrationsprojektes enorm.



Comments / Kommentare

I forgot to alert myself about new comments. Sry! Within the next days, I will answer all your comments. Promised.

Leider habe ich vergessen eine Benachrichtigung für die Kommentare einzurichen. In den nächsten Tagen werde ich alle Kommentare beantworten. Versprochen.

Another place, another proxy

Do you connect to different networks regularly? Well, I do. Switching the proxy each time is annoying. Here is the solution:

Marco wrote a great tool, which will switch your IE proxy based on the Gateway IP or the DNS Suffix 🙂

Have a look at it:


Proxy Switcher is a little helper tool for switching between different proxy settings.

If you are at many locations, e.g. at work, home, hotel, etc. you may be tired of setting (and rember) proxy settings for the different locations.

So, Proxy Switcher will assist you in remeber and easily switch between proxy settings. The major feature which is different from many other tools is, that Proxy Switcher can switch settings automatically depending on network connections.

To make this work, define a new proxy configuration and set a condition for activating it. Possible conditions (in this version) are depending on the DNS suffix (e.g. or on the gateway IP address. If you now connect you notebook to a network, the settings will activated automatically.

Create an eventlog entry

For exception handling it is good practice to write errors to the eventlog.

EventLog.WriteEntry("SharePoint.Error", errorText, EventLogEntryType.Error);

Since SP1 for Windows Server 2003 "the normal user" is not allowed to write to the eventlog. James Kovacs wrote a great article about the problem.

(Remember to create your eventlog source, if you have your own!)

   1:  if(!EventLog.SourceExists("SharePoint.Error", ".")) {
   2:      EventLog.CreateEventSource("SharePoint.Error", "Application", ".");
   3:  }

Install Windows Service Pack on a VM

On a newly installed Virtual Machine you don’t need any uninstall information from a servicepack, which consumes lots of diskspace. You can install the SP2 for Windows Server 2003 (R2) with the /nobackup parameter.


No restart will take place. You will have to perform a manual restart yourself before the service pack installation can be considered complete.

A restart will automatically take place at the end of the installation.This will be handy if you automate the execution of UPDATE.EXE.

You can pop up a dialog to let people know that a restart will take place in X seconds.

/PROMPTRESTART: A request to initiate a restart will be displayed for the interactive user/administrator to acknowledge.


Microsoft includes updated versions of some drivers in the service pack. If the installation finds a driver on your system that it wants to update, it will usually ask if you want to go ahead with this upgrade. Using this flag will force the installer to automatically do this for you. Personally, and I think others agree, if HP, IBM, Dell, etc, have provided me with a driver then I’m going to suspect that there’s something special about it. In fact, these manufacturers often do provide customised or

tweaked versions of drivers from mass manufactures such as Intel or Broadcom. I wouldn’t want to go messing with those drivers, especially if I’m using an OEM version control system for them or an SMS Inventory Tool from the likes of HP or Dell.

Normally, the service pack will create the familiar uninstall folder in the Windows folder. Along with this, a new item is added to the Add/Remove Programs applet in Control Panel. This enables an administrator to roll back the service pack installation if something breaks. Unfortunately, I’ve come across several sites where for some unknown reason, administrators choose to make the C: drive for fresh Windows 2003 installations as small as possible, often less than 5GB. The partition quickly fills up once the OS is installed; quickly followed by anti-virus, backup agents, page file, etc. In this case it may be prudent not to create a backup folder. This means that the service pack can never be uninstalled … so testing and application certification become even more critical.

We’ve just seen how we can choose not to backup files into the Windows folder because C: is nearly full. If you have space elsewhere, you can use the /d flag to point to that path to backup the