Wicket.NET?
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)….
May 9th, 2005 at 2:15 pm
Well,
If you are a seasoned Java developer (meaning you know all of what Java and the Java community has to offer) you will like some of what VS.Net has to offer but mostly will feel like you have your legs and arms tied behind you. If you stay there long, you will be porting lots of Java stuff to .Net
Check out Spring.Net. I’ve used it on at least one .Net project, at least the IOC piece.
May 9th, 2005 at 4:23 pm
Thanks. From what I’ve heard, my collegues had some difficulties getting NHibernate to work (correctly).
May 14th, 2005 at 9:28 pm
Not sure what they did wrong. I’ve used it on several projects with no problems. It is very easy to get started with too.
If you can post some of their issues, I will try to help.
Mark