If you're ACKing on the proper way to architect a .Net app, you shouldn't be considering a conversion.

Also strange that you want to go to .Net after insinuating in another thread that Microsoft snoops on you in.


>>Stop. Don't go there. Several reasons:
>
>too global for my taste
>
>>- I've never seen a converter that did a good job. There are always things you need to do manually.
>
>Can be expected from Pareto law. Still, if there is a large amount that can be converted automatically, that should save cost - even if manual operation is needed.
>
>>- Code that is converted tends to be poor and not optimized.
>
>Same could be said about all genetrated code. The typical answer: "We took care and optimized/streamlined the stuff especially because we are experts in that domain" could be said here as well.
>
>>- .NET applications are architected differently.
>
>Full ACK
>
>>A simple conversion will be sub-optimal and could easily have performance issues.
>
>No beef with that part, but if enough cost is saved, not even thinking about conversion might be considered premature optimization ;-))
>
>regds
>
>thomas