locked
Azure Batch File Issue: A strongly-named assembly is required. RRS feed

  • Question

  • In relation to the post https://social.msdn.microsoft.com/Forums/en-US/d71224ed-377e-4dbb-a6d2-4aa683f692e3/migrating-libraries-to-azure-batch-file-not-found?forum=azurebatch

    I get the following error:

    Could not load file or assembly 'Tamir.SharpSSH, Version=1.1.1.13, Culture=neutral, PublicKeyToken=null' or one of its dependencies. A strongly-named assembly is required.

    I have tried strong naming the assembly like this

    ildasm.exe Tamir.SharpSSH.dll /OUTPUT=Tamir.SharpSSH.il

    only to encounter the error

    File 'Tamir.SharpSSH.dll' not found or not a PE file.


    Thursday, July 27, 2017 5:26 PM

Answers

  • This issue doesn't really have anything to do with Azure Batch (it's a C# assembly loading/signing issue), but:

    1) I don't think you can just strong name an assembly with ildasm.exe like that. Try looking here or here for how to strong name assemblies.

    2) For debugging this issue, you can do so even locally likely: This stackoverflow post has some good suggestions

    -Matt

    • Marked as answer by Hackathor Tuesday, August 1, 2017 5:05 PM
    Friday, July 28, 2017 10:08 PM