Digital Transition

Recently, I’ve been involved in a .NET project that uses both VB.NET and C# projects in the same Visual Studio solution. Personally, I prefer C#, but VB.NET isn’t that hard to switch to, except that you can run into an unlogical namespace inconvenience.

VB.NET and C# handle the namespace inheritence in their class files and project files differently :S

VB.NET project

1. Specify the Root namespace of your project as “Test.VB”
2. Add the following class to that project:
   Namespace Test.VB.TestNamespace
Public Class Class1
'Some code
End Class
End Namespace

C# project

1. Specify the Root namespace of your project as “Test.CS”
2. Add the following class to your project:
   namespace Test.CS.TestNamespace
{
public class Class1
{
//Some code
}
}

Addressing those classes from your main project in the solution:

Test.CS.TestNamespace.Class1 class1;
Test.VB.Test.VB.TestNamespace.Class1 class2;

As you can see… The VB.NET class inherits the project’s namespace, the C# class doesn’t.

Just before bedtime, I payed a visit to amazon.com and a nice surprise it was… Amazon is all dressed up for the holidays. Looking great!

… At first sight. I couldn’t resist looking “under the hood”. What a mess!!! Including embedded javascript and CSS. I had expected more from Amazon.com.

A beautiful and interactive web trendmap from Information Architects in japan.

[Via: FutureLab]

Finally after… euhm… waaaay to long, a new TopStyle.

I’ve been doing some extra tweaks to the new layout and there are still more to come. Nothing much noticeably, except maybe the categories.
Some categories have been removed (Google, Personal Throughts, Search Engines,…) or replaced by tags, because that made more sense. The post in them aren’t gone, just moved to different categories (most likely the parent category of where they were).
I’ll be using tags more often, but going over all previous posts would be a bit too much work.