-
Notifications
You must be signed in to change notification settings - Fork 83
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
"No executable found" when integrating Microsoft.ML.OnnxRuntime.DirectML #472
Comments
Double checking the same project with the Rider extension works both in Debug and Release, hence, with DirectML referenced and not referenced. |
Added a sample app here: https://github.com/llfab/Samples/tree/main/FailedPreviewer Works in Debug because DirectML nuget package is only referenced in Release.
|
Filed an issue here: microsoft/onnxruntime#20574 |
<ItemGroup>
<PackageReference Include="microsoft.ai.directml" Version="1.15.2" Condition="'$(Configuration)' != 'Debug'" GeneratePathProperty="True" />
<PropertyPageSchema Remove="$(PkgMicrosoft_AI_DirectML)/**/*.*" />
</ItemGroup> Will fix the previewer, note thatGeneratePathProperty is important. Since it's a VS bug, I'm closing the issue |
Nice, we will try out... |
Describe the bug
When I have integrated a reference to DirectML using
<PackageReference Include="Microsoft.ML.OnnxRuntime.DirectML" Version="1.17.3" Condition="'$(Configuration)' != 'Debug'" />
the previewer fails with "No executable found".
The Log is as follows:
When I switch to Debug (where DirectML is deactivated), close the last xaml document and re-open the xaml document, the previewer works with the following output:
This may be due to DirectML being Windows only. Potentially, that changes the Runtime Identifier or TargetPlatformIdentifier under the hood causing the previewer execution detection to fail.
To Reproduce
As above integrate DirectML, rebuild and re-open xaml file
AvaloniaVS plugin version
11.5
Avalonia version
11.0.10
Visual Studio version
17.9.6
Relevant log output
Additional context
No response
The text was updated successfully, but these errors were encountered: