Here we explain how to build and run the Hilo sample, how the source code is organized, and what tools and languages it uses.
After you download the code, see the next section, Building and running the sample, for instructions.
Build the Hilo project as you would build a standard project.
- On the Microsoft Visual Studio menu bar, choose Build > Build Solution. This step compiles the code and also packages it for use as a Windows Store app.
- After you build the solution, you must deploy it. On the menu bar, choose Build > Deploy Solution. Visual Studio also deploys the project when you run the app from the debugger.
- After you deploy the project, pick the Hilo tile to run the app. Alternatively, from Visual Studio, on the menu bar, choose Debug > Start Debugging. Make sure that Hilo is the startup project. When you run the app, the hub page appears.
You can run Hilo in any of the languages that it supports. Set the desired language and calendar in Control Panel. For example, if you set the preferred language to German and the system calendar (date, time, and number formats) to German before you start Hilo, the app will display German text and use the locale-specific calendar. Here's a screen shot of the year groups view localized for German.
The source code for Hilo includes localization for English (United States), German (Germany), and Japanese (Japan).
For general info on designing Windows Store apps, see Planning Windows Store apps.
The Hilo project uses Visual Studio solution folders to organize the source code files into these categories:
- The images folder contains the splash screen, the tile, and other images.
- The strings folder contains subfolders named after supported locales. Each subfolder contains resource strings for the supported locales (in .resjson files).
The Hilo.Specifications project contains unit tests for Hilo. It shares code with the Hilo project and adds source files that contain unit tests.
You can reuse some of the components in Hilo with any app with little or no modification. We found that organizing files by feature was a helpful pattern. For your own app, you can adapt the organization and ideas that these files provide. When we consider a coding pattern to be especially applicable to other apps, we note that.
When we considered which language to use for Hilo, we also asked these questions:
We chose Visual Studio Express as our environment to write, debug, and unit test code, along with Microsoft Test Manager to manage testing. We used Team Foundation Server to track planned work, manage bug reports, version source code, and automate builds. We also used Microsoft Expression Blend as a versatile CSS editor.
The document Getting started with Windows Store apps orients you to the language options for creating Windows Store apps.
Build date: 11/29/2012