error MSB6003: The specified task executable "MakePri.exe" could not be run. System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.VisualStudio.Utilities.Internal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.

[HO-COOH]

Describe the bug

Almost the same as #4777 , happens occasionally when I update the wasdk nuget to a newer version.

Build log:

1>ListViewSelectedIndex-WinUI.vcxproj -> D:\WinUI-Bug\19-ListViewSelectedIndex\x64\Debug\ListViewSelectedIndex-WinUI\ListViewSelectedIndex_WinUI.exe
1>D:\WinUI-Bug\19-ListViewSelectedIndex\packages\Microsoft.WindowsAppSDK.1.6.240923002\build\Microsoft.Build.Msix.Pri.targets(304,5): error MSB6003: The specified task executable "MakePri.exe" could not be run. System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.VisualStudio.Utilities.Internal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
1>D:\WinUI-Bug\19-ListViewSelectedIndex\packages\Microsoft.WindowsAppSDK.1.6.240923002\build\Microsoft.Build.Msix.Pri.targets(304,5): error MSB6003: File name: 'Microsoft.VisualStudio.Utilities.Internal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
1>D:\WinUI-Bug\19-ListViewSelectedIndex\packages\Microsoft.WindowsAppSDK.1.6.240923002\build\Microsoft.Build.Msix.Pri.targets(304,5): error MSB6003:    at Microsoft.VisualStudio.Telemetry.TelemetrySessionInitializer.BuildInitializer(TelemetrySessionSettings telemetrySessionSettings)
1>D:\WinUI-Bug\19-ListViewSelectedIndex\packages\Microsoft.WindowsAppSDK.1.6.240923002\build\Microsoft.Build.Msix.Pri.targets(304,5): error MSB6003:    at Microsoft.VisualStudio.Telemetry.TelemetryService.get_DefaultSession()
1>D:\WinUI-Bug\19-ListViewSelectedIndex\packages\Microsoft.WindowsAppSDK.1.6.240923002\build\Microsoft.Build.Msix.Pri.targets(304,5): error MSB6003:    at Microsoft.Build.Msix.Telemetry.CreateTelemetrySession(String vsTelemetrySession)
1>D:\WinUI-Bug\19-ListViewSelectedIndex\packages\Microsoft.WindowsAppSDK.1.6.240923002\build\Microsoft.Build.Msix.Pri.targets(304,5): error MSB6003:    at System.Collections.Concurrent.ConcurrentDictionary`2.GetOrAdd(TKey key, Func`2 valueFactory)
1>D:\WinUI-Bug\19-ListViewSelectedIndex\packages\Microsoft.WindowsAppSDK.1.6.240923002\build\Microsoft.Build.Msix.Pri.targets(304,5): error MSB6003:    at Microsoft.Build.Msix.TelemetryOperation..ctor(String vsTelemetrySession, String eventNameSuffix)
1>D:\WinUI-Bug\19-ListViewSelectedIndex\packages\Microsoft.WindowsAppSDK.1.6.240923002\build\Microsoft.Build.Msix.Pri.targets(304,5): error MSB6003:    at Microsoft.Build.Msix.Pri.WinAppSdkGenerateProjectPriFile.ExecuteTool(String pathToTool, String responseFileCommands, String commandLineCommands)
1>D:\WinUI-Bug\19-ListViewSelectedIndex\packages\Microsoft.WindowsAppSDK.1.6.240923002\build\Microsoft.Build.Msix.Pri.targets(304,5): error MSB6003:    at Microsoft.Build.Utilities.ToolTask.Execute()
1>D:\WinUI-Bug\19-ListViewSelectedIndex\packages\Microsoft.WindowsAppSDK.1.6.240923002\build\Microsoft.Build.Msix.Pri.targets(304,5): error MSB6003: 
1>D:\WinUI-Bug\19-ListViewSelectedIndex\packages\Microsoft.WindowsAppSDK.1.6.240923002\build\Microsoft.Build.Msix.Pri.targets(304,5): error MSB6003: WRN: Assembly binding logging is turned OFF.
1>D:\WinUI-Bug\19-ListViewSelectedIndex\packages\Microsoft.WindowsAppSDK.1.6.240923002\build\Microsoft.Build.Msix.Pri.targets(304,5): error MSB6003: To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
1>D:\WinUI-Bug\19-ListViewSelectedIndex\packages\Microsoft.WindowsAppSDK.1.6.240923002\build\Microsoft.Build.Msix.Pri.targets(304,5): error MSB6003: Note: There is some performance penalty associated with assembly bind failure logging.
1>D:\WinUI-Bug\19-ListViewSelectedIndex\packages\Microsoft.WindowsAppSDK.1.6.240923002\build\Microsoft.Build.Msix.Pri.targets(304,5): error MSB6003: To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
1>D:\WinUI-Bug\19-ListViewSelectedIndex\packages\Microsoft.WindowsAppSDK.1.6.240923002\build\Microsoft.Build.Msix.Pri.targets(304,5): error MSB6003:
1>Done building project "ListViewSelectedIndex-WinUI.vcxproj" -- FAILED.
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
========== Build completed at 2:23 and took 01.327 seconds ==========
========== Deploy: 0 succeeded, 0 failed, 0 skipped ==========
========== Deploy completed at 2:23 and took 01.327 seconds ==========

Steps to reproduce the bug

1. Create a packaged winui3 app (C++)
2. Build once.
3. Upgrade the wasdk package to a newer version.
4. Build again.

Expected behavior

No response

Screenshots

NuGet package version

Windows App SDK 1.6.1: 1.6.240923002

Packaging type

Packaged (MSIX)

Windows version

No response

IDE

Visual Studio 2022

Additional context

No response

[tom-huntington]

Did you find a fix?

Oh restart visual studio.

[LegendaryBlair]

Hi @HO-COOH,
For this issue and issue #4777, are you still be able to repro it? If so, can you use msbuild -bl switch (msbuild MyProject.proj -bl) to generate a binary log file (.binlog) and share it out. For details, visit this document. Once .binlog file is provided, we can try to figure out what went wrong in the build process.

[HO-COOH]

@LegendaryBlair This issue really only happens when launching for debugging in Visual Studio and trust me, it will reproduce. It does NOT seems to reproduce when using msbuild in command line. In this screenshot I first build it inside visual studio (after downgrading the wasdk version, but upgrading will also easily reproduces), failed with makepri.exe, then run msbuild in the developer terminal, and it build successfully.

[LegendaryBlair]

Hi @HO-COOH,
Just want to clarify, did this error happen when you press F5 or when you clicked build on a project? F5 operation could do more things like app deployment.

In case the latter, you can try to collect .binlog file following the instructions below:

1. Install the Project System Tools Extension: This extension is available for Visual Studio 2017, 2019, and 2022. You can find it in the Visual Studio Marketplace and install it directly from Visual Studio.

2. Open the Build Logging Tool Window: Once the extension is installed, go to View > Other Windows > Build Logging to open the Build Logging tool window.

3. Start Logging Builds: In the Build Logging tool window, click the Start logging builds button. This will start capturing the build logs for any projects you build in Visual Studio.

4. Build Your Project: Now, build your project as you normally would by clicking the Build button or using the Build menu.

5. Stop Logging and Save the .binlog File: After the build is complete, go back to the Build Logging tool window and click the Stop logging builds button. You will be prompted to save the .binlog file, which contains the detailed build logs.

[HO-COOH]

@LegendaryBlair WASDKBuildRepro_Debug_x64_DesignTimeBuild_2024-12-26T23_35_20.5421073+08_00.zip

[LegendaryBlair]

Hi @HO-COOH
Today I used MSBuild Structured Log Viewer tool to analyze your log. It turned out that this build was successful.
I'm wondering if you can share your solution as zip file so that I can repro from my end.

[HO-COOH]

@LegendaryBlair
Sorry I might be drunk then, I think I build twice and it logged the success one.
Here is the corrected one. WASDKBuildRepro_Debug_x64_Build_2024-12-27T19_45_30.0459603+08_00.zip

[haonanttt]

Hi @HO-COOH , could you follow https://github.com/dotnet/maui/wiki/Capturing-Binary-Logs to:

1. set MSBuild project build log file verbosity to Diagnostic
2. and collect .binlog file again

From current binlog you uploaded, we didn't find enough information about why this happens. And also, we didn't repro this issue from our side

[HO-COOH]

@haonanttt

WASDKBuildRepro_Debug_x64_Build_2025-01-11T12_26_43.3351558+08_00.zip

[LegendaryBlair]

Hi @HO-COOH,
Thank you for providing the binlog file. Unfortunately, I was unable to find any additional clues from the log regarding why the Microsoft.VisualStudio.Utilities.Internal DLL cannot be found.

I also attempted to reproduce this issue by repeatedly upgrading the WindowsAppSDK version, but I was unable to replicate the problem.

Given that the frequency of upgrading the WindowsAppSDK is not high and that restarting Visual Studio resolves the issue, I don't have any further suggestions at this time.

[HO-COOH]

@LegendaryBlair Let's keep this issue open, and let other people, who also encounter this issue, to find this step to upload a binlog and see if additional information available.