Thanks for that. I hadn't notices the search ribbon before and I've been using it a while now. It's the drop down that hides it.

I like to go with the underdog as well. I don't regret buying the phone, it was a 520 and only cost me about £80. I've had it a good number of years and as you said it was still getting updates until recently. My house has some poor wifi areas in it, something to do with the walls, and my little phone kept its link a lot better than any other device we have both android and apple. So it was well worth having, I'm just sad to see it go.

I have just bought a Nokia phone. So my apologies to every one working for Nokia.

Very true. Me and the other 11 will probably get over it. I managed to get over buying a mini-disk player instead on an mp3. Turns out I'm not very good at picking a technology winner!

My little Windows phone is no more, well I've turned it into an mp3 player for my son, but in terms of a working phone it has gone. So much unfulfilled potential. I know I was in a very small minority but I really liked it and I really liked the UI. I particularly liked the confused looks I got from people when I told them I had a windows phone which often meant I didn't have access to a particular app. It let me make calls, listen to podcasts and access the internet and emails. I have simple needs. But everything has either stopped working or will soon and too many things just kept on crashing. Now I have to spend lots of time trying to stop Google doing things for me. I'm not interested in their news and I don't want to talk to them!!! Still it's progress I guess.

So nice to hear that I'm not the only one who likes Windows Phones. I'm on my second and I really like it. I've got an iPad and my wife has an Android phone nut I just prefer the UI of the WP. The poor app support is a pain sometimes and in the UK the BBC iPlayer radio app is very poor but I've found apps to do all the things I want to do. I fear Microsoft is going to leave me high and dry though.

Thanks bery much for the clarification. Sorry it's taken all weekend to reply. I use my work email for CP and only go your reply today. Stephen

Hi Marc Thanks for the reply. I guess my question is more about the process of bug fixing. This is how I think it goes. 1. A bug is reported. 2. Write a test to recreated the bug - this test will pass. 3. Write a test to test how the code whould work - this test will fail. 4. Fix the bug. 5. The first test will now fail as the bug is fixed and the second will pass. Do I keep the first test that recreated the bug? It would be good to keep it as part of the history of how the bug was fixed but I wouldn't want to keep on running a failing test. Rereading a bit of your book again (the Prove a Bug is Recreatable and Prove a Bug is Fixed sections) I might have misunderstood steps 2 and 3. It looks like you might be writing a test to recreate the bug (DivideByZeroException) in your example and then you change the test to test what should happen (ArgumentOutOfRangeException). So it's one test rather than two. Stephen

Hi Marc I read your post and decided to down load your book. I've given it a good read now and thought it was very informative. I've recently been increasing my use of unit testing and you gave me some good information and some new ideas to try. I particularly liked the comparison between NUnit and the Visual Studio testing framework. I have one question about bug fixing. I get the part about writing a negative test to recreate the bug and then a positive test to test what should happen. Once you've fixed the bug do you keep the negative test or do you delete it and just keep the positive one. Thanks Stephen Well that's my first post done then!!