SDK DLLs should be signed: IppDotNetSdkForQuickBooksApiV3.dll blocked by Windows Smart App Control

If I enable Smart App Control (in Windows 11 25H2), I'm unable to build my project that uses the .NET SDK. Smart App control pops up a message saying that IppDotNetSdkForQuickBooksApiV3.dll is blocked, and Visual Studio reports:

> Unknown build error, 'Could not load file or assembly 'file:///C:\Users\DHuang\.nuget\packages\ippdotnetsdkforquickbooksapiv3\14.7.1.5\lib\net472\IppDotNetSdkForQuickBooksApiV3.dll' or one of its dependencies. An Application Control policy has blocked this file. (Exception from HRESULT: 0x800711C7)'

If I check Windows Event Viewer, under Applications and Services -> Microsoft -> Windows -> CodeIntegrity -> Operations, I see this error logged:

> Code Integrity determined that a process (\Device\HarddiskVolume3\Program Files\Microsoft Visual Studio\2022\Professional\MSBuild\Current\Bin\amd64\MSBuild.exe) attempted to load \Device\HarddiskVolume3\Users\DHuang\.nuget\packages\ippdotnetsdkforquickbooksapiv3\14.7.1.5\lib\net472\IppDotNetSdkForQuickBooksApiV3.dll that did not meet the Enterprise signing level requirements or violated code integrity policy (Policy ID:{0283ac0f-fff1-49ae-ada1-8a933130cad6}).

Users of our application also encounter the same error, so it's not just a problem during development.

I notice that none of the SDK DLLs have a digital signature. I think they should be signed in order to pass Smart App Control's checks.

Start by locating the build or packaging entry point that produces IppDotNetSdkForQuickBooksApiV3.dll and the other SDK DLLs, then inspect how the NuGet package is assembled. Reproduce the Windows Smart App Control or Code Integrity failure described in the issue and verify the published DLLs have valid digital signatures and are no longer blocked.

Written by the indexing model from the issue text.