Best practices for portable C# [closed]

Question

I am looking to write some C# code for linux/windows/mac/any other platform, and am looking for best practices for portable code.

Project mono has some great porting resources.

What are the best practices for portable C#?

Answer 1

I hate the term "Best practice" because it seems that some practices can be the best in any context, which is a risky thing, but I'll tell what I consider a "Good practice" for multi-platform code (and for most other type of development):

Use a continuous integration engine and build for all the target platforms all the time.

Sounds too complex? Well, if you really need to support multiple platforms, better to do it. No matter how careful you are with your code and library usage, if you test too late, you'll find yourself spending looong hours reworking big portions of the app.

Answer 2

I've actually used winforms and it was fine. It was BUTT UGLY, but it worked.

Obviously, don't use P/Invoke, or any win32 stuff like the registry. Also be aware of any third party DLL's. For example, we use a third party SQLite dll which actually contains native code in it which we have to swap out if we want to run on OSX/linux.