On Wed, 2007-07-18 at 17:42 +0100, Robert Greig wrote: > On 18/07/07, Arnaud Simon <[EMAIL PROTECTED]> wrote: > > > I was expecting of using the Java Language Conversion Assistant that > > comes with visual studio. > > That is not really a tool that can be used to maintain a piece of > software. It can give you a rough conversion but it needs a lot of > manual intervention. Plus it does not generate idiomatic .NET code. > From memory it doesn't deal with NIO either and would almost certainly > explode with MINA and some of our other dependencies.
I know that JLCA is not that good, they have a 3.0 beta version available that may improve things though. I was expecting of using it as a starting point. Once the first migration done the .Net repository would leave its own life. > > Another solution would be to use The XML > > Encoded Source tool that would convert java into XES and XES back to > > C#. > > I haven't tried it but I have to say I am quite skeptical, especially > since XES is still 0.4 alpha. I know this is a very much an early version but it could be a good idea for our code generation tool. I agree with you that generating the two clients from the same code is very much an an utopia.
