Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Microsoft.ML.OnnxTransformer asking for wrong Microsoft.ML.OnnxRuntime version #7297

Open
sportbilly21 opened this issue Nov 11, 2024 · 1 comment
Labels
untriaged New issue has not been triaged

Comments

@sportbilly21
Copy link

System Information (please complete the following information):

  • OS & Version: 10
  • ML.NET Version: 3.01
  • ML.OnnxTransformer 3.01
  • .NET Version: Framework 4.7

Describe the bug
I have updated all nuget packages to the latest versions, include Microsoft.ML.OnnxRuntime.Gpu which I now you are not managing version of the package is 1.20 and the version of the produced dll of that package Microsoft.ML.OnnxRuntime is again 1.20.
When I running a unit test I am getting the following error System.IO.FileLoadException: Could not load file or assembly 'Microsoft.ML.OnnxRuntime, Version=0.0.0.0, which comes from the Microsoft.ML.OnnxTransformer nuget package.
Microsoft.ML.OnnxRuntime.Gpu, before version 1.19, was producing the Microsoft.ML.OnnxRuntime.dll with the version 0.0.0.0 which was a bug from their side, This has been corrected from their side and now it updates the version in the dll.
The issue is that ML.OnnxTransforme still needs the 0.0.0.0 so it cannot be used with any of the newests versions of Microsoft.ML.OnnxRuntime.Gpu
Can you please advise?

Screenshots, Code, Sample Projects
Image

Many thanks
Vasilis

@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged label Nov 11, 2024
@ericstj
Copy link
Member

ericstj commented Nov 17, 2024

We reference an older version of the package so as not to require the latest. So long as their latest package is newer it should work. On .NET Framework you'd need a bindingRedirect -- which is pretty typical when using nuget packages on .NETFramework. Normally build tools will provide auto-generated bindingRedirects in this case.

Let us know if you tried this and it still didn't work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
untriaged New issue has not been triaged
Projects
None yet
Development

No branches or pull requests

2 participants