Fact-checked by Grok 2 weeks ago

MonoDevelop

MonoDevelop was an open-source (IDE) designed for developing cross-platform applications using the Mono implementation of , with primary support for languages including C#, F#, VB.NET, and Vala on , Windows, and macOS. Key features included advanced code editing with real-time parsing, autocompletion, and for C# and VB.NET; an integrated for both managed and native code; a configurable workbench allowing custom layouts, key bindings, and external tool integration; and specialized tools such as a GTK# visual designer, project templates with an embedded XSP , control integration, frameworks, and application packaging capabilities. Originally initiated as an extension of the IDE to support Mono, MonoDevelop reached its first stable release (version 1.0) in March 2008, focusing initially on and applications for and macOS users. It evolved to facilitate porting .NET applications from Microsoft to open-source environments, enabling single-codebase development across platforms. It was rebranded as Xamarin Studio in 2013 before evolving into for Mac. The IDE became integral to the Xamarin ecosystem after Novell's acquisition of the Mono project in 2003 and subsequent developments, serving as the core foundation for Xamarin Studio (introduced in 2011) and later Visual Studio for Mac (launched in 2016 by Microsoft following its acquisition of Xamarin in 2016). MonoDevelop was also bundled as the default IDE with Unity game engine versions prior to 2018. Development continued until early 2020, with the last official (version 7.6) in 2018; the project's repository was archived in October 2021, marking its discontinuation and shift to read-only status, though community forks like DotDevelop have attempted to revive it. Following the retirement of for Mac in August 2024, MonoDevelop's legacy influences persist in Microsoft's .NET cross-platform tooling, but no active maintenance is provided.

History

Origins and Initial Development

The Mono project, launched on June 30, 2001, by and his team at Ximian, sought to implement an open-source version of Microsoft's for and other systems, providing a runtime environment for C# and related languages on non-Windows platforms. As a key component of this initiative, MonoDevelop was developed as the project's primary (IDE), tailored for cross-platform .NET development with a focus on integration. In late 2003, developers within the Mono community initiated MonoDevelop by forking and migrating the Windows-based SharpDevelop IDE, originally created by Mike Krüger and the Alpha Sierra Papa team, to make it suitable for Linux users seeking a C# development tool with features like IntelliSense. Pedro Abelleira led the initial porting effort, extracting SharpDevelop's core editor and IntelliSense engine and rewriting the user interface using Gtk# instead of Windows.Forms, as the latter was not yet available in Mono. Todd Berman then assumed maintenance responsibilities, aiming for basic usability by the end of 2003, while the project emphasized GNOME desktop integration to align with Linux workflows. The first alpha release of MonoDevelop arrived in , concentrating on essential code editing capabilities for Mono and .NET applications on non-Windows platforms, including basic and through the ported components. Development progressed with contributions from developers like Lluis Sanchez, who integrated Glade-3 for design support, though early versions faced delays in stabilizing the interface due to evolving Mono libraries. MonoDevelop achieved a stable milestone with its 1.0 release on March 14, 2008, marking the IDE's readiness for broader use and introducing a customizable workbench, configurable key bindings (including schemes mimicking and ), and foundational support for C# projects with and refactoring tools. Despite these advances, early versions were constrained by limited features relative to Microsoft's , such as incomplete debugging and deployment options, and the team prioritized GNOME-centric enhancements to overcome platform-specific hurdles in environments.

Growth and Community Adoption

Following its initial development, MonoDevelop experienced steady growth through a series of major releases that enhanced its functionality and accessibility, driven by community contributions and evolving needs in the open-source ecosystem. The release of MonoDevelop 2.0 in March 2009 marked a significant advancement, introducing per-project and solution policies for better , improved capabilities, and enhanced MSBuild integration to streamline project building across diverse environments. Earlier betas in had laid groundwork with features like improved packaging systems and smart indentation for C#, reflecting iterative refinements from user feedback and developer input. This version solidified MonoDevelop's role as a robust for C# development on , where it originated as the primary platform. Subsequent updates further expanded its scope. MonoDevelop 2.2, released in December 2009, officially added support for Windows and macOS, moving beyond Linux-centric use and enabling broader cross-platform development for .NET applications. MonoDevelop 2.4, arriving in 2010, introduced tools like the Navigate To dialog for faster file and symbol navigation, alongside refinements in and editor , which encouraged adoption among developers building Mono-based and web applications. efforts played a key role, with bug-fixing marathons and add-in contributions enhancing stability and extensibility during this period. Language support grew through initial bindings for additional .NET languages, broadening its appeal. By 2008, with MonoDevelop 1.0, it included native handling for Visual Basic .NET projects, allowing import and modification of VB.NET files alongside C#. The first F# language binding arrived in November 2010, providing autocompletion, tooltips, and refactoring via the F# compiler service, which integrated seamlessly into the IDE's workflow. These additions, contributed by the open-source community, positioned MonoDevelop as a versatile tool for multi-language .NET projects in Linux-dominated environments. A pivotal boost came from its integration with Unity Technologies in 2011, when MonoDevelop became the default C# scripting IDE bundled with the Unity game engine, significantly increasing its visibility and use among game developers worldwide. This partnership exposed the IDE to a large Windows and macOS user base via Unity's popularity, fostering contributions that improved scripting support and debugging for game development. The year 2012 saw the release of MonoDevelop 3.0 in May, featuring a revamped add-in system for easier extensibility and integrated support for systems like and SVN, which facilitated collaborative development in open-source projects. The update also overhauled the C# engine using the Mono Compiler Service for more accurate semantic analysis, alongside performance optimizations that reduced load times and improved responsiveness. By the end of its independent phase in , MonoDevelop had garnered substantial adoption within the open-source , particularly for developing Mono-based applications in ecosystems, where it served as a go-to for thousands of developers porting and maintaining cross-platform .NET software. Its growth was evidenced by active participation in community-driven enhancements, such as localization add-ins and database tools, underscoring its maturation into a cornerstone of non-Microsoft .NET development.

Acquisitions, Rebranding, and Discontinuation

In 2011, assumed stewardship of the Mono project, which included the open-source IDE, and subsequently released Xamarin 2.0 in 2013, rebranding MonoDevelop as Xamarin Studio to emphasize support for cross-platform mobile development using C# and .NET. On February 24, 2016, Microsoft announced its acquisition of Xamarin, integrating the company's tools into its ecosystem and further rebranding Xamarin Studio as Visual Studio for Mac later that year, with the MonoDevelop codebase serving as its foundation while shifting primary focus to macOS and iOS development. Under 's ownership, for received continued updates, culminating in a major overhaul with the release of version 17.0 in May 2022, which adopted a fully 64-bit architecture, native macOS UI, and optimization for processors running on .NET 6. announced the discontinuation of for on August 30, 2023, with support ending on August 31, 2024, citing resource shifts toward cross-platform .NET tools like and the C# Dev Kit extension, as well as overlap in functionality that made a dedicated IDE less essential. The last specific maintenance for the original MonoDevelop codebase effectively ceased around January 2020 with its last commit on January 29; its repository was archived on October 4, 2021, without further builds or updates.

Features

Core IDE Functionality

MonoDevelop's core functionality centered on a flexible and extensible designed to enhance developer productivity across diverse workflows. The supported customizable layouts for workspace pads, , and windows, enabling users to tailor the interface to their preferences through the View/Layouts menu or a quick-switch selector. Key bindings were fully configurable via Edit/Preferences, accommodating schemes like or , and allowing multi-state bindings for complex commands. Additionally, integration with external tools was facilitated through preferences and add-in extensions, while window management features permitted docking, floating, and tabbed arrangements for efficient multitasking. At the heart of its editing capabilities lay advanced text editing tools that streamlined code authoring. was provided for supported languages, visually distinguishing elements like keywords, strings, and comments to improve . allowed collapsing expandable regions, such as methods or classes, to manage large files effectively. Code templates, functioning as snippets, could be expanded using the TAB key and customized per file extension for repetitive code patterns. Most prominently, intelligent offered contextual suggestions for namespaces, types, methods, fields, 'as' and 'new' keywords, method parameters, and even C# directives, reducing typing errors and accelerating development. Project and solution management formed a foundational pillar, enabling seamless organization and building of .NET applications using the Mono runtime. Users could create multi-file solutions comprising multiple projects, with built-in templates for common types such as console applications, class libraries, web applications, and test libraries in languages like C#, VB.NET, and . Build integration supported Mono versions 1.1, 2.0, and later, including multiple configurations, dependency resolution, and command-line tools like 'mdtool build' for automated and deployment. This setup facilitated and maintenance of complex solutions without external build systems. Version control integration was embedded to support collaborative development directly within the . Built-in support included (SVN) for operations like checkout, commit, log viewing, and revert, along with automated generation based on customizable policies. Starting with version 2.6, integration provided similar core commands, including diff views and commit tools, extending capabilities to distributed workflows. support was available through dedicated add-ins, enabling comparable functionality for repository management and history tracking. Cross-platform availability ensured broad accessibility, with native support for (optimized for environments), Windows, and macOS. Installer packages were provided for each platform via the official download page, allowing straightforward setup and consistent feature parity across operating systems, though some platform-specific optimizations, like iPhone project targeting, were limited to macOS.

Language and Framework Support

MonoDevelop provided robust support for C# as its primary language, offering advanced features such as IntelliSense-like code completion, refactoring tools including rename and extract method operations, and compilation targeting the Mono runtime. These capabilities enabled developers to build and maintain .NET applications efficiently across Linux, Windows, and macOS platforms. In addition to C#, MonoDevelop supported other .NET languages including F#, Visual Basic .NET, Boo, and Java via the IKVM add-in, with dedicated project templates available for each to facilitate quick setup and development. F# and Visual Basic .NET received full support across all platforms, while Boo and Java were primarily available on Linux. The integrated with key frameworks to support diverse application types, including for web development with full and testing via the XSP Mono , Gtk# for cross-platform desktop GUI applications through its visual designer, for game scripting in C#, and early Xamarin.Mobile components for shared cross-platform logic. MonoDevelop allowed building and debugging against various Mono runtime versions, from 1.1 to 6.x, including profile-specific support for mobile (such as ) and server environments. Its extensible add-in system further enabled custom language bindings and tools, allowing developers to extend support for additional languages or integrate specialized functionality.

UI Design and Debugging Tools

MonoDevelop provided specialized tools for designing user interfaces and debugging applications, enhancing the development workflow for .NET and Mono-based projects. The UI Builder, known as Stetic, served as an integrated drag-and-drop designer specifically for Gtk# applications, allowing developers to visually construct graphical interfaces by placing widgets such as VBoxes, Menu Bars, TextViews, and Scrolled Windows from a palette onto a canvas. This tool supported layout organization through containers and enabled property adjustments via a dedicated Widget Properties pad, while the Widget Tree facilitated navigation among elements. Stetic automatically generated C# code for forms and controls, creating private fields for widgets in a designer file and adding signal handler skeletons—such as for menu actions like "OnOpen" or "OnExit"—directly into the main class, streamlining the connection between visual design and functional code. As the official GUI designer for Gtk# within MonoDevelop, Stetic emphasized seamless integration for cross-platform desktop application development. The integrated debugger in MonoDevelop supported both managed and native code execution analysis, leveraging the Mono Soft Debugger for .NET applications and GDB for native ones. The Mono Soft Debugger, available since Mono 2.6 and tightly coupled with MonoDevelop, enabled core debugging operations including setting s at sequence points, examining call stacks by capturing state during managed-to-native transitions, and performing step-through execution via single-stepping mechanisms like signal-based suspension. While watch variables offered limited support due to thread suspension constraints, the debugger facilitated attach-to-process scenarios and was particularly useful for MonoTouch/ development. GDB integration, introduced in early versions like MonoDevelop 2.0 Alpha 2, allowed debugging of native components with features such as management and variable inspection, complementing the Soft Debugger for mixed-mode applications. Overall, this dual-debugger approach supported languages like C# and C++ by providing step-in, step-over, and step-out controls alongside runtime evaluation. To aid in code exploration and maintenance, MonoDevelop included and class browsers as navigational tools for .NET assemblies and project structures. The , debuted in MonoDevelop 2.0, permitted inspection of assembly contents by displaying type definitions, member details, and Intermediate Language () code for methods, thereby revealing without external tools. It supported dependency exploration through reference visualization, helping developers trace inter-assembly relationships and understand binary compositions. The Class Browser complemented this by providing a hierarchical view of classes, interfaces, and members within projects or loaded assemblies, enabling quick navigation and refactoring previews as part of the IDE's core analysis features. Unit testing integration in MonoDevelop featured a built-in runner that automated test discovery, execution, and result visualization for frameworks like and MbUnit, promoting practices. The add-in, integrated via MonoDevelop's extension system, allowed developers to run tests directly from the , displaying pass/fail outcomes in a dedicated panel with stack traces for failures and coverage metrics where supported. MbUnit compatibility extended this capability to more advanced testing scenarios, such as parameterized tests, through the same runner interface, ensuring compatibility with Mono's runtime for cross-platform validation. This setup facilitated seamless workflow from writing tests in supported languages to immediate feedback without leaving the . The help system in MonoDevelop incorporated Monodoc for comprehensive .NET API documentation and custom help files, accessible via an integrated viewer. Monodoc integration, present from MonoDevelop 1.0 onward, browsed XML-generated documentation for Mono assemblies, providing context-sensitive help on classes, methods, and namespaces directly within the IDE. Developers could extend this with project-specific documentation projects, using Monodoc tools to compile and query custom assemblies, enhancing knowledge accessibility during UI design and debugging tasks.

Legacy and Successors

Xamarin Studio

Xamarin Studio emerged as the direct rebranded successor to MonoDevelop in February 2013, when released version 2.0 of its platform and rebranded the open-source to align with its development focus. Retaining the core architecture of MonoDevelop, Xamarin Studio introduced specialized project templates for and applications, leveraging the Xamarin.iOS and Xamarin.Android frameworks to enable C#-based native development. This followed Xamarin's assumption of MonoDevelop's stewardship, building on contributions from its founders who originated the Mono project. A key enhancement was the creation of a unified IDE environment supporting both Xamarin.iOS and Xamarin.Android workflows, which included built-in device simulators for testing on virtual and hardware, as well as streamlined deployment tools for provisioning devices, signing apps, and submitting to app stores. These additions addressed the challenges of cross-platform mobile development by providing a single interface for building, debugging, and deploying apps across ecosystems, reducing the need for separate tools or environments. The version 5.x series, released progressively from 2014 to 2015, brought further refinements tailored to mobile workflows, such as deeper integration with for seamless native tool chaining (e.g., with ), a visual XAML designer for .Forms that allowed drag-and-drop creation of cross-platform user interfaces shared across , , and Windows, and connectivity to cloud build services for remote compilation on platform-specific hardware without requiring local agents for all builds. These updates emphasized efficiency in UI prototyping and distributed development, making Xamarin Studio more accessible for teams targeting multiple mobile platforms. As adoption grew, Xamarin Studio's user base transitioned from general-purpose Mono and .NET developers to those specializing in applications, facilitated by its Community edition for individual and open-source projects alongside a paid edition offering advanced diagnostics, priority support, and extended licensing for use. This model broadened while monetizing professional features, aligning with the rising demand for C#-driven tools. Technically, Xamarin Studio preserved substantial continuity with MonoDevelop, drawing largely from its established codebase for core IDE functions like code editing, , and add-in extensibility, but underwent optimizations to prioritize macOS as the primary host platform, with cross-platform support for Windows and limited Linux compatibility via MonoDevelop forks. This evolution positioned Xamarin Studio as a mobile-centric until its transition under in 2016.

Visual Studio for Mac

Visual Studio for Mac was launched in November 2016 as a preview following Microsoft's acquisition of earlier that year, serving as a full port of the IDE to macOS and building upon the foundations of MonoDevelop and Xamarin Studio. This rebranding and expansion from its predecessor, Xamarin Studio, enabled developers to create cross-platform applications for , , macOS, and more directly on macOS hardware. The reached general availability in 2017 with version 7.0, introducing initial support for .NET Core 2.0, which allowed for building and running cross-platform .NET applications on macOS. In early 2020, version 8.4 added integration for Server projects, enabling the creation, building, running, and debugging of web applications using and server-side rendering within the . By 2022, version 17.0 marked a significant update with a full transition to a 64-bit architecture, native support for .NET 6, optimization for processors, and tools for development, including project templates and debugging for cross-platform UI applications targeting .NET 6 and later .NET 7. Key enhancements during its evolution included comprehensive debugging capabilities for applications, seamless integration with services for deployment and management, and built-in templates for cross-platform .NET projects that streamlined development for web, mobile, and desktop scenarios. Microsoft announced the discontinuation of for Mac in August 2023, with updates ceasing after version 17.6 and support ending on August 31, 2024, in line with the Modern Lifecycle Policy. Post-retirement, no new features or updates are provided, but existing installations continue to function for maintenance of current projects, prompting users to migrate to alternatives like with .NET extensions.

Post-Discontinuation Alternatives

Following the discontinuation of Visual Studio for Mac in August 2024, Microsoft recommends Visual Studio Code (VS Code) as the primary alternative for .NET development on macOS and other platforms. VS Code, combined with the free C# Dev Kit extension (which incorporates OmniSharp for IntelliSense and project management), provides a lightweight, cross-platform environment supporting .NET 8 and later versions, including debugging, refactoring, and testing capabilities. This setup enables full .NET MAUI development for cross-platform apps, with native support for Apple Silicon processors, ensuring efficient performance on modern Macs without virtualization overhead. Other professional IDEs include , a paid cross-platform tool that excels in advanced refactoring, code analysis, and .NET ecosystem integration, making it suitable for complex projects transitioning from MonoDevelop-era workflows. Rider supports .NET 8+, , and natively, offering a more feature-rich experience than VS Code for users needing deep functionality. For those requiring the full IDE, suggests running the Windows-only version via virtualization tools like Parallels or cloud-based options such as Microsoft Dev Box, allowing Mac and Linux users to access enterprise-grade features while maintaining license compatibility. Community efforts to sustain MonoDevelop include the DotDevelop fork, which builds on the original to improve compatibility and adapt to newer .NET versions, though it remains in early development without major new features. Legacy MonoDevelop 7.x packages are still available through distribution repositories like Fedora's, but they lack updates for .NET 8+ and are recommended only for maintaining older projects. Microsoft provides detailed migration guidance for porting Visual Studio for Mac projects to VS Code, covering solution file adjustments, extension equivalents for UI design (e.g., .NET tools), and setup to minimize disruptions. This shift aligns with the broader .NET ecosystem's focus on .NET 8+ and , where alternatives like VS Code and ensure continued cross-platform development without reliance on discontinued tools.

References

  1. [1]
    MonoDevelop | MonoDevelop
    MonoDevelop enables developers to write desktop and web applications on Linux, Windows, and macOS, and supports multiple languages like C# and F#.Download · Development · Screenshots · Help
  2. [2]
    Development Environments - Mono Project
    MonoDevelop is a Mono/C# Integrated Development Environment for Windows, Linux and macOS. It parses your C# and VB programs as you type them.
  3. [3]
    MonoDevelop 1.0 has been Released - Miguel de Icaza - tirania.org
    Mar 14, 2008 · MonoDevelop 1.0 is designed mostly for Linux developers creating Gnome and ASP.NET applications but MonoDevelop is also available for MacOS users.
  4. [4]
    Introducing Visual Studio for Mac | Microsoft Learn
    Jan 29, 2019 · Like Xamarin Studio, Visual Studio for Mac is based on the open source MonoDevelop IDE, which is actively developed by Microsoft. It's ...
  5. [5]
    Visual Studio and Unity 2018.1, even better together
    May 10, 2018 · With this new release, Visual Studio for Mac is now included in the installer, instead of MonoDevelop on a Mac. Download and Install Unity ...<|control11|><|separator|>
  6. [6]
    Download - MonoDevelop
    Download. The latest MonoDevelop release is: 7.6 (7.6.9.22). Source code is available on GitHub (viewing only) or as a Tarball.
  7. [7]
    MonoDevelop is a cross platform .NET IDE - GitHub
    Oct 4, 2021 · This project has not been built nor maintained since January 2020 and has been archived. If you are interested in working on the project, ...Missing: official | Show results with:official
  8. [8]
    What happened to Visual Studio for Mac | Microsoft Learn
    Sep 5, 2024 · Visual Studio for Mac has been retired as of August 31, 2024 in accordance with Microsoft's Modern Lifecycle Policy. Visual Studio for Mac ...Support Timeline · Alternative Options For... · Get Support<|control11|><|separator|>
  9. [9]
    History - Mono Project
    Here are some historical data points about Mono: Early Posts#. Mono and GNOME, the long reply Local Copy · Mono early history Local Copy. Milestones#. 2001#.Missing: origins development 2003-2005
  10. [10]
    FAQ | MonoDevelop
    MonoDevelop was originally a port of the SharpDevelop IDE to Gtk#, but it has evolved a lot since the initial port. There are numerous goals that MonoDevelop ...What Is Monodevelop? · Troubleshooting · Monodevelop Fails To Start...Missing: origins history 2003-2005
  11. [11]
    MonoDevelop 1.0 Released
    The MonoDevelop team is proud to announce the release of MonoDevelop 1.0. MonoDevelop is a GNOME IDE primarily designed for C# and other .NET languages.Features · Source Code Editing And... · Visual Designer For GtksharpMissing: origins | Show results with:origins
  12. [12]
    MonoDevelop 2.0 Released
    The MonoDevelop team is proud to announce the release of MonoDevelop 2.0. MonoDevelop is a GNOME IDE primarily designed for C# and other .NET languages.Missing: 2009 2012<|separator|>
  13. [13]
    Old News - MonoDevelop
    The first MonoDevelop 2.0 beta release includes per-project/solution policies, better support for code completion, improved support for MSBuild, and many other ...Missing: history | Show results with:history
  14. [14]
    https://www.monodevelop.com/documentation/release-notes/monodevelop-2.2-released/
  15. [15]
    MonoDevelop 2.4 Released
    The MonoDevelop team is proud to announce the release of MonoDevelop 2.4. MonoDevelop is an IDE primarily designed for C# and other .NET languages.Missing: 2009 | Show results with:2009
  16. [16]
    F# in MonoDevelop and cross-platform web sites & screencasts
    Nov 16, 2010 · The first version of the F# language binding for MonoDevelop is now available. Using the F# compiler service, it provides autocompletion, ...
  17. [17]
    Q&A with Lluis Sanchez, Project Manager of MonoDevelop - InfoQ
    Nov 3, 2011 · Many of the users come from Unity, which bundles MonoDevelop. Unity has many Windows users. · There are many more developers (in general) on ...
  18. [18]
    Release Notes for MonoDevelop 3.0
    New Features and Improvements# · New C# code completion engine · Virtual indent mode in the text editor · New MonoMac addin · Visual UI Designer for Mono for ...Missing: 2012 | Show results with:2012
  19. [19]
    What's new in MonoDevelop 3.0
    The major focus of MonoDevelop 3.0 is a new C# code completion engine, which provides more accurate and reliable code completion and navigation.Missing: 2012 | Show results with:2012
  20. [20]
    Xamarin 2.0 reviewed: iOS development comes to Visual Studio
    Xamarin's own IDE is a good alternative. The company says it took MonoDevelop "back to the drawing board." The result is Xamarin Studio, an ...
  21. [21]
    SD Times Blog: Xamarin acquisition will take Microsoft to other ...
    Feb 24, 2016 · Soon thereafter, in 2013, Xamarin released Xamarin 2.0, which rebranded MonoDevelop as Xamarin Studio. This release also added support to ...
  22. [22]
    Microsoft to acquire Xamarin and empower more developers to build ...
    Feb 24, 2016 · Microsoft has signed an agreement to acquire Xamarin, a leading platform provider for mobile app development.<|separator|>
  23. [23]
    Microsoft makes Visual Studio for Mac generally available - ZDNET
    May 10, 2017 · Visual Studio for Mac is not a port of Visual Studio for Windows; it's a rebranded version of Xamarin Studio integrated development environment ...<|separator|>
  24. [24]
    Visual Studio 2022 for Mac is now available
    May 23, 2022 · This is the fastest Visual Studio for Mac version yet with an all new native macOS UI, fully running on .NET 6, and optimized for Apple Silicon ...
  25. [25]
    Visual Studio for Mac Retirement Announcement
    Aug 30, 2023 · Visual Studio for Mac was retired on August 31, 2024 in accordance with Microsoft's Modern Lifecycle Policy.
  26. [26]
    Feature List | MonoDevelop
    Native support for Visual Studio 2005 projects#. The following project types can be opened and modified: C#; Visual Basic .NET; ASP.NET. Import VS 2003 project#.
  27. [27]
    What's new in MonoDevelop 2.6
    The version control subsystem in MonoDevelop now supports GIT. The basic version control commands already available for the Subversion support are now available ...
  28. [28]
    Version Control - MonoDevelop
    Support for new version control systems ; Support for GIT. Completed, Critical ; Support for Mercurial. Pending, Normal ; Spell Checking, Pending, Normal ...
  29. [29]
    MonoDevelop - Unity - Manual
    MonoDevelop is the integrated development environment (IDE) supplied with Unity. An IDE combines the familiar operation of a text editor with additional ...
  30. [30]
    Mono For Android - MonoDevelop
    Xamarin allows developing Android applications using Mono. There is an addin for MonoDevelop that allows building Mono for Android applications with ...
  31. [31]
    Compatibility - Mono Project
    The easiest way to describe what Mono currently supports is: Everything in .NET 4.7 except WPF, WWF, and with limited WCF and limited ASP.NET async stack.
  32. [32]
    Language Addins - MonoDevelop
    There are a number of extension points that need to be implemented when creating a Language Addin for MonoDevelop. 1. Stub out the addin#.
  33. [33]
    Stetic GUI Designer - MonoDevelop
    This tutorial will demonstrate how to create the layout of the GUI, including the menu, and how to link this GUI to the underlying software.
  34. [34]
    Stetic - Mono Project
    May 24, 2010 · Stetic is the GUI designer for creating Gtk# applications. To develop Gtk# interfaces with Stetic, users should download and use MonoDevelop.
  35. [35]
    Soft-Mode Debugger - Mono Project
    The Mono Soft Debugger first became available with Mono 2.6 and is primarily used today with Mono on the iPhone and is used from the MonoDevelop IDE.
  36. [36]
    Release notes for MonoDevelop 2.0 Alpha 2
    There is support for two debuggers: MDB (the Mono debugger, which allows debugging managed applications), and GDB (which allows debugging native applications).
  37. [37]
    Xamarin 2.0 Brings a New IDE, Visual Studio Add-in for iOS and a ...
    One of the new features introduced with Xamarin 2.0 is the Component Store. Xamarin has built a framework for creating, sharing and reusing components directly ...
  38. [38]
    Paket Support in Xamarin Studio - Matt Ward
    More information on all the changes in Xamarin Studio 5.9.2 can be found in the release notes. NuGet 2.8.5 support. Xamarin Studio now supports NuGet 2.8.5.
  39. [39]
    Build a Cross-Platform UI with Xamarin.Forms - CODE Magazine
    Feb 13, 2015 · It provides a way to write project code in C# and produce an app that runs on Android, iOS, and Windows devices. In the early days of Xamarin, ...
  40. [40]
    Microsoft officially launches the first preview of Visual Studio for Mac
    Nov 16, 2016 · You can now use Visual Studio for Mac to develop for apps for iOS, Android, Windows and macOS. You can download the preview of Visual Studio for Mac here.
  41. [41]
    Xamarin - Wikipedia
    ... Xamarin 2.0 based on the open source project MonoDevelop. In ... In 2013, Xamarin acquired the mobile application testing platform LessPainful.
  42. [42]
    Visual Studio for Mac 'retired': From open source, to ... - devclass
    Aug 31, 2023 · Microsoft is freezing development of Visual Studio for Mac (VS Mac), with support ending on August 31 2024.
  43. [43]
    Visual Studio 2017 Version 15.5, Visual Studio for Mac Released
    Dec 4, 2017 · Updater support for .NET Core. Visual Studio for Mac will now check to see if the .NET Core 2.0 SDK is installed when checking for updates. If ...Missing: initial | Show results with:initial
  44. [44]
    Visual Studio 2019 for Mac version 8.4 is now available
    Jan 8, 2020 · Although there is feature parity between VS on Mac and VS on Windows ... MonoDevelop has been taken away from Linux and turned into a ...
  45. [45]
    visual studio for mac debugging asp.net core project - Stack Overflow
    Jul 19, 2017 · If you create an ASP.NET Core project from within Visual Studio for Mac, you can see it debugs quite well (at least on my machine).
  46. [46]
    Visual Studio for Mac - Microsoft Azure
    The macOS integrated developer environment (IDE) designed for creating powerful, scalable .NET applications for Azure.
  47. [47]
    Visual Studio With GitHub Copilot - AI Pair Programming
    Sep 26, 2023 · GitHub Copilot is a coding assistant powered by Artificial Intelligence (AI), which can run in various environments and help you be more efficient in your ...
  48. [48]
    Visual Studio 2022 - 17.6 Now Available - Microsoft Developer Blogs
    May 16, 2023 · If you're still chasing down a few bugs in your code, Visual Studio version 17.6 answers the call with new debugger & diagnostics capabilities.
  49. [49]
    Visual Studio for Mac Retirement Announcement - Visual Studio Blog
    Aug 30, 2023 · The current version was a re-branding of Xamarin Studio from their acquisition of Xamarin and they kinda just let it rot compared to the money and people ...Microsoft is discontinuing Visual Studio for Mac after major overhaulMicrosoft acquired Xamarin : r/programming - RedditMore results from www.reddit.com
  50. [50]
    .NET MAUI - Visual Studio Marketplace
    The .NET Multi-platform App UI (MAUI) extension gives you the tools you need to build beautiful, performant, cross-platform apps anywhere you write code.
  51. [51]
    Rider: The Cross-Platform .NET IDE from JetBrains
    JetBrains Rider is a truly cross-platform IDE, providing a seamless development experience across Windows, macOS, and Linux. With added support for Android, iOS ...Download Rider · Buy Rider: Pricing and... · What's New in Rider 2025.2 · Features
  52. [52]
    dotdevelop/dotdevelop: MonoDevelop is a cross platform .NET IDE
    This is an effort to get MonoDevelop open sourced again. DotDevelop will hopefully be a full-featured integrated development environment (IDE) for .NET using ...
  53. [53]
    https://packages.fedoraproject.org/pkgs/monodevelop/monodevelop/