Exciting times! Starting today, Windows 10 is available for everyone: During the next twelve months, people can upgrade for free if they’re running Windows 7 or Windows 8 on their machine. What’s in it for us?
Well, we can see that Microsoft’s efforts of rewriting the Windows kernel over the past few years have really paid off: With Windows 10, universal apps enable each and every one of us to develop a single app and run it on phones, desktops and consoles alike!
I found that this is the perfect time to start a new big blog series about developing multi-platform online games. In this series, we’ll learn how to build a classical strategy game on Windows 10 using a (free!) Microsoft Azure backend. Azure enables us to create a backend that scales to arbitrary user counts, is easy to connect to various client platforms (not just Windows) and comes with full tool support for maximum productivity. Azure is a huge platform, and this can really be a little overwhelming – it was for me, and I think it will be even for more experienced developers. So we’re going to go through this step by step.
We’ll talk about building and deploying client and server, authenticating users, implementing the game logic itself on both sides, and sending push notifications, among others. Whenever you’ve got any questions, or are aching to see a specific feature, just add your thoughts to the comments below!
Okay – let’s do this!
Continue reading “Creating A Windows 10 Game With Azure”
In my previous post I started talking about potential issues you might face when upgrading C++ Windows Store apps to Windows 10 Technical Preview along with Visual Studio 2015 Preview.
Another thing that might occur when trying to deploy your app on your local machine is the following error:
error APPX3104: You cannot create an app bundle when building for platform ‘x86’ which is not included in the list of platforms selected for producting app bundle. Set platform to a one of following values: arm.
Note that this error doesn’t occur when deploying directly for your ARM devices, such as your Microsoft Surface or your Windows Phone.
This happens due to an entry in your .vcxproj file which has most likely been created by Visual Studio 2013:
Removing that entry will allow you to deploy for all platforms again. In fact, this line won’t be present if you create a new Visual C++ DirectX Windows app from scratch in Visual Studio 2015 Preview.
If you’ve recently installed the Windows 10 Technical Preview along with Visual Studio 2015 Preview, you might encounter the following compiler error after having upgraded your C++ Windows Store app:
error MSB3774: Could not find SDK “Microsoft.VCLibs, Version=14.0”
Chances are that Visual Studio automatically changed the Platform Toolset of your project:
This may be pointed out by your version control system as well as the only change in your project file after the upgrade:
Changing it back to Visual Studio 2013 (v120) (or <PlatformToolset>v120</PlatformToolset> in the project file) might resolve that issue for you.
If you’ve recently run the Windows App Cert Kit for your C++ Windows Store app, you might have encountered these or similar failures of the Supported API test:
API free in msvcr120_app.dll is not supported for this application type.
API malloc in msvcr120_app.dll is not supported for this application type.
API memcpy in msvcr120_app.dll is not supported for this application type.
API memmove in msvcr120_app.dll is not supported for this application type.
API memset in msvcr120_app.dll is not supported for this application type.
API swprintf_s in msvcr120_app.dll is not supported for this application type.
API wcslen in msvcr120_app.dll is not supported for this application type.
You’ve ensured you’re not building in Debug mode. The error persists. And you could swear, a few days ago, everything was fine.
Clearly, msvc dlls are not the type of code you would have written yourself. So what to do about this?
Luckily, the friendly folks over at the MSDN forums have isolated the issue, verifying that it can (temporarily) be resolved by uninstalling the recent Windows update KB2976978. This is the officially recommended workaround by Microsoft for the time being, as well.
Note that the above errors won’t cause your app to fail submission.
I’ll update this post as soon as there’s anything new!
Many games support script languages to be able to change their logic with having to re-compile: Blizzard allows customizing your World of Warcraft user interface with Lua, for instance, and CCP built EVE Online around Stackless Python.
I’ve been messing around with C++ Windows Store Apps recently, more specifically with DirectX games for Windows Store. It required quite a bit of an effort to get Lua to run (and validate) with Windows Store apps, and I’d like to share my learnings.
- Download and install Microsoft Visual Studio Express 2013 for Windows, and create a new Visual C++ Windows Store DirectX App.
- Download and extract the Lua 5.2.3 source code.
- Copy and include the contents of the Lua src folder in your project.
- VC++ does not support C++/CX extensions in files compiled as C. Select all Lua C source code files, and open the properties dialog. In Configuration Properties > C/C++ > General, change Consume Windows Runtime Extension to No.
- The precompiled header file (pch.h) for the Windows Store App is C++ and can’t be used from C. With all Lua C source code files still selected, open the properties dialog. In Configuration Properties > C/C++ > Precompiled Headers, change Precompiled Header to Not Using Precompiled Headers.
- Some of the functions in Lua call system and IO functions that are not supported by Windows Store Apps – but we’re not going use them anyway:
- First, we need to disable deprecation warnings for these functions treated as errors. In the properties of your C++ project, in Configuration Properties > C/C++ > Preprocessor, add _CRT_SECURE_NO_WARNINGS to your Proprocessor Definitions.
- Next, in luaconf.h, remove the LUA_DL_DLL define in the #if defined(LUA_WIN) section.
- In lualib.c, remove the io_popen and io_pclose functions, and remove the popen entry from the iolib array in the same code file.
- In lua.c, loadlib.c and loslib.c, replace all calls to the getenv function by NULL. These functions are designed to handle NULL as a failed call to getenv.
- Finally, in loslib.c, remove the os_execute function and its entry in the syslib array in the same file.
- In the source file luac.c, remove the main function.
- Build and deploy the solution, and observe that validating it using the Windows App Certification Kit succeeds, except for the Branding validation test that requires you to replace the app icon images.
Congratulations, you’re good to go! Go ahead, and take your first steps with the overview of the Lua C API!
1. Justin M. Chase. Embedding Lua into a Windows Store app. January 13, 2014.