Ohh crap. :( thats bad. The worst part are it being closed source. For me it would mean changing jobs. Theres just too many things. Build server unit testing version control etc are a whole new thing. Just in those things a huge investment buying licenses (afaik all are $/commercial in ms land) . After that the porting of code can begin. Its gonna be expensive. Ask if he has calculated the roi on it, if not get a. Net consultant to help on a rough estimate and put a little on the top to be sure..
Regards On Feb 7, 2012 8:57 PM, "shetc" <sh...@bellsouth.net> wrote: > 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 > >
