sharpdx / SharpDX

SharpDX GitHub Repository
http://sharpdx.org
MIT License
1.68k stars 641 forks source link

3.1.1 nuget package fails cert for Windows8.1 Store app #843

Open faaland opened 7 years ago

faaland commented 7 years ago

Building with 3.1.1 from nuget with VS 2015 Update 3 and latest tools fails with:

Supported APIs Error Found: The supported APIs test detected the following errors: This API is not supported for this application type - Api=D3D11On12CreateDevice. Module=d3d11.dll. File=SharpDX.Direct3D11.dll. This API is not supported for this application type - Api=D2D1GetGradientMeshInteriorPointsFromCoonsPatch. Module=d2d1.dll. File=SharpDX.Direct2D1.dll. Impact if not fixed: Using an API that is not part of the Windows SDK for Windows Phone Store apps violates the Windows Phone Store certification requirements.

I tried submitting officially just in case and it failed for the same reason. I'm not actually calling either of these, so I have to think it's not related to my code.

edit: If I remove those two externs from the Functions.cs of each assembly, my app passes. It would sure be nice if the nuget package just worked though...

xoofx commented 7 years ago

I'm sorry, but you will have to try to use an older version of SharpDX for now. There is no plan to re-introduce support for Windows Phone. Currently, SharpDX should only support desktop and UWP apps.

Keeping this issue open because while the D3D11On12CreateDevice is a certified API I'm not sure for D2D1GetGradientMeshInteriorPointsFromCoonsPatch... PR is welcome if not.

faaland commented 7 years ago

Clarification: one of the packages I built was for Windows Phone, but the other was for PC targeting 8.1. Neither of them passed. I didn't check for targeting Win10.

The bummer about going to an earlier version is that the same version (3.0.0 I think) that introduced the API calls also fixed the exception while setting values for shaders, which was necessary for me. However, building from source without the two APIs wasn't hard.

faaland commented 7 years ago

Oh, I see the error I posted was from the Phone version. The PC version had the same error message but slightly different "impact" verbiage.