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. Unite 2023 Registrations are now LIVE! We are thrilled to announce that Unite 2023 Registration is now live and open for all!
    Dismiss Notice
New Forum User Notice Unite 2023 Registrations are now LIVE!

'UnityEngine' does not have a strong name

Discussion in 'Scripting' started by Qbit86, Jun 18, 2014.

  1. Qbit86

    Qbit86

    Joined:
    Sep 2, 2013
    Posts:
    487
    Hi!

    I'm trying to create Unity plugin in Visual Studio 2013 — simple assembly for .NET 3.5/CLR 2.0 which utilizes only Mono-compatible API. I need it to be signed, so I (or runtime environment during assembly loading) could check integrity according strong name given. Unfortunately I've got an error:
    “Assembly generation failed -- Referenced assembly 'UnityEngine' does not have a strong name”

    Why is UnityEngine.dll not strong-named? Should I report this as bug?
     
    Qbit86, Jun 18, 2014
    #1

  2. Tomas1856

    Tomas1856

    Unity Technologies

    Joined:
    Sep 21, 2012
    Posts:
    3,658
    UnityEngine is not strong-named on purpose, and it will probably never be signed with strong name
     
    Tomas1856, Jun 19, 2014
    #2

  3. ZimM

    ZimM

    Joined:
    Dec 24, 2012
    Posts:
    963
    Could you please give any details on that? Why not? This makes it impossible to build a strong-named assembly that references UnityEngine.
     
    ZimM, Dec 12, 2014
    #3

  4. Tomas1856

    Tomas1856

    Unity Technologies

    Joined:
    Sep 21, 2012
    Posts:
    3,658
    Mainly because, even when it is compiled, it still being patched during the build to Windows Store Apps, also if we would suddenly change UnityEngine.dll to be strong-named, all the current plugins in the asset store would stop working.
     
    Tomas1856, Dec 12, 2014
    #4

  5. XRenkoX

    XRenkoX

    Joined:
    Nov 3, 2013
    Posts:
    14
    what are the advantages and disadvantages of making a .dll strong named or not?>
     
    XRenkoX, Dec 12, 2014
    #5