navigate site menu

Start learning with our library of video tutorials taught by experts. Get started

Distributing Windows Store Apps

Distributing Windows Store Apps

with David Gassner

 


Start selling or distributing your apps through the Microsoft Windows Store with these tutorials from author and experienced developer David Gassner. Beginning with a completed application that was built with XAML and C# in Visual Studio 2012, the course describes available business models such as free trials, in-app purchases, and advertising; how to test an app prior to distribution; how to get a developer account and reserve an app name; and how to upload an app.
Topics include:
  • Testing an app on your development computer
  • Creating a security certificate and testing package
  • Creating a developer license
  • Opening a developer account
  • Reserving an app name
  • Publishing a privacy statement
  • Taking app screenshots

show more

author
David Gassner
subject
Developer, Desktop Apps
software
Windows 8, Visual Studio
level
Beginner
duration
52m 51s
released
Apr 08, 2013

Share this course

Ready to join? get started


Keep up with news, tips, and latest courses.

submit Course details submit clicked more info

Please wait...

Search the closed captioning text for this course by entering the keyword you’d like to search, or browse the closed captioning text by selecting the chapter name below and choosing the video title you’d like to review.



Introduction
Welcome
00:04My name is David Gassner and this is Distributing Windows Store Apps.
00:09In this course, I'll show you how to test your app on your development computer
00:13and how to side load and test apps on other Windows 8 and Windows RT devices.
00:18I'll then describe how to create a developer account and reserve your app name,
00:23and how to associate your app with the Windows Store from Visual Studio.
00:26I'll describe the process of creating and uploading app packages, and then how
00:32to provide the app's Description, Screenshots, Promo Graphics, Privacy Policy, and
00:40other required information.
00:42Regardless of how you build your Windows Store apps with Visual Basic, C#, C++,
00:48or JavaScript, I hope this course gives you the information you need to start
00:52distributing your app through the Windows Store.
Collapse this transcript
What you should know before watching this course
00:00Windows 8 Store apps can be built with a variety of technologies and
00:04programming languages.
00:06If you're already comfortable with Windows Presentation Foundation or
00:09Silverlight, or other Microsoft technologies, you might choose to work with
00:14XAML, Extensible Application Markup Language, and do your programming in C#,
00:18Visual Basic, or C++, or if you already know how to work with Web standards,
00:23building modern apps that work in web browsers, you can use those same technologies
00:28here, using HTML and Cascading Style Sheets to layout your application and
00:33JavaScript to control it.
00:35My recommendation is to build your Windows Store apps with the skills you
00:39already have, if you already know one of the Microsoft languages, use that, and
00:44if you're a web developer who knows how to build modern apps that work in web
00:48browsers like Internet Explorer and Chrome, use those tools.
00:52Regardless of which application programming languages you use, you'll use the
00:56same development tools to build and distribute your Windows Store apps,
01:00Visual Studio 2012. There are a number of editions of Visual Studio to choose
01:05from, including the paid versions, Professional, Premium, and Ultimate, and a
01:10free edition, Visual Studio 2012 Express for Windows 8, that's the version of
01:16Visual Studio that I'll use throughout this course.
01:19If you're just getting started, here are some of the foundational skills that you'll need.
01:23If you're new to XAML, I recommend looking at Silverlight 5 Essential Training,
01:28and then the language courses, C# Essential Training, and C++ Essential Training.
01:34If you want to build Windows Store apps with Web standards, look at the
01:38lynda.com courses on HTML, JavaScript, and Cascading Style Sheets, and then when
01:44you're ready to build your first apps, you'll find a number of available courses
01:48that can help you get started, including Building Your First Windows Store App
01:52with XAML and C#, or a nearly identical course with Visual Basic.
01:57There's also a course about building games using HTML and JavaScript, and then an
02:02extensive course Building Windows Store Apps Essential Training.
02:06Once you've built your application and tested it, you're ready for that final
02:10step, deploying and distributing your app through the Windows Store, and that's
02:15what this course is about, showing you how to do your final testing, and then
02:19how to package and describe your app for distribution to the universe of Windows
02:238 and Windows RT users.
Collapse this transcript
Using the exercise files
00:00This course includes Exercise Files that you can use to follow along with
00:04the demos on screen.
00:06I've placed the Exercise Files on my Desktop, but you can copy them anywhere on your hard disk.
00:11The Exercise Files include a number of copies of an application, called the Roux
00:16Academy Art Conference.
00:18The Roux Academy folder in the Start folder is a Visual Studio Solution.
00:23You can double-click the solution file, RouxAcademy.sln and that will open up
00:28the beginning project in Visual Studio.
00:30If you have Visual Studio Express 2012 for Windows 8, you can use that free
00:35product, or you can use any of the pay- for-license versions of Visual Studio
00:40Professional, Premium and so on.
00:43In addition to the starting version of the application, I've also provided
00:46a Solution version.
00:48This version has all of the coding changes that I make throughout the course.
00:52And finally, under the Assets folder, there's a zipped version of the starting
00:56version of the application, the zip file is called RouxAcademyBackup.zip, and I
01:01provided it so that you can walk back and start over from scratch at any time
01:06through the process.
01:07This course describes how to submit an application to the Windows store and
01:11I've provided this application so that you can experiment, but it's very
01:15important that you don't try to submit this exact application through your
01:19Windows Store developer account.
01:21First of all, I will have reserved the actual application name and you won't be
01:26able to submit it yourself, but more importantly, this application is designed
01:30for experimentation and for understanding how Windows Store apps work.
01:34It's not designed to actually be submitted and distributed through the Windows Store.
01:39I encourage you to build your own Windows Store application and follow along
01:44these exercises with that app, so that you can see how to submit your own apps
01:48to the Windows store and see your apps used by actual Windows 8 users.
Collapse this transcript
1. Testing an App
Testing your app on your development computer
00:00The first step in getting ready to submit your app to the Windows Store is to do
00:04a complete test of the app's features.
00:07Throughout the exercises in this course, I'm going to be demonstrating using an
00:11application that I originally built in a course called Building Your First
00:15Windows Store App with XAML and C#.
00:18The name of the application is ArtConference, and it's part of a solution
00:22called RouxAcademy.
00:24I'll be using the version of the application that's in the Exercise Files.
00:27You can either follow along with this application, or you can use your own
00:31Windows Store Application.
00:34I'll double-click the RouxAcademy.sln file and that opens the project in Visual Studio.
00:40Before I try to run it, I'll build the application.
00:43I'll go to the Menu, and select BUILD > Build Solution.
00:48And that should result in getting rid of any errors that might appear when the
00:52application first opens.
00:54Then, I'll run the application by selecting Debug > Start Without Debugging.
01:00You can also press ctrl + F5.
01:04This application starts by downloading an RSS XML feed from a
01:09publicly accessible web page.
01:12It uses the data to display this list.
01:14The list items contain an artist name, and a photo of the artist.
01:19The photo of the artist and the artwork are downloaded from the public website as well.
01:24When you click on an item in the list, you see the details of that item on the
01:28right side of the screen.
01:29This application implements a few special Windows 8 features.
01:33For example, when you've selected an artist from the list, you can go to
01:38the Share charm, and you'll be able to share information about the artist in an email.
01:44You must have configured the mail application that comes with Windows 8 for this to work.
01:49I'll click back on the application, and I'll right-click on the right side of
01:53the screen, and show that an app bar appears with a Refresh button.
01:57When I click the Refresh button, it re- executes the call to the RSS feed, and
02:02refreshes the display.
02:04And finally, when you click an artist and display the details of that artist on
02:08the right, that results in creating a live tile.
02:12The application tile will update and show the selected artwork.
02:17In addition to testing these basic features, when you're getting ready to submit
02:21an application to the Windows Store, you should make sure that the application
02:25behaves well in the Snapped and Filled views.
02:29These are the visual states that an application must handle in order to be
02:33certified for the Windows Store.
02:35To test this, I'll open another Windows Store App.
02:38I'll open the Weather Application.
02:41Then, with that application open, I'll move the cursor down to the lower-left
02:46hot corner, and then up again.
02:48And I'll click my Art Conference application, drag it over to the right and then
02:53back into the left and let it snap into place.
02:57I'm checking to make sure that the application adjusts correctly.
03:00And in this case, the application's title has a smaller font in the
03:05Snapped visual state.
03:07I'll drag the separator over, and put the application in the Filled state, and
03:12make sure that it looks good there too.
03:15And then I'll take it back to full screen.
03:17Finally, you should also test your application in a variety of resolutions.
03:22The easiest way to do that is to use the Windows 8 Simulator that's
03:26included with Visual Studio.
03:29I'll return to Visual Studio, and on the Toolbar, I'll change my Testing
03:33Environment from Local Machine to Simulator.
03:36Then, once again, I'll select Debug > Start Without Debugging.
03:41And that will launch the Windows 8 Simulator and load the application.
03:47Now, I'll rotate the Simulator clockwise 90 degrees, and put it into Portrait Mode.
03:53And this shows me what the application will look like approximately with that orientation.
03:59Then, I'll flip it back counterclockwise.
04:02I'll click on an item and see how it's looking.
04:05And then I'll try a couple of different resolutions.
04:07I'll click the Change Resolution icon, and change the resolution of the
04:12Simulator to 1024 x 768.
04:16I'll click around, see how the application looks.
04:20Then, once again, I'll rotate it clockwise, and see how it looks now.
04:25So, these are the kinds of tests you want to take your application through.
04:29Use the Simulator to see how the application behaves in a variety of
04:33orientations and resolutions, and make sure that the application looks okay in
04:38the Snapped and Filled visual states as well.
04:41If you haven't used those visual states before, you can look at the code in this
04:45finished application for some tips on how to implement them.
Collapse this transcript
Creating a security certificate and a testing package
00:00Once you've completed your functional testing on both your development computer
00:04and in the Windows 8 Simulator, it's a good idea to also test your application
00:09on other Windows 8 and Windows RT devices.
00:12To do this, you'll need to create a testing package: a collection of files that
00:17can be copied to these other devices.
00:19And to create the package, you'll need to create a digital certificate to sign the package.
00:24I'm going to close the Windows 8 Simulator by going to the taskbar,
00:27right-clicking on the icon for the Simulator, and selecting Close Window.
00:32Then, I'll open the application's manifest file which is named
00:36package.appxmanifest.
00:38You can find it in the Solution Explorer Panel.
00:41Before you create the certificate, you should update all of the text that's
00:45associated with your application.
00:46For example, on the Application UI Tab, I'll change the display name from
00:51ArtConference --the original project name-- to Roux Academy Art Conference.
00:57Then, I'll type in a description.
00:59This application displays featured artists from the Roux Academy Art Conference.
01:04Next, I'll go to the Packaging Tab.
01:07On the Packaging Tab, I'll change the Package Display Name using the same value
01:11that I put in the Application UI;
01:14Roux Academy Art Conference.
01:16And I'll change the Publisher display name.
01:18When you're building your own application, the Publisher display name defaults
01:22to your account name, but you might want to use your company name.
01:25I'll change it to Roux Academy.
01:27I'll save those changes by pressing ctrl + s, and now I'm ready to create the certificate.
01:32I'll click the Choose Certificate button, and click Configure
01:36Certificate > Create Test Certificate.
01:39I'll change the Publisher Common Name to the same value I put into the
01:42Packaging Tab, Roux Academy.
01:45Then, I'll type in a password.
01:46You type the password in twice, making sure they match, and make sure that you
01:50use a password that you can easily remember.
01:53You won't be able to retrieve it easily later.
01:56After typing the password twice, I'll click OK, and then click OK, and confirm
02:01that I want to replace the existing certificate.
02:03So now, I've created the certificate, and I'm ready to create my testing package.
02:08I'll save my changes to the Manifest again.
02:10Then, I'll go to the Menu, and select STORE > Create App Packages.
02:15The Create App Packages dialog asks whether I'm building packages to upload
02:20to the Windows Store.
02:21I'm not, I'm only creating a testing package initially.
02:24So, I'll select No, and click Next.
02:27Now, I'm asked where I want to put the package.
02:30The default will be a subfolder called App Packages under your Project folder.
02:35But to make this easier to find, I'm going to click the Browse icon, and select my Desktop.
02:41The version of the package is set by default to 1.0.0.0.
02:47If you leave this checkbox checked, each time you build a new version of the
02:50package, the dot value will update by 1.
02:53If you want to keep it at .0, uncheck the checkbox.
02:57Then you have explicit control.
02:59Finally, set the solution configuration, changing it from Debug to Release.
03:04I'm selecting Release for any CPU.
03:07This particular application doesn't have any native code in it, it's all C# and
03:11XAML, so this app should run fine on any Windows 8 or Windows RT computer.
03:17And I'll leave the checkbox selected to include public symbol files.
03:21This will make sure that if there's a crash during testing, that I'll get the
03:25maximum available information about what caused the crash.
03:29Now, I'm ready to create the Package.
03:31I'll click the Create button, and after a few moments, the testing package is
03:35created on my desktop.
03:36I can click the link here under the output location, and that opens the Windows
03:408 File Explorer, and takes me to the folder where the package was created.
03:45For testing, you only need this folder.
03:48You won't need this file with a file extension of .appxupload.
03:50I'll talk about what that file is doing later on in the course.
03:55But, I'm going to delete that file.
03:57And then, I'll drill down into this folder and show you what's inside.
04:01There's a folder with a .resources extension.
04:04It has a lot of internationalization folders.
04:06In the primary folder, there is a script called Add-AppDevPackage.
04:10That's going to be used by Windows PowerShell eventually.
04:13And then, there are a number of other files including your security certificate.
04:18To get the package ready to transfer to another computer, I'll go back to the
04:21folder containing the package, I'll right-click, and select Send
04:25To > Compressed (zipped) folder.
04:28And that creates a zip file.
04:29I can now email the file or transfer it to another computer using SkyDrive, or
04:34Dropbox, or any other file sharing mechanism.
04:37So, now you have a testing package that's ready for sideloading onto another
04:41Windows 8 or Windows RT computer.
04:44And I'll show you how to complete the sideloading process in the next video.
Collapse this transcript
Creating a developer license on other computers
00:00When you use Visual Studio to build your application you're prompted to create a
00:04developer license on your development system automatically, but you can't use
00:08Visual Studio on Windows RT devices at all.
00:11And on lower powered Windows 8 devices such as those that have an atom processor
00:16you probably don't have enough power to run Visual Studio adequately.
00:20Fortunately, it's very easy to add a developer license to any Windows 8
00:24computer using Windows PowerShell, a scripting environment that's a part of the
00:28Windows Operating System.
00:30Here the steps go to the Start screen and type Power that'll take you to the
00:35Windows PowerShell application, make sure you run Windows PowerShell as an
00:39administrator, right-click on it, and choose Run as administrator from the App bar.
00:45When prompted with a user account control dialog, click Yes.
00:49Now type this command Show-WindowsDev, then press the Tab key and that should
00:57auto complete to Show- WindowsDeveloperLicenseRegistration, press Enter and
01:04you'll see a dialog pop-up.
01:06If you already have a Developer License on this computer, you'll see this dialog
01:10asking you to Renew your developer license.
01:13If you don't have a developer license yet you'll be asked to create one from scratch.
01:17I'll click I Agree and on my computer and next I'm prompted for my Microsoft
01:22account credentials.
01:23I'll type my account credentials and then Sign In.
01:27And after a few moments, I'll see my Developer License has been updated.
01:31The expiration date will depend on your status as a Windows 8 developer.
01:36If you don't have Windows Store account yet your expiration date will be one
01:39month after the current day.
01:41If you do have a Windows store account your expiration date will be 90 days
01:45from the current date, either way you can always renew the license whenever it expires.
01:51Click Close, and then close the command window that you opened with PowerShell.
01:56Now that your developer license is installed you're ready to go on to the next
02:00step, sideloading and testing the application.
Collapse this transcript
Side loading and testing the app on other computers
00:00Once you've setup a developer license on another Window 8 or Windows RT computer
00:05you should be able to sideload a testing package onto the computer and run the
00:09application there, here are the steps.
00:11First, I'll make sure that I've uninstalled the application from my
00:15development computer.
00:16I'll go to the Start screen, right- click on the title for the application and
00:21choose Uninstall and Confirm.
00:24I'll also make sure that I've closed Visual Studio, so that I'm only working
00:28with the testing package that I created earlier.
00:31Now I'll go back to my desktop and here's the testing package that I created
00:35in an earlier video.
00:36I'll extract the contents of the zip file to the desktop.
00:40I'll right-click, select Extract All, and click Extract.
00:45Then I'll drill down into the folder that contains my application package, there
00:50are four files and one folder here.
00:53Here's the only file that I'll need to work with directly, it's always
00:57called Add-AppDevPackage.
00:59It's a Windows PowerShell script and all you need to do is run the script in
01:04Windows PowerShell and your application will be sideloaded and will be ready to test.
01:09Right-click on the script file and select Run with PowerShell.
01:14PowerShell should open and I'm going to expand it to maximum, so we can see all
01:17of the text, and then I'll follow the prompts.
01:20You must have administrator credentials to install the signing certificate, and
01:25install the application.
01:26I'll press Enter to continue and I see a user account control dialog ask me if I
01:31want to continue with these changes.
01:33I'll click Yes, then I'm taken to another Windows PowerShell window and here I'm
01:39running as administrator.
01:41When I'm asked, if I'm sure I want to continue, I'll type Y for Yes and press
01:46Enter, after just a few moments your certificate will have been installed and
01:50your package will be installed.
01:52Press Enter to continue and both PowerShell windows will close.
01:56Now go to your Start screen and you should see a tile for the sideloaded
02:01application appears, click the Tile to run the application, and run the
02:05application through its paces on the new computer or device, where you have sideloaded it.
02:10In particular, I recommend going to the Settings charm. You should see your
02:14publisher name that you entered in the application manifest listed there.
02:18You should also see an item called Permissions, this Settings option always
02:22shows the current application name, the publisher name, and the version number,
02:27and indicates the application's Permissions.
02:30This application has Permission to use my Internet connection and no other
02:34special permissions.
02:35So if you've gotten this far you verified that you can run the application on
02:39other Windows 8 and Windows RT devices.
02:42There is one other critical testing step that you want to follow, before you
02:46actually submit the App to the Window Store and that's to run the application
02:50through the Windows App Certification Kit, and I'll show you how to do that in
02:54the following videos.
Collapse this transcript
Installing the latest Windows App Certification Kit
00:00In addition to functional testing of your application you also need to run your
00:04application through a software package called the Windows App Certification Kit.
00:09The Certification Kit is installed automatically with Visual Studio, but in many
00:14cases is out of date and needs to be upgraded before you can use it.
00:17To find out whether you need to update it, close all instances of Visual Studio.
00:22Then go to the Windows 8 Start screen.
00:25If you haven't rearranged your Start screen since you installed Visual Studio, there
00:29should be a tile for the Windows App Certification Kit there.
00:33You can start the kit by just clicking the tile.
00:35If you don't see the tile there, try typing App Cert Kit, and a tile
00:41should appear then.
00:42Either way, when you open the Certification Kit, if you see a user account control
00:47dialog, click Yes, You should then see this dialog appear.
00:51If you see the three commands to Validate a Windows Store App, Validate the
00:55Desktop App, or Validate the Desktop Device App, then you probably have the
01:00most recent version.
01:01But if you see another message indicating that you need to upgrade then you
01:04might see a link to get to the appropriate web page. Either way, I recommend that
01:10you install the latest version.
01:11So, I'll click Cancel to close the kit and then go to this web page
01:16at msdn.microsoft.com/enus/windows/ apps/jj572486, click Download now to
01:28download the latest version of the Windows SDK and when prompted at the
01:32bottom of the screen, click Run.
01:34This will download an installation application. Accept the default location and click Next.
01:41Then, after you accept the license agreement, you'll come to this screen, asking
01:45you which features you want to install, for this purpose you only need to
01:49install the latest version of the Windows App Certification Kit.
01:52So, uncheck all of the other options and you'll see that the Windows App
01:57Certification Kit is actually pretty small.
01:59If your App Certification Kit is already up to date, like mine is, then your
02:03estimated disk space required will be zero bytes, but if you need to install it,
02:08you'll see a larger number.
02:09Click the Install button and follow the rest of the prompts to install the
02:13latest version of the App Certification Kit.
02:16When the installation is complete you might need to reboot your computer, but
02:20then, after you've rebooted and reopened Visual Studio, you'll be ready for the next
02:24steps: running your application through the App Certification Kit to make sure
02:28it's ready for submission to the Windows Store.
Collapse this transcript
Testing with the Windows App Certification Kit
00:00After you've made sure that you have the latest version of the App
00:03Certification Kit installed, you can run your current application through the
00:07kit by going back to Visual Studio.
00:10I've reopened my project in Visual Studio, and then I'll go to the Menu, and once
00:15again select Store > Create App Packages.
00:19In order to easily run the App Certification Kit from Visual Studio you'll
00:23simply go through the process of creating an app package again.
00:26Now if you discovered anything in your sideload testing you might have made
00:30some coding changes, and that's great.
00:32But now you'll create another testing package --once again it's not designed to
00:36upload to the Windows Store-- and that's the version of the application that you
00:40will test with the Certification Kit.
00:42I'll leave this first option set to No, and click Next, and then once again as I
00:46did before, set my solution configuration to Release, then I'll update my version
00:53number. This time I'll use 1.0.0.1, and I'll click Create, and that creates a new
01:00version of my application package.
01:02Now to run the application through the Certification Kit, click the button at
01:07the bottom of the screen, that has the Administrator icon.
01:10If you see a user account control dialog, click Yes.
01:13After a few moments the App Certification Kit will load your application and
01:18start the test. The test takes quite a few minutes and during this process
01:22you'll see the application launch and shut down a number of times.
01:26I recommend leaving the keyboard and mouse alone during this process. Don't open
01:31any other applications, and definitely don't interact with your application.
01:35Let the Windows App Certification kit do its job. It's testing things like how
01:40long your application takes to start and suspend, whether your application has
01:44any memory leaks, or it has hanging asynchronous requests, and many other issues
01:50that are common to Windows Store Apps.
01:52When the App Certification Kit is done validating your application, you'll come
01:56to the Validation results screen and hopefully you'll see what I show here that
02:00my overall score is passed.
02:02Depending on your environment you might be prompted to select the name of
02:07your report file. But either way you should be able to click this link to
02:10view the full report.
02:12If you have any issues in your application your next step is to follow up and
02:17find out what the nature of the issue is and fix it.
02:20One very common issue is something called a suspend failure, and these failures
02:25are commonly caused with problems with asynchronous data requests.
02:29For example in my application I had a failure that was caused by my not wrapping
02:34an asynchronous request inside a try-catch block.
02:37Regardless, if you have a failure, make sure you've debugged and fixed the
02:42application and that the application gets through the App Certification Kit successfully.
02:47If that hasn't happened and you submit your application it will almost certainly
02:51fail the certification process.
02:53But if your application did pass, you're finally ready to submit the app to the Windows Store.
02:58I'll show you how to do that in the next chapter, but for convenience you will
03:02find a link on the App Certification Kit dialogue that will take you directly to
03:06the Windows Developer Center.
Collapse this transcript
2. Submitting an App
Opening a developer account
00:00In order to submit an app to the Windows Store, you must have a Windows
00:04Store Developer account.
00:05You can get a developer account by going to the website dev.windows.com. On this
00:11page, click the dashboard link.
00:13If you're not yet logged in with a Microsoft account, you can login now. Type in
00:18your email address and password.
00:20After you sign in, this first screen asks what country you live in, or where your
00:25businesses is located.
00:26I have selected the United States. Then you're asked to choose an account type.
00:30Individual accounts are for individuals, and company accounts are for
00:34companies or organizations.
00:36I've selected an individual account.
00:38On the next screen you're asked for your contact information, including your
00:41address, phone number, and if you like the website URL of your organization.
00:47Your publisher display name must be unique among all Windows Store App
00:51Developers. Type in the name that you want to use, then click the
00:54Check availability link.
00:56And if you see the message Available, that means you can proceed, I'll click Next again.
01:01And on this screen I'm asked to review and agree to the Developer Agreement,
01:05scroll through and read the agreement, and if you accept its terms, click the
01:09appropriate checkbox, and click Next again.
01:11And now you're ready to pay for your registration. As of the time of recording
01:15this course the cost of the Windows Store Developer Registration was $49 a year,
01:20this gives you all the services that you see listed here, including two
01:24technical support incidents per year.
01:26I'll click Next again, and on this screen, I'm asked to provide Payment, and that's it.
01:32Once your payment has been processed, you'll have a developer account that's
01:35good for one year, and you'll be ready to go on to the next step creating a record
01:39for your application for the Windows Store.
Collapse this transcript
Reserving an app name and entering basic app information
00:00Once you've created your developer account you can submit as many
00:03applications as you like.
00:05To submit a new application go to dev. windows.com again and make sure that you've
00:10logged in with your account, then click the Dashboard link again.
00:13Since you're now logged in with a valid developer account, you should see this
00:17screen: the app Dashboard.
00:19The first step is to create a new application record and reserve a name for it.
00:24Click the Submit an app link, this will let you reserve a name for the app and
00:28add its description, and after a few more steps, submit it for certification.
00:33First reserve the app name, click the link, and type in the name that you want to use.
00:38I'll type Roux Academy Art Conference, and I'll click Reserve app name.
00:44If you see this message that means that the name of your application has been
00:48reserved. If you see an error message indicating that the app name can't be
00:52reserved at this time, try logging out, closing your browser, reopening the
00:57browser, and logging back in again, that typically clears that common error.
01:02If you see this message though and you want to save your changes, click the Save button.
01:06Next you're asked for the selling details; how your app will be sold and how
01:11you want it listed.
01:12I'll click the Selling Details link, and first I need to select a Price tier.
01:16I'm going to make my app free, but notice that you can choose any of the
01:20listed Price tiers;
01:22you can't set your own Price tier that's not listed here.
01:26If you select a paid Price tier you're also asked whether you want to provide a free trial.
01:30I'm going to make mine free and so no free trial will be available.
01:34Next you're asked what market you want to offer your app in. You can select
01:39specific markets, or click Select all as I'm doing here.
01:42And now your app will be available anywhere the Windows Store is available.
01:46Scroll down toward the bottom, and there are a few more selections to make.
01:50You can choose to release your app as soon as it passes certification, or you
01:55can set a minimum month, day, and year.
01:57I'll select the default to release my app as soon as it's available.
02:00And next I need to select an app category. There are many categories
02:05available and as with pricing tiers you have to select one of those listed,
02:08you can't create your own.
02:10Some of the categories have subcategories. For example Games lists subcategories
02:16of Action, Adventure, Arcade, and so on.
02:19Other categories don't have subcategories.
02:22I'm going to put my app in the category, Lifestyle, and I won't see any available
02:27subcategories, so that's all I have to do there.
02:29Next I need to indicate whether there's a limit on what hardware will support
02:34my app. By default an app is listed as being available to all Windows 8 and
02:38Windows RT devices.
02:40But you can limit applications to only work on systems with DirectX and you can
02:44limit applications to systems with at least 2GB of RAM.
02:48I've tested my application on a surface RT and I'm satisfied it works on that and
02:53on lower powered Windows 8 computers as well, so I'll accept the defaults.
02:57And finally, if your application has been tested to meet accessibility
03:01guidelines, you can check this option, mine has not.
03:04So, I'll leave it unchecked and click Save.
03:07Next go into the Advanced features screen. Here you can add information about
03:11push notifications, and additional features, and products. My app doesn't have
03:16any of these so I'll click Save, and I'll be ready to go to the next screen about
03:20Age rating and rating certificates.
03:22Every Windows Store App must be rated, and it's up to you to do the rating.
03:27Read through the information on the ratings. Microsoft's guidelines say that if
03:31you're not sure what the ratings should be, choose at least 12+. Applications that
03:36aren't correctly rated can be rejected during the certification process.
03:40If you set a higher rating than would really be required it won't be rejected
03:44for that reason. But if you set a lower rating and the content of your app
03:47doesn't make sense, then it might be rejected.
03:50I'll choose that default recommended value of 12+ and I'll scroll down a little
03:55bit further and show that sometimes you need rating certificates depending on
03:59which regions you're submitting to.
04:01I'm going to skip past that information and click Save, and here's the last
04:06required screen, Cryptography. You must indicate here whether your app calls,
04:11supports, contains, or uses, cryptography, or encryption.
04:15If it doesn't, click No. If it does use these features there might be some
04:19restrictions on its distribution. Check the documentation for more information.
04:24Check the checkbox if you're sure that the app is widely distributable in all
04:28jurisdictions. Again, check the rules. Make sure your app is ready to
04:33distribute in this fashion. Scroll down. Click Save, and those are all the
04:38initially required values.
04:40We still have a few things to do including uploading the App Package, setting a
04:45Description to tell the customers what the app does, and providing notes to
04:49testers for anything about this release.
04:51But if you've finished these steps, you're ready to go on to the next step, creating
04:55a privacy statement, which is required for many applications.
Collapse this transcript
Publishing a privacy statement
00:00One of the most common reasons that Windows 8 Store Apps fail certification is
00:05because they lack a privacy statement.
00:08A Privacy Statement also known as a Privacy Policy is required for any app that
00:13communicates over the Internet.
00:15The requirement is described in Section 4 on this page, Windows 8 app
00:19certification requirements.
00:21I'll scroll down to that section, and show you that section 4.1.1 says your app
00:26must have a privacy statement if it is network capable.
00:30The Privacy Statement must be displayed in the app itself and in the description
00:35page of the app's record in the Windows Store.
00:38In order to display the Privacy Statement in the app, you can either use a
00:42flyout Window --and you can learn how to code that in any of the supported
00:46languages-- or you can place your policy statement on a web page on a publicly
00:51accessible website, and link to that page from the Settings charm in the app.
00:55I'm going to use the second strategy.
00:57I've created a fake privacy policy, and here it is, at
01:01datafeeds.rouxacademy.com /win8store/privacy.html.
01:08Now this isn't a real privacy policy, and in fact, Microsoft explicitly says
01:13that they don't provide any templates or samples of valid policies.
01:17It's up to you to write your own Privacy Statement, but I will show you how to
01:22link to this page from within the Settings charm of my app.
01:25I'll select and copy this URL to the clipboard, and then I'll switch over to
01:30Visual Studio, where I've opened my project.
01:33I'll go to the mainpage.xaml file and to its code behind file, mainpage.xaml.cs.
01:40Then I'll go down to the OnNavigatedTo method, this method is called
01:44automatically as this page is loaded, and as it's loaded, a request is sent
01:49from the Windows 8 operating system to the application, asking whether there
01:54are any settings commands.
01:55I'm going to use a class called the SettingsPane to register a new settings
01:59command and then when the user clicks on that command, they will be taken to my web page.
02:05I'll place the cursor after the existing code, and I'll press alt + shift + enter
02:09to go into full-screen mode. I'll close the output panel down at the bottom,
02:13and I'm ready to code.
02:15I'll start by using a class called, SettingsPane.
02:18This SettingsPane class represents the SettingsPane in Windows 8. This class
02:23isn't automatically available in my application, so I get the little squiggly
02:27line, and there isn't any auto complete yet, but I'll press ctrl + period (.)
02:32and I'll select the first option using Windows.UI.ApplicationSettings, and that
02:38adds required using statement at the top of my code.
02:42Now, I'm going to call a method called GetForCurrentView, and this returns the
02:46instance of the SettingsPane for the CurrentView, that is the CurrentPage, and
02:51then from there I'll add an event handler.
02:53For the event CommandsRequested. This event is telling my application the
02:58SettingsPane is asking do you have any settings you want to add to the pane.
03:04I'll use the increment operator and I'll reference a new method that hasn't been
03:09created yet, called onCommandsRequested.
03:13Now to create the method, I'll press ctrl + period (.)
03:17and I'll select the Only option Generate method stub for 'onCommandsRequested'.
03:22Now as the application starts up, this method will be called.
03:26I'll get rid of the throw command, because I'm going to implement this right
03:30away. When this method is called, I receive a collection of arguments called
03:34SettingsPaneCommandsRequestedEventArgs, and I'm going to use those arguments
03:39to register a new command.
03:41I'll create an instance of a class called UICommandInvokedHandler.
03:48Once again this is a class that isn't automatically available.
03:51So, I'll type in the name of the class and press ctrl + period (.)
03:54and add the using statement.
03:56I'll name this new object handler and I'll create it by calling the constructor
04:00method for the class new UICommandInvokedHandler.
04:06And I'll pass in the name of another method that I'm about to create, which I'll
04:10call onSettingsCommand.
04:12Now this method hasn't been created yet either, but I'm going to leave this
04:16error there for the moment and come back to it after I add a couple more lines of code.
04:21Next, I'll create an instance of a class called SettingsCommand.
04:25I'll name this object command and I'll instantiate it with the constructor
04:28method for this class SettingsCommand and I'll pass in three arguments.
04:33The first argument is the CommandID, this can be any value and I'm going to use
04:38a string of simply privacy.
04:41Next I'll pass in a label and this is what the user sees. I'll type in a
04:46string of Privacy Policy and then I'll pass in the UICommandInvokedHandler object,
04:53which I named handler.
04:54So, I've created the command and now I'm going to add it to the SettingsPane,
04:58using this syntax, args --that's the argument that was passed into the current
05:04method-- args.Request.ApplicationCommands.Add and I'll pass in my command object.
05:12Now there is enough information for Visual Studio to know what onSettingsCommand
05:17is going to be, it'll be a method that's called when my SettingsCommand is
05:21triggered by the user.
05:23So, I'll come back here and I'll place the cursor after the name of the new
05:27method, I'll press ctrl + period (.)
05:28and I'll generate the method stub for the new method.
05:31Now I'm ready to add code that will be executed when any of my Custom
05:35SettingsCommands are called by the user.
05:38If I had more than one CustomSettingsCommand, I would have to look at the
05:42command object that's being passed into this method and ask which command was
05:46called, but because I only have one, I know it's the privacy statement.
05:50So, I'm going to create a string variable that I'll call privacyUrl, and I'll
05:57give it a value of the URL that I looked at in the browser previously, remember,
06:01I had copied it to the clipboard, so now I can just paste it in.
06:05Next, I'm going to launch that URL. I'm going to wrap it inside a URI object and
06:11then call a method of the Launcher class, called Launch URI async.
06:16Before I call that method, I'm going to mark this method as asynchronous. I'll
06:21add the async keyword before the keyword void.
06:24Then I'll go back to after the string and I'll put in the keyword await, then
06:28I'll type in the name of the class, Launcher.
06:31I'll press ctrl + period (.)
06:33and select using Windows.System. Then I'll type in the period (.)
06:38and I'll call the method LaunchUriAsync.
06:41I'll create a new URI object, and I'll wrap the privacyUrl string around it.
06:47So, when the user clicks on my new SettingsCommand, which will be labeled
06:51Privacy Policy that will result in calling this method, I'll call
06:55LaunchUriAsync, and I'll launch this URL pointing to my Privacy Policy, in the
07:00system's default browser.
07:02So, now I'm ready to test.
07:04I'll save and press ctrl + F5 to run the application.
07:07With the application open, I'll move the cursor to the top right corner and then
07:12go to the SettingsPane, and there's my new Privacy Policy.
07:17I'll click the link, and that launches the URL in the default browser, which on
07:22my system is the Start screen's version of Internet Explorer.
07:26So, those are all the steps you need to implement the Privacy Policy in your application.
07:31The Privacy Policy must be a part of your application, and it must be exposed
07:36through the Settings charm.
07:37Whether you display the Privacy Policy directly in your application, or you link
07:42to a public web page as I've done is up to you, but this is a strict requirement
07:46for Windows Store App Certification.
Collapse this transcript
Creating and uploading the app package
00:00Once you've created an application record in your developer account the next
00:04step is to associate your application with that record, and you can do that
00:08through Visual Studio.
00:09I'm back in Visual Studio and I've reopened my application project, and I'll go
00:13to the Menu and select Store > Create App Packages again.
00:18I previously used this wizard to create a testing package, but now I'll create a
00:22package to upload to the Windows Store.
00:24So, I'll select Yes, when asked whether I want to build the package to upload to
00:29the Windows Store, and then I'll click the Sign In button at the bottom.
00:33Now I'll sign in with my Microsoft account information. That takes me to a
00:38listing of the applications that I've registered.
00:41I'll click on the application record, and click Next.
00:44As I've done previously, I'll set the solution configuration to Release and only
00:49select an Architecture of Neutral. Then I'll click Create, and that creates a new
00:54set of files on the desktop.
00:56I'll click the link to go to the output location, and then I'll navigate to the
01:01dev.windows.com homepage.
01:03I'll click the dashboard link, I'll sign in again.
01:08And then when I get to the Dashboard screen, I'll click the Edit link to
01:12continue working with my application.
01:14Now I'm going to drag Internet Explorer over to the left and dock it on the
01:18left, and then I'll go to the File Explorer and dock it on the right.
01:23You might remember that previously when I created a testing package, I said that
01:27the file with the extension of .appx.upload wasn't needed for testing;
01:32it is needed to upload your Packages to the Windows Store.
01:36In the browser on the left, I'll scroll down and I'll click the Packages link.
01:41Then I'll click and drag the appx.upload file and drop it into the rectangle;
01:48that causes the entire package to be uploaded to the Windows Store.
01:52I'm done with the File Explorer so I'll close it, and then I'll expand the
01:55browser to full screen again.
01:57Check the Confirmation. It should say We uploaded the package. Click Save, and
02:02now you're ready for the next step, adding your application's description, and
02:06I'll take you through those steps in the next video.
Collapse this transcript
Creating app screenshots
00:00Once you've uploaded the application packages to the Dashboard, the next step is
00:05to provide a Description.
00:06I'm in the Dashboard, in the Application, and I'll scroll down to the
00:10Description section.
00:11I'll click into it, and show you that one of the required elements of the
00:15description is screenshots.
00:17The requirements are shown here. The screenshot images must be PNG files that are
00:22at least 1366 x 768 in landscape mode or 768 x 1366 in portrait mode, and not larger than 2 MB.
00:33It's very easy to create these screenshots in Visual Studio using the Windows 8 Simulator.
00:39So, I'll go back to Visual Studio where I still have my application loaded up.
00:43I will make sure I have my testing environment set to the simulator, and I'll
00:46select DEBUG > Start Without Debugging, and that launches the Windows 8 Simulator,
00:52and loads the application.
00:54Next, I'll arrange the application so that it looks the way I want my
00:58screenshot to show up.
00:59I'll select one of the artists. I'll make sure I haven't truncated vertically
01:03any of these rows, and now I'm ready to take the screenshot.
01:07The screenshots are saved by default as files, and they're placed in a
01:12folder called Windows Simulator, under My Pictures. That's where I'll place my screenshots.
01:17So, with the application set up the way I want it to look, I'll click on the Copy
01:21Screenshot icon. There's no feedback, but that does create the screenshot file.
01:27I'll go back to the Settings icon, and click View Saved Screenshots;
01:32that takes me to the Windows Simulator folder in the File Explorer.
01:36I can double-click the file and see what it looks like.
01:41I'll also create a portrait screenshot, I'll go back to the Windows 8 Simulator,
01:46I'll rotate the application, and I'll take another screenshot by clicking the
01:50Copy Screenshot icon.
01:52I'll go back to the File Explorer and show that both screenshots are there.
01:56So, now I'll be ready for the next step, filling in my description and uploading
02:01my screenshot images.
02:02And I'll go through those steps in the next video.
Collapse this transcript
Creating the app description
00:00After uploading the app packages for your Windows Store app, the next step is to
00:05provide the description.
00:07The Description is a combination of text and images.
00:11There are some open text fields such as the description itself, and some
00:16image upload tools.
00:18You'll need at least one screenshot of your application, and
00:22optionally, promotional images.
00:24There are four possible promotional images, and their sizes are listed here on the screen.
00:29If you only want to submit one image, submit the smallest one, with
00:33resolution of 414 x 180.
00:36For this demonstration I have an image in the Exercise Files that I'll use.
00:41The rules for the promotional images go like this, if you submit at least one
00:45promotional image --and again, preferably the smallest one-- then your app will be
00:50eligible to be featured in the Windows Store.
00:53There's no guarantee that it will be featured, but if you don't supply
00:56promotional images, it's a guarantee that it won't be featured.
01:01So, let's go to the top of the screen, and I'll fill in the values one at a
01:05time, the main description can be pretty large, you can type in up to 10,000 characters.
01:10I'll keep it short though;
01:12I'll use a simple description of a list of the Roux Academy Art
01:16Conference's featured artists.
01:21Next, you can add App features. You can add up to 20, and they can each be up to
01:26200 characters long.
01:28I'll type in two features, a list of featured artists from this year's Art
01:32Conference, and gets data from an RSS feed on the Roux Academy website.
01:38Next, you can type in keywords. These are keywords for Search.
01:43So, I'll type in Roux Academy, the name of the Organization, and Art Conference.
01:49If I wanted to go further, I might type in names of artists that I want to be
01:54searchable, but I'll leave it at just these two keyword values.
01:58The next field is the Description of update. If you're updating the application,
02:03you should fill in this value, but if it's a brand-new application, leave this field blank.
02:10The next field is the Copyright and trademark info.
02:14I'll type in Copyright and then instead of the copyright symbol, I'll put in a
02:18(c) in parentheses, which is good enough, and then the name of the organization,
02:23Roux Academy. You should put in copyright information according to your
02:27organization's requirements.
02:29If you have additional license terms you can enter them here, but if you don't,
02:34you can leave it blank.
02:35Now I'm ready for my screenshots.
02:37As I showed in a previous video, I created screenshots of my application using
02:42the Windows 8 Simulator.
02:44I'll add my two Screenshots. I'll click the first link. I'll go to My
02:49Pictures folder in my libraries; to the Windows simulator, and I'll select my
02:55landscape screenshot.
02:56I'll click Open, wait a moment, and the screenshot is uploaded and displayed.
03:02For each screenshot, you can enter a description of up to 200 characters.
03:08The app in landscape orientation. Then I'll add the second image and I'll
03:14select the Portrait version, and once it's been uploaded, I'll type in the
03:18description for that.
03:23For each image you can click on the little magnifying glass icon, and you'll
03:27see what the image looks like in full screen, and then press Escape (Esc) to
03:32clear it from the screen.
03:33I'll preview the portrait image, and again press Escape (Esc).
03:37Now I'm ready for my promo image, as I mentioned, these are optional, but highly
03:42recommended, and I'll add one.
03:44I'll click Add Image, then I'll go to my Exercise Files, to the Assets folder, to
03:51Icons, and I'll choose this file;
03:53RouxAcademyPromographic, and click Open.
03:57Once it's been uploaded it's displayed as a small version and I can click the
04:01magnifying glass icon to see it in full size.
04:05Next, enter your recommended hardware.
04:08I'll type in Internet-connected computer with Windows 8 or Windows RT.
04:14Next is your website, this is optional, but recommended.
04:18I'll typ in http://www.rouxacademy.com.
04:25Next, provide a support contact, this can either be an email address or a
04:31URL that takes the user to a data entry form, into which they can type support requests.
04:37I'll type in a fake email address of support@rouxacademy.com.
04:43Next and finally, is the Privacy policy.
04:46I described this in a previous video.
04:49If your app connects to the Internet as it's running, you must provide
04:53this information, and the easiest way is to provide the URL that displays
04:58your privacy statement.
05:00I'll go to the page that displays the statement, copy its URL to the clipboard,
05:05come back to the data entry form, and paste it in, and I'll save my changes.
05:10After I come back to the main app page, I'll scroll down and make sure that I
05:15get a Complete icon, and this tells me that the description has been filled in.
05:20Finally, click the Notes to testers link.
05:23If you have any instructions for testers, provide them here. You don't have
05:28to provide any information here, but if there is anything special about your
05:32application, such as the need to log into a service, you should provide the info.
05:37I've clicked into the screen, and I'll click Save. Then I'll scroll down to the
05:42bottom and make sure that all of these items have a complete icon.
05:46At this point you can review your release information or Submit for certification.
05:52When you click Review release info, you'll go to a screen that shows you
05:56everything that you've entered.
05:58You can print or otherwise save this, you can edit the release, or you can
06:02complete the process by submitting your application for certification.
06:06And that's it, your app has been submitted, it will be reviewed by Microsoft,
06:11and if it's accepted, it'll go live in the Windows Store based on the
06:15schedule that you requested, either immediately, or no earlier than the date
06:20that you entered.
Collapse this transcript
Conclusion
Reviewing common reasons for certification failures
00:00Many Windows Store Apps fail certification the first time they are submitted,
00:04and there's a short list of common reasons for these failures.
00:08I've mentioned some of them during this course.
00:11For example, if your app connects to the Internet, it must have a privacy
00:14statement. That privacy statement must be exposed through the Settings charm,
00:19and must also be available in the Description page in the Windows Store.
00:23There are other common reasons for certification failure, and they're listed on
00:27this page, the name of the page is JJ657968.aspx and it's labeled, Avoiding
00:34common certification failures.
00:36I recommend reading through this web page before you submit your application
00:40for the first time.
00:41And if you get back a certification failure upon your first submission, try
00:46looking at this page, Resolving Certification Errors. You'll find a list of
00:51common reasons for certification failures, and recommended approaches to
00:55resolving them, including issues around security, technical, and content
00:59compliance, and other common issues.
01:02If your app fails certification, read the reasons that are sent back to you
01:06thoroughly, figure out how to resolve them, using a combination of Microsoft's
01:10documentation and the posts that are available on many developer's blogs about
01:16Windows 8 development. Then after you've resolved your issues, resubmit the
01:20application. Stick with it.
01:22Eventually, once you've resolved all those issues and your app is certified and
01:26accepted into the Windows Store, it'll be made available to all the users of
01:30Windows 8 and Windows RT.
Collapse this transcript
Next steps
00:00Thanks for watching, this course, Distributing Windows Store Apps.
00:04You can learn more about building Windows Store Apps with the lynda.com course:
00:08Building Windows Store Apps Essential Training, and you can learn how to build
00:12the app I use in this course's demonstrations.
00:15If you like to program in C#, watch Building Your First Windows Store App with XAML and C#.
00:20Or for Visual Basic, watch Building Your First Windows Store App with XAML and Visual Basic.
00:26Regardless of which languages you use to create Windows Store Apps, I hope
00:30this course will help you get started, distributing your apps through the
00:33Windows Store.
Collapse this transcript


Are you sure you want to delete this bookmark?

cancel

Bookmark this Tutorial

Name

Description

{0} characters left

Tags

Separate tags with a space. Use quotes around multi-word tags. Suggested Tags:
loading
cancel

bookmark this course

{0} characters left Separate tags with a space. Use quotes around multi-word tags. Suggested Tags:
loading

Error:

go to playlists »

Create new playlist

name:
description:
save cancel

You must be a lynda.com member to watch this video.

Every course in the lynda.com library contains free videos that let you assess the quality of our tutorials before you subscribe—just click on the blue links to watch them. Become a member to access all 104,069 instructional videos.

get started learn more

If you are already an active lynda.com member, please log in to access the lynda.com library.

Get access to all lynda.com videos

You are currently signed into your admin account, which doesn't let you view lynda.com videos. For full access to the lynda.com library, log in through iplogin.lynda.com, or sign in through your organization's portal. You may also request a user account by calling 1 1 (888) 335-9632 or emailing us at cs@lynda.com.

Get access to all lynda.com videos

You are currently signed into your admin account, which doesn't let you view lynda.com videos. For full access to the lynda.com library, log in through iplogin.lynda.com, or sign in through your organization's portal. You may also request a user account by calling 1 1 (888) 335-9632 or emailing us at cs@lynda.com.

Access to lynda.com videos

Your organization has a limited access membership to the lynda.com library that allows access to only a specific, limited selection of courses.

You don't have access to this video.

You're logged in as an account administrator, but your membership is not active.

Contact a Training Solutions Advisor at 1 (888) 335-9632.

How to access this video.

If this course is one of your five classes, then your class currently isn't in session.

If you want to watch this video and it is not part of your class, upgrade your membership for unlimited access to the full library of 2,024 courses anytime, anywhere.

learn more upgrade

You can always watch the free content included in every course.

Questions? Call Customer Service at 1 1 (888) 335-9632 or email cs@lynda.com.

You don't have access to this video.

You're logged in as an account administrator, but your membership is no longer active. You can still access reports and account information.

To reactivate your account, contact a Training Solutions Advisor at 1 1 (888) 335-9632.

Need help accessing this video?

You can't access this video from your master administrator account.

Call Customer Service at 1 1 (888) 335-9632 or email cs@lynda.com for help accessing this video.

preview image of new course page

Try our new course pages

Explore our redesigned course pages, and tell us about your experience.

If you want to switch back to the old view, change your site preferences from the my account menu.

Try the new pages No, thanks

site feedback

Thanks for signing up.

We’ll send you a confirmation email shortly.


By signing up, you’ll receive about four emails per month, including

We’ll only use your email address to send you these mailings.

Here’s our privacy policy with more details about how we handle your information.

Keep up with news, tips, and latest courses with emails from lynda.com.

By signing up, you’ll receive about four emails per month, including

We’ll only use your email address to send you these mailings.

Here’s our privacy policy with more details about how we handle your information.

   
submit Lightbox submit clicked