3 ms·

The answer to your latter question is: no. Only pretty trivial stuff is portable to Mono. I've tried it on every project I've worked on over the last 6 years to

by d0 13y ago

The answer to your latter question is: no. Only pretty trivial stuff is portable to Mono. I've tried it on every project I've worked on over the last 6 years to no avail. Show stopper every time.

andyjohnson0 13y ago
Interested in your experience. Were these projects desktop applications or server-side, or a mix of both?
- d0 13y ago
  Mix of both. The killer on the server-side is always stuff like missing WCF features, odd bugs with DI containers, missing API calls, slight behavioural differences etc. Client-side. No WPF and WinForms is dreadfully incomplete. It's a no go. If you start on Mono and deploy to .Net I imagine it'd work but no-one realistically does that these days. If they were going to do that, Java would be a better choice for the product.
  - danabramov 13y ago
    Well, client-side Microsoft has abandoned both (although of course they still run).
    - d0 13y ago
      They haven't abandoned any of them. We still have ATL, MFC, Win32, WPF, WinForms and now Metro. Not that I want to use any of them myself :)
Guillaume86 13y ago
Yes it's a big disapointment for me, my predilection language is C# and I would love to be able to code on linux... I wish one day microsoft will be forced to port/support .NET (at least server components) to linux but I'm not holding my breath...
- d0 13y ago
  I really don't want them to port it. I want to see Java 8!
  - CmonDev 13y ago
    Yeah, because lack of competition makes best stuff float to the top.
skrebbel 13y ago
This is nonsense. You just have to dev with Mono in mind from the start. Basically, don't use WPF and WCF and you're all set. I'm currently in a web app team with a C# backend. Two devs run Windows, one has a Mac, and one runs Ubuntu. It works great. And yes, we deploy to Linux using Docker.
- d0 13y ago
  See my comment "portable to mono". I agree with you but I wouldn't do it myself.
- hkarthik 13y ago
  "You just have to dev with Mono in mind from the start." You say that like it's the most trivial thing in the world. Most people attempting Mono have been loyal Windows-based .NET developers for years. Mono only has value for them if they can port their legacy apps from Windows and .NET to Mono.
- camus2 13y ago
  > You just have to dev with Mono in mind from the start. then it cannot replace .net .You can put it every ways you want serious C# and .net development is windows only. Mono doesnt run every C# library out there. The people pushing mono here dont have to face the consequences of that choice. It's easy for them to say "it just works", they wont be around when one realises it doesnt work. Dont use mono thinking it really works.It's an experiment.

by d0 13y ago

The answer to your latter question is: no. Only pretty trivial stuff is portable to Mono. I've tried it on every project I've worked on over the last 6 years to no avail. Show stopper every time.

andyjohnson0 13y ago

Interested in your experience. Were these projects desktop applications or server-side, or a mix of both?

d0 13y ago
Mix of both. The killer on the server-side is always stuff like missing WCF features, odd bugs with DI containers, missing API calls, slight behavioural differences etc. Client-side. No WPF and WinForms is dreadfully incomplete. It's a no go. If you start on Mono and deploy to .Net I imagine it'd work but no-one realistically does that these days. If they were going to do that, Java would be a better choice for the product.
- danabramov 13y ago
  Well, client-side Microsoft has abandoned both (although of course they still run).
  - d0 13y ago
    They haven't abandoned any of them. We still have ATL, MFC, Win32, WPF, WinForms and now Metro. Not that I want to use any of them myself :)

Guillaume86 13y ago

Yes it's a big disapointment for me, my predilection language is C# and I would love to be able to code on linux... I wish one day microsoft will be forced to port/support .NET (at least server components) to linux but I'm not holding my breath...

d0 13y ago
I really don't want them to port it. I want to see Java 8!
- CmonDev 13y ago
  Yeah, because lack of competition makes best stuff float to the top.

skrebbel 13y ago

This is nonsense. You just have to dev with Mono in mind from the start. Basically, don't use WPF and WCF and you're all set. I'm currently in a web app team with a C# backend. Two devs run Windows, one has a Mac, and one runs Ubuntu. It works great. And yes, we deploy to Linux using Docker.

d0 13y ago
See my comment "portable to mono". I agree with you but I wouldn't do it myself.
hkarthik 13y ago
"You just have to dev with Mono in mind from the start." You say that like it's the most trivial thing in the world. Most people attempting Mono have been loyal Windows-based .NET developers for years. Mono only has value for them if they can port their legacy apps from Windows and .NET to Mono.
camus2 13y ago
> You just have to dev with Mono in mind from the start. then it cannot replace .net .You can put it every ways you want serious C# and .net development is windows only. Mono doesnt run every C# library out there. The people pushing mono here dont have to face the consequences of that choice. It's easy for them to say "it just works", they wont be around when one realises it doesnt work. Dont use mono thinking it really works.It's an experiment.