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
New Forum User Notice Update to the Unity Editor Software Terms

vs code omnisharp not working when working with Unity Package

Discussion in 'Editor & General Support' started by wihu, Feb 23, 2020.

  1. wihu

    wihu

    Joined:
    Nov 22, 2012
    Posts:
    25
    Normally when working with a Unity game project, vs code omnisharp works fine and i get auto complete when typing codes, however, when working on a Unity Package and by specifying asmdef with custom package name e.g. X so it creates X.csproj, omnisharp fails to pick up the project file and instead giving these warns:

    Code (CSharp):
    1. [warn]: OmniSharp.MSBuild.ProjectSystem
    2. Found project that doesn't exist on disk: /Users/a/MyProject/Assembly-CSharp.csproj
    3. [warn]: OmniSharp.MSBuild.ProjectSystem
    4. Found project that doesn't exist on disk: /Users/a/MyProject/Assembly-CSharp-Editor.csproj
    Is there a way to configure so that omnisharp would pick up X.csproj instead of default Assembly-CSharp.csproj?
     
    wihu, Feb 23, 2020
    #1
    matheus_unity812 likes this.

  2. Julian_Gamble

    Julian_Gamble

    Joined:
    Feb 26, 2020
    Posts:
    7
    +1 to this. Packages are nice, but engineering workflows needs to be a priority to make the best use of all this.
     
    Julian_Gamble, Mar 25, 2020
    #2