You can do it if you install Mono, the alternative CLR implementation, on Mac OS X:.Mono supports.NET BCL and part of non-standard.NET FCL, and it includes System.Windows.Forms. Then you can develop the applications on either Windows, or MAC. On Windows, you can use.NET or Mono, Visual Studio, or SharpDevelop, or MonoDevelop IDE. On Mac, you can use MonoDevelop. In all cases you can use the same assemblies for.NET, Mono for Windows, or Mono for Mac, without recompilation.
![](/uploads/1/2/8/0/128072342/472851133.jpg)
![Forms Forms](/uploads/1/2/8/0/128072342/226567938.png)
However, you will face some incompatibilities.One nice way to do development on Windows would be developing and testing everything on.NET and then testing it for Mono for Windows, and, in case of incompatibilities, fix them and test on Mono again. This way, you can do essential inner development cycle on Windows only. If some code works well on Mono for Windows, additional problems with Mono for other platforms are much less likely.See also:,.Now, more problems: Mono is good for many platforms, but Apple platforms is notoriously hostile to the 'foreigners'. Even when you successfully develop correctly working Windows Forms application, it will look foreign on Mac; in particular, you will see that the standard Mac menu on top of the desktop is shown as always, but is unrelated to your application, which may have it's own main menu, like in 'normal' Windows Forms applications.Can you develop Mono applications to behave natively on Mac. Yes, but they won't be compatible with Windows.
C is a general-purpose, high-level language that was originally developed by Dennis M. Ritchie to develop the UNIX operating system at Bell Labs. C was originally first implemented on the DEC PDP-11 computer in 1972.
Well.all you really need is a text editor and a C# compiler.but it's hard work!There is a version of VS that works on Macs natively: - but AFAIK that only supports ASP and Cloud apps, not WinForms.I'm really not sure it's a good idea, compared with the PC or Windows-in-a-VM, simply because you are going to need one or the other of those to test you code as your write it anyway! And as for debugging.you pretty much want VS running anyway.:laugh:Me? I'd stick with a PC (they aren't expensive compared to a Mac) and a copy of VS Community edition (licence permitting) or go the VM route - it'll be a lot simpler and easier to debug. When answering a question please:. Read the question carefully.
Understand that English isn't everyone's first language so be lenient of badspelling and grammar. If a question is poorly phrased then either ask for clarification, ignore it, oredit the question and fix the problem. Insults are not welcome. Don't tell someone to read the manual. Chances are they have and don't get it.Provide an answer or move on to the next question.Let's work to help developers, not make them feel stupid.
![](/uploads/1/2/8/0/128072342/472851133.jpg)