Ok today has not started off so good. My goal was to create a simple startup application which was my shell of our WP7 application but this has been WAY more painful than I would have ever thought it could be.
The issue is that when I started the app the very first time (when the project was virgin and no changes had been made) it all worked. However I then proceeded to change the Assembly name and Default namespace of the project along with changing the App.xaml.cs and MainPage.xaml.cs namespaces. When I did this NOTHING WORKED. I would try to launch the app in the emulator and it would simply start and then shut down. I was NOT able to hit any break points and there was nothing in the output console.
After a few minutes of screaming at the monitor (cause we all know that helps) I finally had a thought… ‘what if my startup page/object was not set anymore because of the namespace changes’? So I opened the project properties screen and this is what I saw.
Once I saw that there was nothing in the startup object I quickly set it to a value and re-ran the app. Sure enough this time everything worked just fine.
The moral of this story is this. If you change the namespace of your startup class (ie App.xaml.cs) make sure you go into the project properties page and make sure you still have a startup object set. If you do NOT then you are going to experience the same issues I did.
Till next time,
10-13-2010 6:59 AM