Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice

Bug NotSupportedException: Visual Studio Tools: method GetMonoIslands not found on InternalEditorUtility

Discussion in 'Editor & General Support' started by JasperByrne, Oct 15, 2022.

  1. JasperByrne

    JasperByrne

    Joined:
    Jul 22, 2017
    Posts:
    7
    Hi there,
    I have an issue where I've upgraded my project from 2019 to 2021 LTS, and everything is running smoothly except this one problem. Every time the Editor loads, I get this error:
    upload_2022-10-15_11-54-34.png

    When I run the project, it pauses and the error is triggered again. I am able to switch from the default external tools settings to Visual Studio 2019
    upload_2022-10-15_11-55-33.png

    to
    upload_2022-10-15_11-55-56.png

    ... however, whenever I do this and run the project in the editor, the External Script Editor pulldown reverts to the UnityVS.OpenFile setting and the error is triggered again.

    It doesn't affect the running of the game, but it's very inconvenient because I can never double click code paths in the log and launch VS without resetting this setting again and again.

    What I've tried:
    - reinstalling VS 2019 and 'tools for Unity'
    - uninstalling my old VS 2017
    - reinstalling the VS Tools package

    I can find no mention of this specific error on the internet so I hope someone might be able to help!

    Thanks.
     
  2. JasperByrne

    JasperByrne

    Joined:
    Jul 22, 2017
    Posts:
    7
    Tried out VS2022 but the same issue.

    I've also noticed that the Visual Studio Tools menu is stuck on: upload_2022-10-15_12-38-50.png

    I tried reinstalling and then removing VS2017 and the tools for Unity (as I haven't had it installed for some years), after removing VS2019 and 2022 tools, and finally reinstalling 2022 tools. But nothing will stop the menu referring to VS2017. As far as I can tell I've blitzed my system of VS2017 so I don't know where it's getting this from.
     
  3. trangiusarien

    trangiusarien

    Joined:
    Sep 15, 2017
    Posts:
    1
    I am also affected by this error. Updated from Unity 2019.2.13f1 to 2022.1.20f1. I created a new project and imported assets one by one into it, that worked.
     
  4. flashmandv

    flashmandv

    Joined:
    Mar 26, 2015
    Posts:
    154
    @JasperByrne did you managed to fix the issue?
    I'm having it in Unity 2021.3.27 but I'm unable to upgrade at the moment.