For my current project, I need to work with MS .NET. The project already uses NHibernate and NUnit, both of which I'm familiar with in the Java world.

Although I'm not looking forward to develop mostly in .NET, I anxious to see what .NET does right, and how we can apply that knowlegde for Wicket. Creating a Wicket.NET does't sound that appealing, though. Microsoft already has done a good job at creating a component framework, so probably no need for yet another component framework.

At the moment, I'm already appalled by the installation of the Visual Studio .Net 2003 Architect program. I'm already 2 1/2 hours under way installing the prerequisites (3 times reboot!), security patches (yet another reboot) and installing Visual Studio itself (20% under way)....