Mark Schofield

> Actually, the errors observed on WinUI are: Error C1001: Internal compiler error. Error LNK1000: Internal error during IMAGE::BuildImage. I understand they may seem unrelated to the fix, but both...

> specifically on these WinUI arm64ec sample apps: WinUICppDesktopSampleApp/NativeDX12DesktopSample/WinUICppIsland2SampleApp/WinUICppIslandsSampleApp. These errors haven’t appeared on other samples or platforms. I'm trying to track down what I need to do to reproduce...

OK. A status update: 1. It looks like the "WinUICppDesktopSampleApp/NativeDX12DesktopSample/WinUICppIsland2SampleApp/WinUICppIslandsSampleApp" that you're referring to is a _Microsoft internal_ project. Is that correct? 2. I've attempted to build the containing repository,...

> We're still getting unnecessary batching between WindowsAppRuntimeAutoInitializer.cpp and UndockedRegFreeWinRT-AutoInitializer.cpp, which are being ClCompile Included separately. We could fold inclusion together, since all preprocessor definitions are now set globally. But...

Hmmm... This appears to be coupled to the #550. Even if I migrate 'win10-*' to 'win-*', I still see complaints of 'win10-*' RID's attributed to the Microsoft.WindowsAppSDK verstion 1.5.240227000.

Ah.. Some samples are parameterized, `:/Samples/DynamicDependenciesSample/DynamicDependencies/DirectX/D3D9ExSample.vcxproj` says: ```xml packages ``` The parameterization makes it tidier to see what's going on, TBH.

But it _looks like_ Visual Studio won't update parameterized Imports to NuGet artifacts when updating NuGet versions. Sad.

I _think_ the right answer is: 1. Force all samples to use the same packages folder - regardless of how they're built - by setting `` in the `:/Samples/nuget.config`. 2....