Search Unity

  1. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  2. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

[SOLVED] Unity 2018.1.0f2 - Brand new project gives errors, can't talk to visual studio

Discussion in 'Editor & General Support' started by whilefun, May 2, 2018.

  1. whilefun

    whilefun

    Joined:
    Nov 14, 2013
    Posts:
    130
    Hi folks,

    After installing Unity 2018.1.0f2 and creating a new project, I get this result:

    BrandNewProject.jpg

    It appears visual studio is not talking to unity. I create a new empty script, and double click to edit, and get this message:

    BrokenVS.jpg

    Did I miss a step here? The latest other release is Unity 2017.3.0f3 and it works fine with VS. Does 2018 require some special sauce to get it to work? The older 2018 betas worked fine as well.

    Thanks
     
  2. JeffDUnity3D

    JeffDUnity3D

    Joined:
    May 2, 2017
    Posts:
    14,446
    I had a similar problem. I was using VS 2015, and updating to VS 2017 solved it for me. I used the "Download Visual Studio 2017" option during Unity install.
     
  3. whilefun

    whilefun

    Joined:
    Nov 14, 2013
    Posts:
    130
    Does VS 2017 break anything with old Unity versions? 5.5.4p3 is my daily driver, so I don't want to risk conflicts.
     
  4. JeffDUnity3D

    JeffDUnity3D

    Joined:
    May 2, 2017
    Posts:
    14,446
  5. whilefun

    whilefun

    Joined:
    Nov 14, 2013
    Posts:
    130
  6. whilefun

    whilefun

    Joined:
    Nov 14, 2013
    Posts:
    130
    So, installing Visual Studio 2017 Community solved the issue, however, you also need to switch over the External Tool reference to be Visual Studio 2017 Community instead of Visual Studio 2015. (see screenshot below)

    Unity2018_VS2017Community.jpg

    Also note: Unity 5.5.4p3 auto-switched to use Visual Studio 2017 as well. I can switch it back, but then Unity 2018 also switches back and breaks again.

    If Unity can break out Preferences by install or even better by project, that would be ideal.

    But this solves the immediate term problem with Unity 2018.1.0f2
     
  7. DivideByNil

    DivideByNil

    Joined:
    Dec 4, 2015
    Posts:
    15
    Although this thread is a few months old this seems like the appropriate place to post my issue and work-around.

    Using Unity 2018.2.2f1 and 2018.2.3f1, I found that no matter what I tried (and I tried a great deal), I could not get Unity and Visual Studio 2017 Community to play nice with deploying UWP builds. I got an error telling me the splashscreen.png was not found and was warned that Visual Studio could not find the VC ++ v140 (even though I installed the correct tools). Trying to launch the .appx directly did not work, even with manually applying a license.

    The solution was to use SDK version 10.0.10586.0 with Visual Studio Community 2015. Attemping to use any newer SDK caused failures. Using the aforementioned SDK with Visual Studio 2017 also caused errors.

    TL;DR: The ONLY way I got a UWP project to deploy successfully in Unity 2018.2 was to use SDK 10.0.10586.0 with Visual Studio 2015. VS2017 wouldn't work regardless of SDK version.