C# isn't really my cup of tea, but I've had reasonably good luck running (well-written) third-party C# code on Linux and OS X using Mono. What are some of the issues that make this reckless?
Mono had some issues with memory management that appear to make it less reliable for very long-running processes - I don't have first hand experience with that. The size of the community may also be an issue, since there are not many companies deploying enterprise applications on Mono and you may experience issues completely unique to your stack and have no other way to solve it than to redeploy on .NET.
Comments
C# isn't really my cup of tea, but I've had reasonably good luck running (well-written) third-party C# code on Linux and OS X using Mono. What are some of the issues that make this reckless?
Mono had some issues with memory management that appear to make it less reliable for very long-running processes - I don't have first hand experience with that. The size of the community may also be an issue, since there are not many companies deploying enterprise applications on Mono and you may experience issues completely unique to your stack and have no other way to solve it than to redeploy on .NET.