[bunderbunder]

Library differences could probably just be handled with a support library. Microsoft used one to support its VB6 to VB.NET conversion engine, and it worked fairly well in my experience.

I wonder more about all the myriad C# language features that don't translate directly to Java. If their engine is limited to porting C# 2.0 code then a lot of that hassle probably goes away (though I'd still wonder about unsafe blocks), but that excludes most new code that's been written in the past 8 years. And I would be leery of trusting any automatic porting engine that claims to work with C# 4 but doesn't come with a very clear and detailed explanation of how it's going to handle something like extension methods or late binding.

And, for that matter, a clear explanation for why I should prefer automatic porting of a large project instead of just running it in Mono, using IPC to get it talking to my Java code, and calling it a day.