Summary
A lot of people ask me how they can write a Windows 8 App with Visual Studio and Team Foundation Service (our online, hosted version of Team Foundation Server). In fact, I was talking with a friend recently whom I used to code with about 10 years ago. It had been a long time since he programmed with C# (nearly 10 years?) as he now spends most of his time programming low level driver code. He challenged me with how fast a "new" developer could get started with writing a Windows 8 App. He set the challenge asking if a new developer could get started in under 1 day. Challenge accepted. Challenge accomplished. Here is my journey through documenting how a new developer can get started with Windows 8 application development using Visual Studio & Team Foundation Service.
Step 1 - Where to Start?
This MSDN website has wealth of information on how to get started.
Step 2 - Select your Tools (Visual Studio)
I already use Visual Studio Ultimate w/ MSDN because it lets me architect my applications better and debug my applications a lot faster using IntelliTrace: http://www.microsoft.com/visualstudio/eng#products/visual-studio-ultimate-2012
Step 3 - Select your Programming Language
One of the things I like most about application development on Windows 8 is the access to a variety of programming languages & frameworks. I prefer C# & XAML, which is described here: http://msdn.microsoft.com/en-US/windows/apps/bg125376
Step 4 - Manage your Project using Team Foundation Service
Team Foundation Service, available here, http://tfs.visualstudio.com/en-us/tfs-welcome.aspx is free and it's a great tool to manage your projects. I used TFS for this project to help me:
* Keep track of my user stories
* Create functional requirements
* Storyboard my user experience
* Source Code Control & repository
* Managing my project backlog (i.e. future ideas)
* Manage my test cases
* Solicit feedback from my friends via the UAT Feedback Tool
Step 5 - Create User Stories & Tasks
To help myself stay organized, I created user stories and tasks right within TFS.
Image may be NSFW.
Clik here to view.
Step 6 - Storyboarding in TFS & PowerPoint
As a visual person, it's always easier for me to see applications come alive before I code them. So I used the Storyboarding capabilities of TFS & PowerPoint.
Image may be NSFW.
Clik here to view.
Step 7 - Begin Coding with the Sample Apps
I found these sample applications to be incredibly helpful:
http://code.msdn.microsoft.com/windowsapps and http://code.msdn.microsoft.com/windowsapps/Windows-8-Modern-Style-App-Samples
Step 8 - Obtain your Developer License
Image may be NSFW.
Clik here to view.
Step 9 - Obtain Feedback with the TFS UAT Feedback Request Tool
Right from your TFS as a Service dashboard, you can solicit feedback from your UAT users.
Image may be NSFW.
Clik here to view.
Step 10 - Obtain your Free Windows Store Developer Account from your MSDN Subscription
If you are a Premium or Ultimate MSDN subscriber, you have access to a free Windows Store Developer Account as part of your included MSDN benefits.
Step 11 - Certify your App
Microsoft recommends that you always certify your application before submitting it. This will help you identify blockers to publication before you go through the longer process.
Image may be NSFW.
Clik here to view.
Step 12 - Publish your App
Most developers, myself included, find this to be the most involved step. I encountered a few surprises along the way that I wasn't prepared for. For example, I was declaring that I needed Internet (Client) capabilities in my packaging manifest file. As such, I was required to include a privacy statement in both the submission of my application as well as the Settings charm. But my application doesn't really need internet capabilities, so I just removed this requirement.
There is a great dashboard and step-by-step guide for publishing your applications, here: http://msdn.microsoft.com/library/windows/apps/hh694062.aspx
Conclusion
And there you have it! A 12 step guide for how to publish a Windows 8 App in under a day. Let me know how your experiences go!
Image may be NSFW.
Clik here to view.