Honestly, I would go with creating an OSX app, iOS app and Windows app separately. NET) but you will still need a mac to compile the iOS / OSX versions, an iPhone/iPad/iPod touch to test on device, etc. One thing you won't find is a solution level package manager that you have in Visual Studio on Windows, so you can't manage packages across the solutions. its possible (and brand new) through Visual Studio and Mono (as far as I understood it is an open source implementation of. We got the similar sort of dialogue tailored for the Mac, shows us things like dependencies and results. So we might go out for example and say we want to add a web API client. button, then select Visual C > Cross-Platform > Mobile App (Xamarin.Forms). For example, what if we want to manage NuGet packages? We do have a packages node here, and we can either update all the packages or restore all the packages, add a project level, or we could add a package. Tutorials about the basics of creating Xamarin.Forms applications with Visual Studio and Visual Studio for Mac. There are a few things that I've found in using it, however, that are a little bit different and might throw you off. If you're a C Sharp developer, you're probably already very familiar with Visual Studio, and Visual Studio for Mac should feel very comfortable to you as your development environment.

Visual studio for mac xamarin tutorial