![]() ![]() It is very useful when you have an APPX package of an app which is not available in Windows Store. In Windows 10, Microsoft made it possible to sideload Universal apps easily. Just tell Visual Studio the name of your ARM machine and press F5 to deploy it remotely.RECOMMENDED: Click here to fix Windows issues and optimize system performance The other cool thing about this option is that once you're set up you won't have to create packages manually and side load them anymore. #Download Metro Sideloader install#This will install the necessary SDK components to allow creation of D3D Debug devices. ![]() Or - Install the Remote Debugging tools for Visual Studio on the target machines. Or - Go to DirectXBase.cpp and remove the D3D11_CREATE_DEVICE_DEBUG flag from the code. Any one of these should give you the desired result:Ĭreate a Release package and deploy that instead of a Debug package. Here are a few different options that will allow you to unblock yourself. Device creation will fail if the Windows SDK is not installed on the machine running the code. To be clear, the process I use for building is going to Project -> Store -> Create App Packages and choosing the No option for uploading to the Windows Store.ĭoes anyone have any ideas on what might be going wrong with the build or installation process?Īre you side loading a Debug version of your DirectX app onto a machine that does not have the Windows SDK installed? Visual Studio's default DirectX projects and the samples on MSDN both request the D3D11_CREATE_DEVICE_DEBUG flag when creating the D3D Device. Any of the DirectX samples that I tried have all failed (including the native C++ samples that do not use C# at all). The only test project that worked properly was a simple C# project that did not use DirectX at all. I have packaged a few different test programs (MSDN Samples) that have all installed on their machines, but we get the same results that they will not run (again, all samples run fine on my development machine when building them). I have checked the package file, and the dll file is included in the package after the build process is complete. This makes me believe that the dll may not be installing or referenced correctly upon installation. The C# and XAML interface appears, but the DirectX portion of the application is not visible and the entire application shuts down within a few seconds. The tile appears in the start screen and the program will launch for a few seconds. When I send the package files to other individuals within the company, the installation appears to work fine by installing with the PowerShell script. All of this works flawlessly on my development machine from within Visual Studio (and also when installing the package). The second project is the C# project that references this dll for drawing functions and includes a XAML interface and most of the program logic. The purpose for this is to expose the Direct2D and DirectWrite libraries that seem to be unaccessible to a C# project. The first is a C++ project that is set to build a dll file. However, when I try to create an app package that I can pass along to others within my company for testing purposes, the application will not run properly. For now, I have been developing and testing from Visual Studio on my desktop computer and everything works fine. ![]() ![]() I am currently developing a Windows Store App that will eventually be targeted at the ARM devices when they are available. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |