So after submitting applications a few times for both myself and a few friends, i have learnt a few a few do’s and don’ts that can make the difference between it taking 2 weeks to get your application in the Windows Phone 7 marketplace, and only a day or two including registration. With the help of the tips below, hopefully i can help some of you avoid any of the frustrations that can come from starting development on a new platform.

Last year i started on a project that allows easy tracking of page views, events and transactions to your Google Analytics account without using JavaScript or a Browser simply using a .Net wrapper. This became GaDotNet. Over the Past 6 months i have had well over 2,000 downloads and many thank you emails so obviously people are finding a use for my code – this can only be a good thing. Now it is time for the project to grow up – so I've moved it to a remotely hosted source repository – CodePlex.

Over the past few weeks i have spent a fair bit of time creating Silverlight charts for a few Windows Phone apps I've been writing. The Silverlight charting toolkit’s documentation for advanced scenarios is pretty sparse to say the least. My experience in finding information on working with the DateTimeAxis that you can use on these charts was nothing short of frustrating. This post’s purpose is to hopefully serve to better educate others in my situation.

Over Christmas and New Year i had a little fun with the free time i had, i did what i do most years and started a spelunking exercise into something new and exciting, this time it was: Windows Phone development. After purchasing a Samsung Omnia 7 and getting a feel for the OS and UI design, i set out to create a simple app to try my luck at the lucrative (… we’ll see) world of Windows Phone 7  development. My first Release, BurnStats - a simple app that allows you to view your FeedBurner statistics natively on the device, has finally hit the app store – in true festive spirit, there was much rejoicing to be had.

In my early testing of Windows Phone 7 apps, it has become apparent that a lot of developers are simply not checking for network connectivity before attempting to access the internet – this gives a bad user experience as the user is left to wait until the connection times out. Checking to see if the device is connected to a network will improve this user experience dramatically.

Having a good Continuous Integration setup is the gift that keeps on giving, but what about your database? For most web applications these days, your database is a large part of your application – so why is versioning it such an uncommon thing? Because it’s time consuming and complicated – two requirements that Continuous Integration love conquering with a one-two punch.

Working with Stored Procedures and functions on a database tier can be time consuming, hard to debug and sometimes just difficult to get clarity on what is “happening”. A rarely discussed feature of Microsoft SQL Management Studio is its inbuilt debugging features. These allow you to see exactly what is going on, and step through your logic in a similar fashion to working in Visual Studio.

If on your first ever start of Visual Studio you pick a layout that happens to be missing the oober aweshuum “Build configuration” dropdown menu from your toolbar and are struggling to find it in the Build toolbar (i know i was..) here is how you add it back:

Ever wondered what your favourite iPhone, Android or Windows Phone application is actually doing with your data plan? Wonder if its sending your data to the mother ship without you knowing – Fiddler can be used to easily check this data traffic in the same way that it can be used for web application and web-service troubleshooting and development work.

I watched an interesting thing take place the other day, in the form of someone using the visual tooling in SQL Management Studio to “Edit Top 200 rows” in a table, then realising that the record they wanted was not there, running a manual SELECT query to find the record, and then running a manual UPDATE command to edit the row. This can all be done a lot quicker using the same visual tooling they used in the first action – it’s just sneakily hidden in SQL Management Studio.