Normally I don't blog about non technical subjects. But for a great guy I make an exception.

Last night while browsing the Tam Tam intranet I saw Mart Mullers post about Patrick's death. I was completely shocked...Even more because I, because of busy times at work, only came to read about his death Yesterday

Even though I'm currently not a SharePoint developer I had the chance of attending a SharePoint course given by Patrick at Tam Tam. Being a Belgian aswell it was nice to have a fellow Belgian for the SharePoint training here (@ Tam Tam). Later on I met Patrick on the TechEd 2006 (Barcelona) where he invited me to come along with the other Belgians and his colleagues to go out in Port Olympique. I will never forget this guesture of hospitality. Since I was alone there (as the only Belgian from Tam Tam in Barcelona at the National gathering) it was nice to feel involved. And this was just how he was, friendly, without counter-expectations. I remember him as a passionate person, and I will always remember and admire him for all of this.Because of his deep impression he left me this struck me really hard last night, and I have to admit that I shed some tears. But no tears will ever wash away his memory. His knowledge will be alive in all SharePoint developers and this way he will definitely never be forgotten.

My condoleances go out to his family, friends and colleagues. I hope you all can find the strength to continue where he left off to make sure his legacy stays alive.

Patrick, I strongly believe that we'll meet again someday, and I'll buy you a beer then, one of those (belgian beers) that you used in your courses....

Have you too disliked the fact of having an object that, if you wanted to serialize it, required to have all variables to be exposed via a gettable and settable public property? Well, I have!
In this article I'll explain how I solved this issue using .NET Reflection to serialize all private variables from a class to Xml and back.

Have you never wondered how you could stream into a file while reading from it in a separate process or application. I know I have. In this post I'll explain how it works and I'll tell you about my Stream that I've made to do the job right out of the box.

Maybe you too have seen many database persistance systems/techniques, but most of them are very complex. I wanted to have a very simple and transparent way to persist my objects to a SQL Database. I wanted to do as few changes as possible to my classes when my database changes. And therefore I developed this technique for persisting classes to a (any) database.

While exploring the deeps of .NET I found this wonderful class....
The System.Drawing.ColorTranslator class.
If I'd only known earlier.... This class has a static method that converts a System.Drawing.Color to the Html notation of that color,
and another to convert it back.

Article that describes how I fixed the HtmlForm and MCMS Console to make it render Xhtml strict 1.0 valid Html code. This also gives the possibility to fix the action of the form with proven solutions now also on Mcms instead of fixing this with javascript. This makes MCMS an Xhtml Valid CMS which enables it to compete with other leading CMS systems.

What more can I say, this is my first post as you can see, and it will be the first in a series of publications about problems I solved, and things I "invented" while trying to find a solution for a specific problem.

Hold on, the first post will arrive very soon, It will be about my XHTML Strict 1.0 Valid .NET Html form for Microsoft Content Management Server 2002 (MCMS 2002)

I hope to see you back many times in the future and I hope I can give something useful to the blog-community.