I haven't done any Java-to-.NET porting, but there are examples out there.
I recently attended a.NET Overview Conference here in NYC. Most of the conference was fluff, but one of the interesting topics was a CafePress case study. CafePress swithced from Java to.NET, you can find an overview of this here:
http://msdn.microsoft.com/netframework/prodinfo/ ca sestudies/cafepress/default.asp
The two metrics that stuck out were that the rewrite took 80% less lines of code (mentioned at the conference and not the article. Most of the code saved was in the data access layer), and that CPU usage dropped from 50-70% to 2-3%.
This is not an independant study, so there is no mention (if any) of the cons of using.NET. However, those are some pretty impressive gains.
Slashdot Mirror
I haven't done any Java-to-.NET porting, but there are examples out there.
.NET Overview Conference here in NYC. Most of the conference was fluff, but one of the interesting topics was a CafePress case study. CafePress swithced from Java to .NET, you can find an overview of this here:
/ ca sestudies/cafepress/default.asp
.NET. However, those are some pretty impressive gains.
I recently attended a
http://msdn.microsoft.com/netframework/prodinfo
The two metrics that stuck out were that the rewrite took 80% less lines of code (mentioned at the conference and not the article. Most of the code saved was in the data access layer), and that CPU usage dropped from 50-70% to 2-3%.
This is not an independant study, so there is no mention (if any) of the cons of using