Does Mono has everything

[Twig]

Hi,

Can I use strictly for C# development without missing anything from MS?

Twig

[Giuseppe Turitto]

As far as I know, the Mono project did a great job, but when it hit's
ASP.NET still far to be perfect. Also are many libraries that are not
complete. We did a prof of concept a year ago where we decided to port
a system that we created for Windows to the MacOSX users using Mono,
and when we try to compile the MS-C# code on the MacOSX using the Mono
Compiler, we had so many errors, we started to clean the code and adapt
our code to work, we never finished, after a week an a half cleaning
code and killing bugs, we decide to write the code from scratch. We
finished a week after we started. Lesson from the story, true
portability between platform still a myth. Different platform,
different architecture, different paradigms, different way to attack
the same problem.

Giuseppe Turitto

Twig wrote:

Hi,

Can I use strictly for C# development without missing anything from MS?

Twig

[Martin Z]

My understanding is that the reverse works pretty well - if you start
on Mono using the Mono implementation of WinForms and suchlike, then
when you port to win32 you arrive with minimum pain, since the problem
is more that MS provides a lot of additional functionality over the
limited copy Mono provides.

Giuseppe Turitto wrote:

As far as I know, the Mono project did a great job, but when it hit's
ASP.NET still far to be perfect. Also are many libraries that are not
complete. We did a prof of concept a year ago where we decided to port
a system that we created for Windows to the MacOSX users using Mono,
and when we try to compile the MS-C# code on the MacOSX using the Mono
Compiler, we had so many errors, we started to clean the code and adapt
our code to work, we never finished, after a week an a half cleaning
code and killing bugs, we decide to write the code from scratch. We
finished a week after we started. Lesson from the story, true
portability between platform still a myth. Different platform,
different architecture, different paradigms, different way to attack
the same problem.

Giuseppe Turitto

Twig wrote:

Hi,

Can I use strictly for C# development without missing anything from MS?

Twig

[Giuseppe Turitto]

Yes I agree, the reverse approach can be the best approach for a multi
platform Mono development. But the reality is that you will want to
approach the big guys first. Also it depends how you approach your
development, If you are interested in primarily write applications for
MacOsX then you better use stick on ObjectiveC, and if you need to
approach Windows users, then you can always try to port your C code, or
rewrite you App. If you want truly multi platform development then I
suggest JAVA, Anyway in both cases C# is only if your main development
goes to Windows users. I will not recommend the Mono solution for
anything beyond experimental or home brewed. We bite the bullet because
we thought it could be pretty neat using MONO. Never again. Anyway you
decide how you want to work.

Giuseppe Turitto

Martin Z wrote:

My understanding is that the reverse works pretty well - if you start
on Mono using the Mono implementation of WinForms and suchlike, then
when you port to win32 you arrive with minimum pain, since the problem
is more that MS provides a lot of additional functionality over the
limited copy Mono provides.

Giuseppe Turitto wrote:

As far as I know, the Mono project did a great job, but when it hit's
ASP.NET still far to be perfect. Also are many libraries that are not
complete. We did a prof of concept a year ago where we decided to port
a system that we created for Windows to the MacOSX users using Mono,
and when we try to compile the MS-C# code on the MacOSX using the Mono
Compiler, we had so many errors, we started to clean the code and adapt
our code to work, we never finished, after a week an a half cleaning
code and killing bugs, we decide to write the code from scratch. We
finished a week after we started. Lesson from the story, true
portability between platform still a myth. Different platform,
different architecture, different paradigms, different way to attack
the same problem.

Giuseppe Turitto

Twig wrote:

Hi,
>
Can I use strictly for C# development without missing anything from MS?
>
Twig

[William Stacey [C# MVP]]

Good to know. Just curious, what was the top couple things that you saw
most as issues during the port? tia

--
William Stacey [C# MVP]

"Giuseppe Turitto" <gi**************@gmail.comwrote in message
news:11**********************@i42g2000cwa.googlegr oups.com...
| Yes I agree, the reverse approach can be the best approach for a multi
| platform Mono development. But the reality is that you will want to
| approach the big guys first. Also it depends how you approach your
| development, If you are interested in primarily write applications for
| MacOsX then you better use stick on ObjectiveC, and if you need to
| approach Windows users, then you can always try to port your C code, or
| rewrite you App. If you want truly multi platform development then I
| suggest JAVA, Anyway in both cases C# is only if your main development
| goes to Windows users. I will not recommend the Mono solution for
| anything beyond experimental or home brewed. We bite the bullet because
| we thought it could be pretty neat using MONO. Never again. Anyway you
| decide how you want to work.
|
| Giuseppe Turitto
|
| Martin Z wrote:
| My understanding is that the reverse works pretty well - if you start
| on Mono using the Mono implementation of WinForms and suchlike, then
| when you port to win32 you arrive with minimum pain, since the problem
| is more that MS provides a lot of additional functionality over the
| limited copy Mono provides.
| >
| Giuseppe Turitto wrote:
| As far as I know, the Mono project did a great job, but when it hit's
| ASP.NET still far to be perfect. Also are many libraries that are not
| complete. We did a prof of concept a year ago where we decided to port
| a system that we created for Windows to the MacOSX users using Mono,
| and when we try to compile the MS-C# code on the MacOSX using the Mono
| Compiler, we had so many errors, we started to clean the code and
adapt
| our code to work, we never finished, after a week an a half cleaning
| code and killing bugs, we decide to write the code from scratch. We
| finished a week after we started. Lesson from the story, true
| portability between platform still a myth. Different platform,
| different architecture, different paradigms, different way to attack
| the same problem.
|
| Giuseppe Turitto
|
| Twig wrote:
| Hi,
| >
| Can I use strictly for C# development without missing anything from
MS?
| >
| Twig
|

[Arne Vajhøj]

Twig wrote:

Can I use strictly for C# development without missing anything from MS?

Not quite.

For details:

http://mono.ximian.com/class-status/mono-HEAD-vs-fx-2/

Arne

[Giuseppe Turitto]

They were too many, we had problem even with casting data type's. We
got to a moment that we had the feeling that something was wrong with
the Mono Installation. The major problems were at System Reflection and
System Remoting, also System Threading was a major headache.
William Stacey [C# MVP] wrote:

Good to know. Just curious, what was the top couple things that you saw
most as issues during the port? tia

--
William Stacey [C# MVP]

"Giuseppe Turitto" <gi**************@gmail.comwrote in message
news:11**********************@i42g2000cwa.googlegr oups.com...
| Yes I agree, the reverse approach can be the best approach for a multi
| platform Mono development. But the reality is that you will want to
| approach the big guys first. Also it depends how you approach your
| development, If you are interested in primarily write applications for
| MacOsX then you better use stick on ObjectiveC, and if you need to
| approach Windows users, then you can always try to port your C code, or
| rewrite you App. If you want truly multi platform development then I
| suggest JAVA, Anyway in both cases C# is only if your main development
| goes to Windows users. I will not recommend the Mono solution for
| anything beyond experimental or home brewed. We bite the bullet because
| we thought it could be pretty neat using MONO. Never again. Anyway you
| decide how you want to work.
|
| Giuseppe Turitto
|
| Martin Z wrote:
| My understanding is that the reverse works pretty well - if you start
| on Mono using the Mono implementation of WinForms and suchlike, then
| when you port to win32 you arrive with minimum pain, since the problem
| is more that MS provides a lot of additional functionality over the
| limited copy Mono provides.
| >
| Giuseppe Turitto wrote:
| As far as I know, the Mono project did a great job, but when it hit's
| ASP.NET still far to be perfect. Also are many libraries that are not
| complete. We did a prof of concept a year ago where we decided to port
| a system that we created for Windows to the MacOSX users using Mono,
| and when we try to compile the MS-C# code on the MacOSX using the Mono
| Compiler, we had so many errors, we started to clean the code and
adapt
| our code to work, we never finished, after a week an a half cleaning
| code and killing bugs, we decide to write the code from scratch. We
| finished a week after we started. Lesson from the story, true
| portability between platform still a myth. Different platform,
| different architecture, different paradigms, different way to attack
| the same problem.
|
| Giuseppe Turitto
|
| Twig wrote:
| Hi,
| >
| Can I use strictly for C# development without missing anything from
MS?
| >
| Twig
|