Yibo Hui (徐艺波) blogged about having al look at my (foreign) desk. Quite interesting where your blog entries end up, though. 

Looking around for some cross-post plug-in for a while, I came along this plug-in for Windows Live Writer. Nice idea, but it actually does not load in WLW.

Right now, it is the only plug-in I found so far. I filed the bug and now I am waiting for any response. If nothing happens I have to have a look myself. Thanks for putting it under Ms-PL. If anybody get this plug-in working, let me know.

[svn]Today, I got the first feedback by some of the students about the WebComposition/DGS. Beside the typical start-with-a-new-technology issues considering Visual Studio 2008, ASP.NET and WCF, it looks like the first steps are done successfully. Based on the feedback I received during the day I did several fixes beside the regular enhancements. This evening, I performed a forward integration to incorporate the latest fixes. If you are using the Student Branch, please make sure to  update to revision 1211. 

Changes for today include:

• updated XML documentation of WebComposition.Dgs.Content namespace
• added notes about AppData/Service folder to DemoWeb
• added tests for meta data on service and information store level
• fixed '400 Bad Request' when no write access to AppData folder is given
• fixed SemWeb.dll reference in Content project, now expected to be in /External

[svn]I spend the weekend it setting up the VSR's distributed version control system. From this morning on, the student branch is fully sync'ed and ready to be compiled. Make sure to read the readme.txt in the root directory of the project and copy the SemWeb.dll into your External directory before the first compile run.

This post will give some insight into the distributed version control ad the Distributed and Self-organizing Systems Group. Usually, I am keen about trying out new things, e.g. distributed version control systems such as GIT, Mercurial or Bazaar. However, currently the group's infrastructure is set up with Subversion as internal revision control system.

For the next few months we will start an evaluation phase with the students, working on the WebComposition/DGS approach, based on a distributed version control concept. Core components of the WebComposition project are branched into a dedicated student branch where all students can commit changes. Based on this branch each student creates his or her private branch for local changes.

The coordinator (usually some DSS staff) takes care of regular forward integration of the core components into the student branch. Each student in turn is responsible for forward integration into his or her own branch.

Changes can be submitted after testing and evaluation back into the central student branch by each student performing backward integration. The group working on the project has to agree in the LAKS meeting on the change before backward integrating the updates.

The coordinator finally takes care if these changes are also backward integrated into the original project trunk.

Step 1: Create a local working copy

First, look for a place where to checkout the working copy. Create a folder, e.g. branches\students and use Tortoise to checkout a working copy.

Select the student branch and the local folder where to store the working copy to start the checkout.

After the checkout is finished, you should will have a local working copy of the student branch.

Step 2. Create a private branch

Select 'Branch/tag' from the context menu of your working copy.

Use the path of your private project within the repository to create the branch.

Step 3: Forward integrate changes from the student branch

When the student branch was updated you might be interested in getting these updates into your private branch. To forward integrate these changes into your private branch, select the folder where your local working copy lives, and use the Tortoise context menu to select 'Merge...'.

Select the repository folder you want to forward integrate Probably this will be the student branch - the paths in the screenshot below will thus differ from yours. Select the revision from where the forward integration should start. Now select the revision where it should end. Usually, this will be the head revision. After merging submit the changes of your working copy to the repository and you are done.

To get some more information on Subversion, or to learn how to perform the steps above on command line, refer the Subversion book.

[svn]In preparation for our first LAKS meeting, I did a major forward integration of the WebComposition/DGS trunk into our student branch. The documentation in the DemoWeb project is now completely updated and available in the student branch. Several minor updates will follow in the next few days. A brief description how to create a private branch can be found here.

[clock]The first Learn And Knowledge Sharing (LAKS) Meeting at the Distributed and Self-organizing Systems Group will be held at Wednesday, the 30th April 2008 in Room B203. The time is 13:00 - 16:00 . The following appointments will be every Thursday, 13:00 - 16:00 in Room B203.

These days I won't have much time for blogging since I am working on the refresh for the WebComposition/DGS web site. The final site is not online, yet. However, I can give you a first glance how the new site will look like. Stay tuned.

The documentation will cover the most vital design aspects of the WebComposition/DGS approach as well as all necessary information to write your own extension for the service. I am working hard to make the live demos available  as soon as possible as part of the site.

It is finally done. After some exiting days I moved my web site, blog and domain to my own server. A few seconds I was informed about the succeeded the domain transfer. Now I am just waiting that all the DNS are updated. Since everything is already set up and prepared for the domain name, the master plan is accomplished.

1. Got root
2. Install VMware
3. Install a Windows Server 2008
4. Move my existing site to the new server

In to make sure such a relocation goes off without a hitch just follow a few simple rules

1. Terminate the contract with our current provider, best in written form or by fax
2. Inform your current provider about the domain transfer
3. Request the domain transfer with your new provider
4. Set up your Web applications on the new site - test it!
5. Make the site listening to the domain name to be moved.
6. Make sure you have some mail server set up already listening to the domain name being moved.

That's all.

Here we go...

You probably run into the same problem that Windows Server 2008 won't be able to recognize the virtual hard disk you have planned to installed it on. Get the corresponding SCSI drivers as floppy image from the VMware site. Select the image and connect the drive.

Now say 'Browse' and choose drive 'A:' - don't forget: After selecting the .flp image you also have to connect the drive. Otherwise Windows cannot read the device.

Click on 'Next' and after a few seconds the hard disk will be found. The currently available drivers for Windows Server 2003 seem to work fine also for Windows Server 2008.

Installing the VMware Tools might be a good idea. You can find the image at /usr/lib/vmware/isoimages/windows.iso or just install them from the VMware management console's menu. While the image is mounted go to 'Device Manager' and install the drivers for the network adapter which probably does not work yet.

Now some tweaking for the IP, gateway and DNS servers and one more step in my master plan achieved.

1. Got root
2. Install VMware
3. Install a Windows Server 2008
4. Move my existing site to the new server