Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. .NET (Core and Framework)
  4. Assembly not loading

Assembly not loading

Scheduled Pinned Locked Moved .NET (Core and Framework)
6 Posts 3 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • N Offline
    N Offline
    nutkase
    wrote on last edited by
    #1

    Hi, I am facing a problem ... I have a project, when i try to run the executables from a network path the assemblies fail to load. Where as the executables work perfectly fine when run from a local path. My guess is this has to do something with the .NET security. Any ideas, thoughts????? Thanks in advance :)

    M 1 Reply Last reply
    0
    • N nutkase

      Hi, I am facing a problem ... I have a project, when i try to run the executables from a network path the assemblies fail to load. Where as the executables work perfectly fine when run from a local path. My guess is this has to do something with the .NET security. Any ideas, thoughts????? Thanks in advance :)

      M Offline
      M Offline
      Marcus J Smith
      wrote on last edited by
      #2

      Security may be one, is the .NET framework installed on the network location you are accessing? That may be the other.


      CleaKO

      "I think you'll be okay here, they have a thin candy shell. 'Surprised you didn't know that." - Tommy Boy
      "Fill it up again! Fill it up again! Once it hits your lips, it's so good!" - Frank the Tank (Old School)

      N 1 Reply Last reply
      0
      • M Marcus J Smith

        Security may be one, is the .NET framework installed on the network location you are accessing? That may be the other.


        CleaKO

        "I think you'll be okay here, they have a thin candy shell. 'Surprised you didn't know that." - Tommy Boy
        "Fill it up again! Fill it up again! Once it hits your lips, it's so good!" - Frank the Tank (Old School)

        N Offline
        N Offline
        nutkase
        wrote on last edited by
        #3

        well basically both the machines are dev machines! so i have .net framework and everything else i can concieve installed on both the machines :(

        N 1 Reply Last reply
        0
        • N nutkase

          well basically both the machines are dev machines! so i have .net framework and everything else i can concieve installed on both the machines :(

          N Offline
          N Offline
          nutkase
          wrote on last edited by
          #4

          I have investigated the problem .. here are my findings... my assemblies are strong name signed.. but a simple Assembly.LoadFrom(..) fails? giving me a FileLoadException? The load is successful if i do it from a local path.. but on a network path it fails! :(

          D 1 Reply Last reply
          0
          • N nutkase

            I have investigated the problem .. here are my findings... my assemblies are strong name signed.. but a simple Assembly.LoadFrom(..) fails? giving me a FileLoadException? The load is successful if i do it from a local path.. but on a network path it fails! :(

            D Offline
            D Offline
            Dave Kreskowiak
            wrote on last edited by
            #5

            That's because, by default, code comming from any network source is not trusted. You can read up on Code Access Security here[^]. Believe me, it's not something you want to just "gloss over". Read it.

            Dave Kreskowiak Microsoft MVP - Visual Basic

            N 1 Reply Last reply
            0
            • D Dave Kreskowiak

              That's because, by default, code comming from any network source is not trusted. You can read up on Code Access Security here[^]. Believe me, it's not something you want to just "gloss over". Read it.

              Dave Kreskowiak Microsoft MVP - Visual Basic

              N Offline
              N Offline
              nutkase
              wrote on last edited by
              #6

              Thanks people!

              1 Reply Last reply
              0
              Reply
              • Reply as topic
              Log in to reply
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes


              • Login

              • Don't have an account? Register

              • Login or register to search.
              • First post
                Last post
              0
              • Categories
              • Recent
              • Tags
              • Popular
              • World
              • Users
              • Groups