search

sharpdx / SharpDX

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

Compatibility with UWP (5.x, 6.0...) #927

Open JimSEOW opened 7 years ago

JimSEOW commented 7 years ago

Please follow the discussion here

mrvux commented 7 years ago

I tried to make a sample today (SwapChainPanel with basic swapchain and clear, partly taken from https://github.com/minhcly/UWP3DTest), and yes it worked fine (tried both on my computer and windows phone).

Could be worth adding this to sample (to be honest I'd even remove rotating cube and such, as those part are exactly the same as a desktop app, so at least we only have one project with the exact minimal uwp setup required).

JimSEOW commented 7 years ago

@mrvux It is great to have V4 [faʊfiːɐ̯] team member expressing interest for UWP (XAML) InterOP.

The V4 contribution to SharpDX is always LEGEND!

JimSEOW commented 7 years ago

Update ... Interesting ...

https://github.com/minhcly/UWP3DTest (a) W10M 15240.1000 Emulator works (b) W10M 15240.0 950XL fails. (b) W10: 16232.1000 fails.

Without trying the latest W10M Emulator, I would have given out.

link that may be of interest to W10 XAML Interop

xoofx commented 7 years ago

@JimSEOW concerning your message, afaik, this is not correct. Any UAP10.0 version (UWP5.x) should be compatible with next versions. Same goes for .NET Standard 1.x that is compatible with .NET Standard 2.0 (and should be compatible with UWP6.0).

Afair, SharpDX is working fine on UWP Windows 10 15240.0.

For W10M, frankly, this is not an OS that is highly supported by Microsoft, so any crash on this platform is unlikely related to SharpDX but the platform itself. Same goes for 16232.1000 as they are preview builds, not supported and unstable. (unless proven by a strict equivalent DirectX C++ application that would work on these platforms)

aleksrdm commented 7 years ago

@xoofx New Windows SDK 16299 (Fall Creators Update) with .NET Standard 2.0 brought back System.Reflection.ObfuscationAttribute, and it is now in conflict with one declared in SharpDX package. Will this be resolved in 4.1.0?

xoofx commented 7 years ago

@aleksrdm I thing it can be removed entirely. PR Welcome. Open another issue please, thanks