I have spend about 100 hours in creating a Wicket 1.3 port. Because half of Wicket consists of anonymous classes it is near impossible. I had to add about 1000 new subclasses to get the core to work. When it compiled and actually wanted to start and bind to a port I was unable to get the pages to render. Because these 2 languages are so completely different it is not easy and it will mean that Wicket apps will be completely different to Wicket.NET apps.
Major problems I encountered: property files not supported threading impl works differently anonymous classes not supported loading of html files and getting them to inherit was really odd, maybe it was just me... biggest frustration: finding compatible dependencies... There is a proper maven like system for .NET now but back then they all sucked. Hielke -----Original Message----- From: shetc [mailto:sh...@bellsouth.net] Sent: dinsdag 7 februari 2012 20:57 To: users@wicket.apache.org Subject: Wicket in a Dot Net World Well friends, it's happened -- the company I work for has been bought by a larger competitor. Sadly, the new bosses prefer to work with .NET I don't suppose anyone has ported Wicket to .NET? -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-in-a-Dot-Net-World-tp4366058p4366058.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
