Search Unity

  1. Unity 2020.1 has been released.
    Dismiss Notice
  2. We are looking for feedback on the experimental Unity Safe Mode which is aiming to help you resolve compilation errors faster during project startup.
    Dismiss Notice
  3. Good news ✨ We have more Unite Now videos available for you to watch on-demand! Come check them out and ask our experts any questions!
    Dismiss Notice

Cannot open VS 2017 scripts within the editor

Discussion in '2019.3 Beta' started by EASYJABBA, May 29, 2019.

  1. EASYJABBA

    EASYJABBA

    Joined:
    May 29, 2019
    Posts:
    14
    Cannot believe we have been pushed to the alpha version as this is the only version that works with a CPU with 20 cores or more.

    The first bug we noticed was you cannot double click on any script within the editor which is a shame, using the VS2017 Pro version.

    Also saw many errors in the Event Viewer regarding COMIntegration.exe, I'm sure this is tied to opening the scripts.

    We would very much like to be involved in testing out the 2019 versions as we can only work with this version.

    Hopefully this shouldn't be to much of a nightmare.

    Thankyou for your time and hope to speak soon.
     
    Fewpwew130 likes this.
  2. EASYJABBA

    EASYJABBA

    Joined:
    May 29, 2019
    Posts:
    14
    Update here.

    On the 2018LTS version when you open any script in the editor VS opens the correct script first time no problem.

    I tried to send a bug report but upon clicking 'Send' it stated 'Connection Refused'? So I'll write the bug report here for the V3Alpha.

    1. What happened

    When you open a C# script in the editor it only opens VS2017 Pro with a blank page, you then have to go back to Unity and doubleclick on the C# script again for VS to open it?

    2. How we can reproduce it using the example you attached

    Just open any script from the editor with VS2017 Pro and you will see that VS2017 doesn't open the script until you doubleclick the script again.
    If you have many scripts saved in VS then it will load the wrong one up until you manually select it. This is not good as when you click on a script it should loadup 1st time, because I edited the wrong ones until I noticed it wasn't loading the correct one first time.

    Thankyou for your time and hope to speak soon.
     
    Kerber996 likes this.
  3. EASYJABBA

    EASYJABBA

    Joined:
    May 29, 2019
    Posts:
    14
    Update here.

    Just download the V4 Alpha and its still the same, VS wont load the script within the editor.

    Please fix this Unity.
     
  4. Fewpwew130

    Fewpwew130

    Joined:
    Feb 4, 2014
    Posts:
    7
    After using 2019.4 LTS and Visual Studio Community 2017 for quite some time, today I decided to try Unity 2020.1.0. This was a mistake. After upgrading the project, it didn't allow to seamlessly open in by double clicking on a script file - COMIntegration.exe error and Visual Studio instant crash. However, a partial workaround was to go to the Unity menu bar:

    1. In Unity, do Edit -> Preferences.
    2. In the Preferences window that opened, choose the External Tools tab.
    3. Click on the External Script Editor dropdown.
    4. Here it was chosen Visual Studio 2017.
    5. Instead a change to open By File extension partly solved the problem.

    Partially, because VS seems to be disconnected from the Unity's 'libraries', thus it has no code autofill enabled. If someone knows how to fix that, it would be great :)
     
unityunity