Assembly not found in deps.json

Hi,

If I run the attached .net core console app I get

Johns-Mac-mini:Debug JohnMoshakis$ dotnet AmazonSQSCoreConsoleApplication.exe
Error:
An assembly specified in the application dependencies manifest (AmazonSQSCoreConsoleApplication.deps.json) was not found:
package: ‘System.Net.Http’, version: ‘4.3.3’
path: ‘runtimes/unix/lib/netstandard1.6/System.Net.Http.dll’
AmazonSQSCoreConsoleApplication.zip (597.4 KB)
Cheers,
John

Will this one be looked into ?

I don’t know.

TBH I’d help if you could do a little bit of background research as to what’s wrong. EBuild emits a ton of infos, the you build with --debug, and there’s a lot off things you can check. Not every single build error should become a support request…

1 Like

Im adding AWSSDK.SQS 3.3.3.59

Should I expect the deps.json file to be exactly the same ?

Looking at just the assembly its complaining about

From targets

Elements

  "System.Net.Http/4.3.3": {
    "dependencies": {
      "runtime.native.System.Net.Http": "4.3.0",
      "runtime.native.System.Security.Cryptography.OpenSsl": "4.3.3",
      "runtime.native.System": "4.3.0",
      "System.Collections": "4.3.0",
      "System.Diagnostics.Debug": "4.3.0",
      "System.Diagnostics.DiagnosticSource": "4.5.1",
      "System.Diagnostics.Tracing": "4.3.0",
      "System.Globalization.Extensions": "4.3.0",
      "System.Globalization": "4.3.0",
      "System.IO.FileSystem": "4.3.0",
      "System.IO": "4.3.0",
      "System.Net.Primitives": "4.3.0",
      "System.Resources.ResourceManager": "4.3.0",
      "System.Runtime.Extensions": "4.3.0",
      "System.Runtime.Handles": "4.3.0",
      "System.Runtime.InteropServices": "4.3.0",
      "System.Runtime": "4.3.0",
      "System.Security.Cryptography.Algorithms": "4.3.0",
      "System.Security.Cryptography.Encoding": "4.3.0",
      "System.Security.Cryptography.OpenSsl": "4.3.0",
      "System.Security.Cryptography.Primitives": "4.3.0",
      "System.Security.Cryptography.X509Certificates": "4.3.0",
      "System.Text.Encoding": "4.3.0",
      "System.Threading.Tasks": "4.3.0",
      "System.Threading": "4.3.0"
    },
    "runtimeTargets": {
      "runtimes/unix/lib/netstandard1.6/System.Net.Http.dll": {
        "rid": "unix",
        "assetType": "runtime",
        "assemblyVersion": "4.1.1.2",
        "fileVersion": "4.6.25705.1"
      },
      "runtimes/win/lib/netstandard1.3/System.Net.Http.dll": {
        "rid": "win",
        "assetType": "runtime",
        "assemblyVersion": "4.1.1.2",
        "fileVersion": "4.6.25705.1"
      }
    }
  },

Microsoft

  "System.Net.Http/4.1.0": {
    "dependencies": {
      "System.Collections": "4.0.11",
      "System.Diagnostics.Debug": "4.0.11",
      "System.Diagnostics.DiagnosticSource": "4.0.0",
      "System.Diagnostics.Tracing": "4.1.0",
      "System.Globalization": "4.0.11",
      "System.Globalization.Extensions": "4.0.1",
      "System.IO": "4.1.0",
      "System.IO.FileSystem": "4.0.1",
      "System.Net.Primitives": "4.0.11",
      "System.Resources.ResourceManager": "4.0.1",
      "System.Runtime": "4.1.0",
      "System.Runtime.Extensions": "4.1.0",
      "System.Runtime.Handles": "4.0.1",
      "System.Runtime.InteropServices": "4.1.0",
      "System.Security.Cryptography.Algorithms": "4.2.0",
      "System.Security.Cryptography.Encoding": "4.0.0",
      "System.Security.Cryptography.OpenSsl": "4.0.0",
      "System.Security.Cryptography.Primitives": "4.0.0",
      "System.Security.Cryptography.X509Certificates": "4.1.0",
      "System.Text.Encoding": "4.0.11",
      "System.Threading": "4.0.11",
      "System.Threading.Tasks": "4.0.11",
      "runtime.native.System": "4.0.0",
      "runtime.native.System.Net.Http": "4.0.1",
      "runtime.native.System.Security.Cryptography": "4.0.0"
    },
    "runtimeTargets": {
      "runtime/unix/lib/_._": {
        "rid": "unix",
        "assetType": "runtime"
      },
      "runtime/win/lib/_._": {
        "rid": "win",
        "assetType": "runtime"
      }
    }
  },<a class="attachment" href="/uploads/default/original/2X/c/c6b8fd90336e8ed4ce395653f1d02a0a975635ff.zip">AWS.zip</a> (786.9 KB)

Thats my example.

So instead I created a console app in both referencing System.Net.Http 4.3.4

In the targets section the dependencies section is the same but Elements has

    "runtime": {
      "ref/netstandard1.3/System.Net.Http.dll": {
        "assemblyVersion": "4.1.1.3",
        "fileVersion": "4.6.26907.1"
      }
    },
    "runtimeTargets": {
      "runtimes/unix/lib/netstandard1.6/System.Net.Http.dll": {
        "rid": "unix",
        "assetType": "runtime",
        "assemblyVersion": "4.1.1.3",
        "fileVersion": "4.6.26907.1"
      },
      "runtimes/win/lib/netstandard1.3/System.Net.Http.dll": {
        "rid": "win",
        "assetType": "runtime",
        "assemblyVersion": "4.1.1.3",
        "fileVersion": "4.6.26907.1"
      }
    }

Microsoft has

    "runtimeTargets": {
      "runtime/unix/lib/_._": {
        "rid": "unix",
        "assetType": "runtime"
      },
      "runtime/win/lib/_._": {
        "rid": "win",
        "assetType": "runtime"
      }
    }

If I update the deps.json to just have dependencies and runtimes it loads

This without my modifications

SystemNetHttp.zip (231.0 KB)

Will this one be looked into ?

can I get two identical sample projects (code+bin), dotnet and Elements?

SystemNetHttp.zip (232.7 KB)

SystemNetConsoleApp is from dotnet

"runtimeTargets": { "runtimes/unix/lib/netstandard1.6/System.Net.Http.dll": { "rid": "unix", "assetType": "runtime", "assemblyVersion": "4.1.1.3", "fileVersion": "4.6.26907.1" }, "runtimes/win/lib/netstandard1.3/System.Net.Http.dll": { "rid": "win", "assetType": "runtime", "assemblyVersion": "4.1.1.3", "fileVersion": "4.6.26907.1" } }

that does seem to match whats in the actual NuGet package, though…

Yes.

I couldn’t find any in depth documentation for whats meant to be in the file. I don’t know how you got this far.

Yeah, me neither… :woman_shrugging:t3: :(.

Have you got a contact at Microsoft that can provide help ?

The only way I get things working is to use dotnet to create a web app and reference my oxygene code as standard libraries. I don’t really want to have to do that.

Cheers,
John

Hi,

I would really like to get this one moving forward again. I was reading about the plans for .net 5 and it seems focused on .net core. Currently this is blocking me from making use of it.

Cheers,
John

I’m as out of ideas on this as I was 2 months ago :(.

.NET 5 will ship at the end of 2020. Microsoft will change how all of this works 37 times between now and then (and I’m sure not for the better ;). Remember when .NET 2.0 was a nice, clean and straightforward toolchain? good times…

Even .NET Core 3 is not due til this fall.

As a tools developer for the windows platform do you not have an official channel with microsoft ?

it’s not as clear cut as that, but I’ll see if we can reach out to someone form Microsoft on this, yes.

Thanks. I’m sorry to go on about cases its just that I really enjoy using Fire/Elements

1 Like