The applicationView variable has a CoreWindow property, but it’s null for some reason, so we can’t do anything at the moment.

Initialize(CoreApplicationView applicationView): this is the first function called when running the application.

The methods enforced by IFrameworkView are the following:

MyViewProviderFactory factory = new MyViewProviderFactory ().

// Tell CoreApplication to create a view instance through the factory.

And yes, you guessed it correct, your window class must implement it. The only method that is enforced by this interface is CreateView, that returns a IFrameworkView object. You can’t instance them directly, as they must be created via a proxy class that implements the IFrameworkViewSource interface. Window creation for Windows Store applications is a bit different from everything so far. Now, add references to SharpDX.dll, and. I will be using the stable versions (2.5.0 as of the writing of this tutorial) and updating when necessary. You can download the latest stable version (recommended, since DirectX SDK is required for compiling) or get a copy of the source code and build it by yourself. Get yourself a copy of SharpDX’s libraries.

Now you can safely delete all the files except the Assets folder (contains the Windows Store icons for your program), the Package.appxmanifest file (has information about your application deployment settings) and the *_TemporaryKey.pfx file (the temporary certificate for signing the app). It’s a series of wrappers that let you access the DirectX libraries from your C# code, and since XNA looks like a dead end, it’s what I’ll be writing about from now on.īegin creating a new Windows Store > Blank App (XAML) (remember that this template is only available if you are running Visual Studio 2012 in Windows 8!) Well, now you can do this, thanks to the SharpDX project. Sealed classes, no member functions for structures… this is the 21st century, please let me use a modern programming language and not one that has been patched through 30 years of existence. So, if you want to target Metro apps with DirectX, the only initial option is to use C++/CX, which in my humble opinion is a total overkill and a huge step back. The only alternative for graphics programming is using pure DirectX 11 now that it has been merged in the Windows core (no more separate DirectX SDK downloads, yay!) and Microsoft is going to actively promote it (Visual Studio 2012 includes a nice node-based shader editor). Since Microsoft has decided that “XNA is mature enough” and Shawn Hargreaves has moved to Windows Phone, it looks like we won’t see a version 5 that supports Metro-style applications.

UPDATE: you can learn how to initialize Direct3D in XAML applications in this new article.

Create dxgi factory 2 download