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 2017.3.1f1 and 2017.3.1p4 cannot switch to .NET 4.6 - blank console error

Discussion in 'Editor & General Support' started by Naphier, Mar 27, 2018.

  1. Naphier

    Naphier

    Joined:
    Aug 4, 2014
    Posts:
    114
    Unity Editor 64-bit under Windows 10. Project platform is standalone.

    Shot in the dark here since there's very little info I can give...
    We're trying to switch to .NET 4.6 and after the switch we get 2 errors.
    One is an error about missing .nuget package:
    System.Exception: Package directory not found: "C:\Users\XXXXX\.nuget\packages\Microsoft.CSharp\4.0.1"

    This error can be cleared and only seems to appear after re-import.

    Then there's a lovely blank console error that cannot be cleared and we cannot build or run...
    This is a well-established project with quite a few libraries. I removed some suspect ones (ones that I could remove without changing a ton of stuff in the code) and notta.
    I've tried deleting the Library, and all .proj/.sln etc files. Notta...

    This is happening across multiple workstations running Windows 10.
    And it's happening with Unity 2017.3.1f1 as well as the latest patch 2017.3.1p4.
    This does not happen in other projects we have.

    Unfortunately, we need .NET 4.6 support for an SDK that we're required to integrate.

    I'm stuck :( and hoping someone has run into a similar situation.

    Here's a link to some backup files - a list of libraries we use, the unhelpful editor log, and a screencap showing the awesome blank console error :(
    https://www.dropbox.com/sh/hwvondzhscalxbu/AABBmpwV1pQWWc4R5dacCNtqa?dl=0

    I've tried deleting AVPro, Ooki.Dialogs.dll, System.Windows.Forms.dll, and a few others. There's too much to try and I may have to end up working the other way around and Importing stuff to a new project until the error hits. Either way is super painful...

    Appreciate any help that can be provided!!

    Unity issue tracker:
    https://fogbugz.unity3d.com/default.asp?1019084_1fbmtcgb959s5vhg
     
    Last edited: Mar 27, 2018
  2. Naphier

    Naphier

    Joined:
    Aug 4, 2014
    Posts:
    114
    Reply from Unity:
    Hey,


    Thank you for reporting the issue.


    Does your project contain any UnityScript files? We had a similar issue with .NET Standard 2.0 --> https://issuetracker.unity3d.com/is...ed-in-assets-and-net-standard-2-dot-0-is-used


    It was fixed in 2018 beta version. Perhaps the bug found its way in the latest 2017.3 patch releases, we could not reproduce the issue on 2017.3 back then.


    Regards,

    Mantas

    Unity QA​

    Indeed this was the issue. I deleted all JS files from our project and all is well!