Search Unity

  1. The 2022.1 beta is now available for testing. To find out what's new, have a look at our 2022.1 beta blog post.
    Dismiss Notice

Bug Omnisharp update v1.23.3 breaks references to common unity namespaces

Discussion in 'Formats & External Tools' started by djweaver, Oct 13, 2020.

  1. djweaver

    djweaver

    Joined:
    Jul 4, 2020
    Posts:
    105
    I noticed after updating to omnisharp that one of my plugin namespaces wasn't being recognized anymore. Then when I brought up omnisharp in the panel I noticed a whopping 5k errors. This happened immediately after updating to omnisharp v1.23.3. Anyone know how to roll back to 1.23.2?

    I've tried everything mentioned here: https://stackoverflow.com/questions/64334703/omnisharp-update-v1-23-3-breaks-unity-references

    EDIT: looks like its already been reported: https://github.com/OmniSharp/omnisharp-vscode/issues/4110

    I found that rolling back to 1.23.2 does fix the issue for the time being
     
    Last edited: Oct 13, 2020
    Incode, The-Oddler and ooviixoo like this.
  2. ooviixoo

    ooviixoo

    Joined:
    Dec 12, 2017
    Posts:
    11
    Oh wow... just spent the last 3 hours tearing up my dev env only to stumble upon this thread...

    1.23.2 rollback...priceless.
     
    The-Oddler and djweaver like this.
  3. BagoDev

    BagoDev

    Joined:
    Jan 2, 2017
    Posts:
    11
    Same issue here, some projects are broken while others remain untouched.
     
    djweaver likes this.
  4. Choppa2

    Choppa2

    Joined:
    Aug 28, 2020
    Posts:
    1
    Got this nasty error and spent a whole afternoon trying to fix it. Somehow setting Unity's 'External Script Editor' option to Visual Studio 2019 fixed the problem for me.

    Waiting for the fix. I really don't want to accidentally open Visual Studio when I debug and have the computer freeze for a good minute.
     
    djweaver likes this.
unityunity