[Mono-list] Typical Port issues for C#->Mono

[Rodrigo Kumpera]

Your best shot is to try the MoMa tool which will give you a pretty clear
picture of how much work
the port might require. http://www.mono-project.com/MoMA.

Once you have such information it will be easier to measure the porting
effort to bring your C# project
to work under mono. You can, as well, use the VMWare image or the LiveCD to
try out the last release
with your software.



On Mon, Oct 13, 2008 at 6:59 PM, Dev007 <toms at sabigames.com> wrote:

>
> We in the process of porting a C# project to another platform and are
> debating going with mono or doing a complete re-write in C++.
>
> >From people's experience here what are some of the challanges they you
> face
> going from .NET on the PC to Mono.
>
> Considering these challenges would you be inclined to say a Mono port would
> take 1/2 the time of a C++ rewrite? More that than that? Less than that.
>
> I know there are a lot of varibles here but I would like to know, the
> experinces that people have had.
>
>
> --
> View this message in context:
> http://www.nabble.com/Typical-Port-issues-for-C--%3EMono-tp19962814p19962814.html
> Sent from the Mono - General mailing list archive at Nabble.com.
>
> _______________________________________________
> Mono-list maillist  -  Mono-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-list/attachments/20081015/fd574ea9/attachment.html