Search Unity

  1. How can our website serve you better? Give us your feedback. Take our survey and let us know.
    Dismiss Notice

Bug 2021.1.10 doesn't upgrade old projects to add package for Visual Studio - com.unity.ide.visualstudio

Discussion in 'Editor & General Support' started by jason_yak, Jun 9, 2021.

  1. jason_yak

    jason_yak

    Joined:
    Aug 25, 2016
    Posts:
    400
    Just spent over a day trying to work out why my old project going from 2020.3 to 2021.1 no longer worked with Visual Studio. It would not open the solution properly and would give me no options to regenerate the visual studio project in preferences > external tools. Yet if I start a new project in 2021.1 it allows me to use visual studio properly and the generate csproj option appears.

    I copied my problematic project and started deleting chunks at a time and trying to run the project until I narrowed it down to this new obviously required package for Visual Studio - com.unity.ide.visualstudio, which probably comes as no surprise to Unity devs, but how is everyone else meant to know this is now required? you'd think that given that the project has Visual Studio selected as the the external editor in an older project created pre-2021 that it would add this missing required package in.

    There's also zero mention to this in the upgrade guide https://docs.unity3d.com/2021.1/Documentation/Manual/UpgradeGuide20211.html

    I searched the forums for any mention to com.unity.ide.visualstudio package. How on earth would anyone know about this otherwise? where should I be looking in the future to find out these important changes?
     
    Last edited: Jun 9, 2021
  2. jason_yak

    jason_yak

    Joined:
    Aug 25, 2016
    Posts:
    400
    Just checked all release notes for all 2021.1.x releases as well and also no mention of this change either.
     
  3. jason_yak

    jason_yak

    Joined:
    Aug 25, 2016
    Posts:
    400
    If you can't automate adding this package as an upgrade, I'd suggest the most bullet proof way of dealing with this is that in the preferences under the external editor tool selection it adds a warning label that the appropritate package listing is missing for the tool selected. As no doubt even if there is some messaging in release notes or upgrade guide many peolpe will still not work this out easily.
     
unityunity