Browse by Tags
All Tags »
C# (
RSS)
Tip #2: How not to break Windows Phone certification rule No. 5.2.4 – Use of Back Button. So this is a rather common one, mostly because developers don’t take the hardware keys into consideration when developing an application, or on the contrast use them incorrectly. Basically what it means is: Make sure the Back Button does what it’s supposed to do: Navigate Back. No matter what your application does, no matter how many transitions occur, the back navigation needs to be fluid, logical and...
Tip #2: Proper Exception Handling in .Net and in General. ” Always code as if the person who ends up maintaining your code is a violent psychopath who knows where you live. ” You can never know when this phrase will turn into horrible reality, so you’d better be prepared! Tip #2: Proper Exception Handling – Part 1 This time on “Code Tips That Will Save Your Life” – Exceptions . We all know them and sadly we all have to deal with them, but are you doing it right? To most it seems like a very straightforward...
Tip #1: How not to break Windows Phone certification rule No. 6.5 – Correctly working with the Media Player. Oh this is a fun one… The first certification rejection I ever got was because of this one. It's a very simple rule, but not knowing of it's existence or how to abide it in code can make things tricky when you try to fix it later. The idea is fairly basic, if the user has music playing while entering your application (via Zune or whatnot), you can't hijack the Media Player and...
Tip # 1 : Document & Comment Your Code. "Always code as if the person who ends up maintaining your code is a violent psychopath who knows where you live." You can n ever know when this phrase will turn into reality, so you'd better be prepared. This is the beginning of what I expect to be a long series of coding tips and best practices that will help you write better code and might even save your life one day! Tip # 1 : Document & Comment Your...
A.K.A: Critical But Stable Condition Probably the least user friendly experience one can have in a Windows Phone App, not including the "screen freeze" horror, is having the application crash back to start screen. No one tells you what happened, no one warned you that it is coming, and you are left with the horrifying feeling of assuming the worst. Now I know that you know, that when an application crashes it's just an unhandled exception, nothing big, no scary monsters there...