Paul Hazen
Paul Hazen

Reputation: 2473

WP7 App Crashes Immediately upon deploy

Okay, so I'm developing an app for Windows Phone, and I can't seem to figure out what this issue is.

To start with, I should say my application compiles with no warnings, no errors, nada. Looks like a charm.

However, when I build the application to either the emulator, or any one of the two different WP7 devices I have on hand, the splash screen shows for a split second, and I'm returned to the home screen of the device.

Looking at the output:

'taskhost.exe' (Managed): Loaded 'mscorlib.dll'
'taskhost.exe' (Managed): Loaded 'System.Windows.RuntimeHost.dll'
'taskhost.exe' (Managed): Loaded 'System.dll'
'taskhost.exe' (Managed): Loaded 'System.Windows.dll'
'taskhost.exe' (Managed): Loaded 'System.Core.dll'
'taskhost.exe' (Managed): Loaded 'System.Xml.dll'
'taskhost.exe' (Managed): Loaded '\Applications\Install\6D7C6AA5-7D7C-4056-8BF7-1097F7FBAC40\Install\Subsplash.ExampleLibrary.dll', Symbols loaded.
'taskhost.exe' (Managed): Loaded '\Applications\Install\6D7C6AA5-7D7C-4056-8BF7-1097F7FBAC40\Install\ClientCore.dll', Symbols loaded.
'taskhost.exe' (Managed): Loaded 'System.Xml.Linq.dll'
'taskhost.exe' (Managed): Loaded 'Microsoft.Phone.dll'
'taskhost.exe' (Managed): Loaded 'Microsoft.Phone.Interop.dll'
The thread '<No Name>' (0xda1003e) has exited with code 0 (0x0).
The thread '<No Name>' (0xd660032) has exited with code 0 (0x0).
The program '[206110770] taskhost.exe: Managed' has exited with code 0 (0x0).

I'm guessing that it may be an issue with the dev environment. One more detail is that a few versions ago this was working 100%, then I changed some namespaces and folder names, and since then this issue has prevented us from doing any kind of dev. However, I'm confused as to why there would be a problem related to namespace name changing and folder change, but no build errors.

Thoughts?

Upvotes: 22

Views: 3906

Answers (2)

Nigel Sampson
Nigel Sampson

Reputation: 10609

If you've done any namespace renaming (especially of the App object) double check the startup object in the project is set correctly.

Upvotes: 64

Matt Lacey
Matt Lacey

Reputation: 65564

Try running Clean on the project.

Check the Startup object is set correctly in the project properties.

Check the DefaultTask in "WMAppManifest.xml" is pointing to the right view.

Upvotes: 4

Related Questions