Search Unity

  1. Unity Asset Manager is now available in public beta. Try it out now and join the conversation here in the forums.
    Dismiss Notice
  2. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  3. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

API updater makes DLL's unusable for VS

Discussion in 'Unity 5 Pre-order Beta' started by Immanuel-Scholz, Dec 8, 2014.

  1. Immanuel-Scholz

    Immanuel-Scholz

    Joined:
    Jun 8, 2013
    Posts:
    221
    Hello,

    When upgrading our binary dll's with Unity 5, beta 15 *), they sometimes become unusable in Visual Studio. More specific, its unable to update PlayMakerEditor.dll.

    A co-worker already submitted a bug report: 652911

    I know that Visual Studio is not "officially" supported by Unity, and the Unity mono compiler itself don't seem to have a problem with the DLL's.

    But we heavily rely on VS for coding here and this would be a major headache for us if we can't use VS in Unity 5 anymore. Could you please check whether this bug can be resolved soon or whether there are obstacles and its likely to stay for a while?
    Thank you :)

    Immanuel Scholz


    *) Yes, I know Beta16 is the latest. I couldn't test it on beta16 right now, but there is no mentioning of "DLL" in the release notes and the two items about "API updater" are not related, so I guess it applies to beta15 as well. The bug is also left open.
     
  2. AdrianoVerona_Unity

    AdrianoVerona_Unity

    Unity Technologies

    Joined:
    Apr 11, 2013
    Posts:
    317
    Hi, thanks for reporting. I don't see why the assembly should not be usable after updating. I'll take a look later

    Adriano
     
  3. Immanuel-Scholz

    Immanuel-Scholz

    Joined:
    Jun 8, 2013
    Posts:
    221
    Any news on this? :)
     
  4. AdrianoVerona_Unity

    AdrianoVerona_Unity

    Unity Technologies

    Joined:
    Apr 11, 2013
    Posts:
    317
    Hey, I am debugging it now :)

    What I already noticed is that we only apply 5 ~ 6 updates to this assembly

    I'll continue trying to isolate the culprit

    I'll post more info soon.

    Adriano
     
  5. AdrianoVerona_Unity

    AdrianoVerona_Unity

    Unity Technologies

    Joined:
    Apr 11, 2013
    Posts:
    317
    It looks like either we hit a bug in, or we are misusing, one of the libs used by the updater.

    Simply opening and saving the assembly causes PEVerify to complain about it (even though mono tools have no issues with the assembly)

    I'll investigate further.

    Adriano
     
    Last edited: Dec 11, 2014
  6. AdrianoVerona_Unity

    AdrianoVerona_Unity

    Unity Technologies

    Joined:
    Apr 11, 2013
    Posts:
    317
    Just want to let you know this is fixed in our VCS. Should be available in the next builds

    Adriano
     
  7. Immanuel-Scholz

    Immanuel-Scholz

    Joined:
    Jun 8, 2013
    Posts:
    221
    Woot. Thanks.

    I assume that I will have to restore the unpatched (and unbroken) DLL's in this version, so the updater can patch them again, right?
     
  8. AdrianoVerona_Unity

    AdrianoVerona_Unity

    Unity Technologies

    Joined:
    Apr 11, 2013
    Posts:
    317
    yep! (BTW: code has just been merged to our main dev repo :)

    Thanks for reporting

    Adriano