From f522b97e77a9a3f27415b85c264fa5ab990c959d Mon Sep 17 00:00:00 2001 From: Simon Nattress Date: Thu, 3 Sep 2015 19:40:42 -0700 Subject: [PATCH] Update .Net Native fwlink with new known issues Add guidance for two new issues: 1. WACK failure for apps with native code and "Optimize Code" unchecked in project properties. Developer experience mode pulls in illegal Store APIs. 2. Large applications failing compilation in Store. The toolchain distributed with Windows 10 Tools 1.1 mitigates this. --- Documentation/ilcRepro.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/Documentation/ilcRepro.md b/Documentation/ilcRepro.md index c0dfa79d11..a6cd277019 100644 --- a/Documentation/ilcRepro.md +++ b/Documentation/ilcRepro.md @@ -25,6 +25,19 @@ For help with any other issues, please share their details at https://connect.mi ## Known Issues +### CoCreateInstance is not supported for this application type when running the Windows Application Certification Kit (WACK) +This error shows up in applications with a native code component: + +`API CoCreateInstance in api-ms-win-core-com-l1-1-1.dll is not supported for this application type. SomeBinary.dll calls this API.` + +This error can occur when running the WACK with your application in Release configuration and "Optimize Code" unchecked in your project properties. Ensure that "Optimize Code" is checked when submitting your application to the Store. + +### Application was too large to be compiled in the Store +Some apps may successfully compile with the .NET Native Toolchain during development but fail to compile in Store due to their size. This issue has been mitigated with the release of the .NET Native Toolchain included in the Windows 10 Tools 1.1 Update. + +You can see which version of the .NET Native Toolchain you have by opening AppxManifest.xml in the app package you submitted to Store and looking for `