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

So how come we can't replace missing assemblies anymore, eh?

Discussion in '2019.1 Beta' started by MegamaDev, Mar 27, 2019.

  1. MegamaDev

    MegamaDev

    Joined:
    Jul 17, 2017
    Posts:
    77
    Because it seems like, if you've got a missing assembly, the only two useful things to do to it are to remove the reference or redirect it to point to a new, existent assembly.

    Seems a little weird to grey over one of those options, is what I'm saying. Not to mention inconvenient, being that I use said option all the time. And yeah, GUID-based references exist now, and yeah, I'll eventually get used to not being able to add new references directly from VSCode. Just...while we're still moving our brains (and our .asmdef files) over to the newer, better way, maybe provide a bit more room for error?
     
  2. HaraldNielsen

    HaraldNielsen

    Unity Technologies

    Joined:
    Jun 8, 2016
    Posts:
    136
    I agree that not being able to update the reference is not optimal.
    Will find a better way to signal that the asmdef is not there.
     
    MegamaDev likes this.