Search Unity

  1. Improved Prefab workflow (includes Nested Prefabs!), 2D isometric Tilemap and more! Get the 2018.3 Beta now.
    Dismiss Notice
  2. The Unity Pro & Visual Studio Professional Bundle gives you the tools you need to develop faster & collaborate more efficiently. Learn more.
    Dismiss Notice
  3. Improve your Unity skills with a certified instructor in a private, interactive classroom. Watch the overview now.
    Dismiss Notice
  4. Want to see the most recent patch releases? Take a peek at the patch release page.
    Dismiss Notice

MonoDevelop in 2017 create problems ??

Discussion in 'General Discussion' started by Nithin126, Jul 13, 2018.

  1. Nithin126

    Nithin126

    Joined:
    Sep 3, 2017
    Posts:
    9
    I want to use monodevelop in 2017 version.. Will it create any sort of problem while building or publishing in App Store ??
     
  2. Ryiah

    Ryiah

    Joined:
    Oct 11, 2012
    Posts:
    12,136
    No, and the reason it won't cause any of these problems is because the editor (monodevelop, visual studio, etc) is never responsible for building binaries or publishing. Both of these tasks are handled by Unity itself.
     
    Nithin126 and angrypenguin like this.
  3. Nithin126

    Nithin126

    Joined:
    Sep 3, 2017
    Posts:
    9
    Thank you @Ryiah , then how should I take the note of "Unity stopping Monodevelop support from v.2017 ??". What will it do to me ??
     
  4. Ryiah

    Ryiah

    Joined:
    Oct 11, 2012
    Posts:
    12,136
    Support for MonoDevelop was handled by custom code written and maintained by Unity. With support being stopped that code will no longer be provided. You can continue using MD as an editor but some of the features (eg debugging) will no longer work.

    Ideally you should start looking at alternative editors. Visual Studio Code is an excellent choice.

    https://code.visualstudio.com/docs/other/unity
     
    Nithin126 likes this.
  5. Nithin126

    Nithin126

    Joined:
    Sep 3, 2017
    Posts:
    9
    Thanks for your information, once again @Ryiah