Results 1 to 2 of 2

Thread: .SNK FileNotFoundException

  1. #1

    Thread Starter
    Hyperactive Member
    Join Date
    Aug 2001
    Location
    India
    Posts
    276

    .SNK FileNotFoundException

    Hi,
    Whenever we referenced "component X" from our application we got the error:
    "System.IO.FileNotFoundException: File or assembly
    name <assembly name>, or one of its dependencies, was not found"

    The strange part is this happens
    1. Only from 1 system on the network
    2. Only on the assembly X

    When we gave a project reference and tried to debug the code, it worked when we commented out the reference to the strong key in the assemblyInfo file:
    [assembly: AssemblyKeyFile("<networkPath>")]
    The SNK file exists on this path and all other assemblies use the same SNK file without any problems

    First thing I wonder how relevant is the error message? As the same assembly X, works on other machines..

    Is there something wrong in the framework on this particular machine?
    Thanks,
    Jemima.
    "Your worst days are never so bad that you are beyond the reach of God's grace...
    and your best days are never so good that you are beyond the need of God's grace."

  2. #2
    Hyperactive Member
    Join Date
    Aug 2002
    Location
    Fort Collins, CO
    Posts
    366

    Re: .SNK FileNotFoundException

    If there was a problem here:
    Code:
    [assembly: AssemblyKeyFile("<networkPath>")]
    with the key file not found at <networkPath>, you
    would only see an error when compiling the assembly who needs the key file, and the exception would not be FileNotFoundException. Out of curiousity, why would you put that key file on the network?

    Back to the prob, so on the one system that has the FileNotFoundException issues, all of the dependencies that "component X" needs(i'm assuming this component is not part of the .NET framework) must be on that machine. That means the exact same versions of those dependencies that "component X" was compiled against.

    Since this assembly(component X) works on the other machines, find the dependencies component X requires on those machines and move them to the system that has issues.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width