microsoft / microsoft/WindowsAppSDK-Samples
Cannot build WindowsML projects
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 1k
- Forks
- 335
- Avg merge
- 5d 1h
- Merged PRs (30d)
- 8
Description
Hi all,
I've tried to build the project of "experimental/Samples/WindowsML/cpp/CppConsoleDesktop/". However, it fails.
This is the snapshot of the packages I've downloaded by "Nuget" in VisualStudio Project
As the document mentioned, I also install the runtime under packages\Microsoft.WindowsAppSDK.Runtime.1.8.250702007-experimental4\tools\MSIX\win10-x64\
Shall I do other settings to let it work or manually add the included path?
Thanks
Error Messages:
MSB406, Could not load file or assembly 'file:///C:\Program Files\Microsoft Visual Studio\2022\Professional\MSBuild\Microsoft\VisualStudio\v17.0\AppxPackage\Microsoft.Build.Packaging.Pri.Tasks.dll' or one of its dependencies.
I've done the same thing under another platform, it shows the folloing:
LNK1181 cannot open input file '..\CppConsoleDesktop\packages\Microsoft.WindowsAppSDK.InteractiveExperiences.1.8.250626001-experimental\build\native....\lib\native\win10-x64\Microsoft.UI.Dispatching.lib
===== Platform Issues =====
Visual Studio: VS2022-17.14
Windows-x64
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the build for experimental/Samples/WindowsML/cpp/CppConsoleDesktop/ with Visual Studio 2022 17.14 on Windows x64. Check the NuGet packages and Microsoft.WindowsAppSDK.Runtime.1.8.250702007-experimental4 path mentioned in the report, then investigate the MSB406 and LNK1181 messages. Done means the sample builds without either missing-assembly or missing-library error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100