Sentence similarity: Project debug failed with error "Two TorchSharp runtime packages have been referenced (both libtorch-cpu and libtorch-cuda)".

[v-Hailishi]

System Information (please complete the following information):
Windows OS: Windows-11-Enterprise-22H2
ML.Net Model Builder 2022: 17.15.0.2322401 (Main Build)
Microsoft Visual Studio Enterprise: 2022(17.5.2)
.Net: 6.0

Describe the bug

• On which step of the process did you run into an issue:
  Project running failed with error "Two TorchSharp runtime packages have been referenced (both libtorch-cpu and libtorch-cuda)".

TestMatrix
home-depot-sentence-similarity-small.csv

To Reproduce
Steps to reproduce the behavior:

1. Select Create a new project from the Visual Studio start window.
2. Choose the C# Console App (.NET Core) project template.
3. Add model builder by right click on the project.
4. Select "Sentence similarity" scenario.
5. On Data page, choose the attached .csv data source and set the three options like below.
   
6. On the Train page, click "Start training" button to complete the training.
7. Press "F5" to debug the project.

Expected behavior
Project debug successful.

Screenshot

Additional context

1. There are many errors in "consumption.cs" and "training.cs" files.
   
   

2. The issue is not repro in the generated Console App and Web API projects.

[JakeRadMSFT]

@v-Hailishi did you try training using GPU and CPU at some point for that project? Does removing one of them from CSPROJ work?

[v-Hailishi]

@JakeRadMSFT The bug occurs after training "Sentence similarity" scenario successfully using CPU.
The bug would be fixed if you delete the error condition in "libtorch-cpu.targets" file.

[JakeRadMSFT]

@v-Hailishi can you share your csproj?

[v-Hailishi]

@JakeRadMSFT Attached my csproj.
ConsoleApp4.zip

[zewditu]

@v-Hailishi thanks for sharing csproj, The two torchs (torch cpu and toch GPU ) are installed in the same project we need to check if there is a different torch and then remove it

[v-Hailishi]

The bug is still repro on the latest main build 17.16.0.2326803.

[luisquintanilla]

Closing since it's been fixed in MB.

[luisquintanilla]

@zewditu can you please look into this. Thanks.