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.

[SOLVED] System.Io.FileLoadException

Discussion in 'Windows' started by wolfen231, Jul 4, 2014.

  1. wolfen231

    wolfen231

    Joined:
    Apr 22, 2014
    Posts:
    402
    Hi there,

    A script from one of the assets downloaded on the store gives this error

    Error Error: System.IO.FileLoadException: Could not load file or assembly 'file:///C:\Windows\Microsoft.NET\Framework\v2.0.50727\System.Xml.dll' or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515) (Error: System.IO.FileLoadException: Could not load file or assembly 'file:///C:\Windows\Microsoft.NET\Framework\v2.0.50727\System.Xml.dll' or one of its dependencies. Operation is not supported. (Exception from HRESULT) (Assembly-UnityScript-firstpass)

    I am unsure how to resolve this. Any help would be appreciated.
     
  2. Aurimas-Cernius

    Aurimas-Cernius

    Unity Technologies

    Joined:
    Jul 31, 2013
    Posts:
    3,671
    Which vearsion of Unity do you use? I think this error was fixed, but want to make sure.
     
  3. wolfen231

    wolfen231

    Joined:
    Apr 22, 2014
    Posts:
    402
  4. Lanre

    Lanre

    Joined:
    Dec 26, 2013
    Posts:
    3,963
    What's your .NET framework version? Is it updated?
     
  5. Aurimas-Cernius

    Aurimas-Cernius

    Unity Technologies

    Joined:
    Jul 31, 2013
    Posts:
    3,671
    Can you try with 4.5? It's quite possible 4.3 has this bug.
     
  6. wolfen231

    wolfen231

    Joined:
    Apr 22, 2014
    Posts:
    402
    So it seems a few asset packs conflicted or just broke things. I removed three primary biggies I use, reloaded the project, all cs errors were gone. Re-imported the assets one by one and restarting after each import. Problem solved that way.

    I already went through all the .net stuff I could. .Net fix from MS, uninstall re-install, checked if files were blocked, etc. That's why I came here. I originally tried really hard to find an answer to the error being spit out in Monodevelop.

    I am actually just really confused how these packs could of randomly set this issue off. However we did have a bad gui script that wasn't updated which stopped scripts from compiling only because that one was broken. But that wasn't causing all cs to spit that error out. Very strange behavior.

    Edit: P.S. Thanks to those who did try to help with this. Much appreciated. =)