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!

UnityExtensions Why do these DLLs end up in Android build? HoloLens?

Discussion in 'Editor & General Support' started by Gerold_Meisinger, Apr 18, 2018.

  1. Gerold_Meisinger

    Gerold_Meisinger

    Joined:
    Sep 8, 2015
    Posts:
    93
    When I build a new empty project (+use micro mscorlib) in Unity 5.6.5p4 for Android and analyze the used assets in %LOCALAPPDATA%\Unity\Editor\Editor.log I can see the following DLLs end up in the build:

    UnityExtensions/Unity/Networking/UnityEngine.Networking.dll
    UnityExtensions/Unity/UnityHoloLens/RuntimeEditor/UnityEngine.HoloLens.dll
    UnityExtensions/Unity/UnityHoloLens/Runtime/UnityEngine.HoloLens.dll
    UnityExtensions/Unity/TestRunner/UnityEngine.TestRunner.dll
    UnityExtensions/Unity/Advertisements/UnityEngine.Advertisements.dll
    UnityExtensions/Unity/UnityAnalytics/UnityEngine.Analytics.dll
    UnityExtensions/Unity/UnityPurchasing/UnityEngine.Purchasing.dll

    As I said, it's a new and empty project. No scripts that use any network capabilities. Never used the TestRunner. Analytics were set to off at project creation. No ads, No purchasing activated. And what about HoloLens, in Android?

    Why do these DLLs end up in the build and how can I avoid it?
     
    Last edited: Apr 18, 2018
    Gerold_Meisinger, Apr 18, 2018
    #1

  2. Gerold_Meisinger

    Gerold_Meisinger

    Joined:
    Sep 8, 2015
    Posts:
    93
    bump
     
    Gerold_Meisinger, May 3, 2018
    #2