Silverlight – Windows Phone 7 – The application does not start, there is no error, just load the load

When preparing for the release of my mobile application, I thought I would change the version numbers of all assemblies.

I also encountered a problem, WCF service client does not automatically generate proxy code, I have raised a known bug, MS has fixed vNext, but I don’t think it is relevant. Anyway, I ruled it out and believe it is related to what I’m doing The preparation is related.

My application will not load in the emulator or device now. It just bombs during the CLR boot without any errors to help me. I am very sad, I will use MS in ten years Opened my first support call.

The following is the content of the output window:

'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\A2C90EB3-BF72-4317-B6FB-7D05843D6E15\Install\Company.Product.Mobile.WindowsPhoneUK.dll' , Symbols loaded.
'taskhost.exe' (Managed): Loaded'\Applications\Install\A2C90EB3-BF72-4317-B6FB-7D05843D6E15\Install\Company.Product.Mobile.dll', Symbols loaded.
'taskhost.exe' (Managed): Loaded'Microsoft.Phone.d ll'
'taskhost.exe' (Managed): Loaded'Microsoft.Phone.Interop.dll'
The thread'' (0xc7e00a2) has exited with code 0 (0x0).< br />The thread'' (0xcdd0076) has exited with code 0 (0x0).
The program'[232259726] taskhost.exe: Managed' has exited with code 0 (0x0).

See? There is no error! There is nothing to continue. It's not that I can set the Fusion log on blummin's phone.

The log should show more assembly loading. I have reversed my changes and the version number is no longer a car, I can't think of it I will do it, it will cause this!

Source code control is absolutely necessary.

Thank you Luke

I ran into the same weird error last week.

After creating a new solution (build and run without problems), I found that changing the namespace would cause the error.

Hope it helps.

When preparing for the release of my mobile app, I thought I would change the version numbers of all assemblies. < p>

I also encountered a problem, WCF service client did not automatically generate proxy code, I have raised a known bug, MS has fixed vNext, but I don't think it is related. Anyway, I ruled this out and believe it is related to the preparation I am doing.

My app will not load in the emulator or device now. It just does not bomb during CLR boot Any mistakes to help me. I am very sad, I opened my first support call with MS in ten years.

The following is the content of the output window:

'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\A2C90EB3-BF72-4317- B6FB-7D05843D6E15\Install\Company.Product.Mobile.WindowsPhoneUK.dll', Symbols loaded.
'taskhost.exe' (Managed): Loade d'\Applications\Install\A2C90EB3-BF72-4317-B6FB-7D05843D6E15\Install\Company.Product.Mobile.dll', Symbols loaded.
'taskhost.exe' (Managed): Loaded'Microsoft.Phone. dll'
'taskhost.exe' (Managed): Loaded'Microsoft.Phone.Interop.dll'
The thread'' (0xc7e00a2) has exited with code 0 (0x0).< br />The thread'' (0xcdd0076) has exited with code 0 (0x0).
The program'[232259726] taskhost.exe: Managed' has exited with code 0 (0x0).

See? There is no error! There is nothing to continue. It's not that I can set the Fusion log on blummin's phone.

The log should show more assembly loading. I have reversed my changes and the version number is no longer a car, I can't think of it I will do it, it will cause this!

Source code control is absolutely necessary.

Thank you Luke

Last week I encountered the same weird Error.

After creating a new solution (build and run without problems), I found that changing the namespace causes the error.

Hope it helps.

Leave a Comment

Your email address will not be published.