Home Dashboard Directory Help
Search

Windows Phone 8' Unforgivable Exception by Rashad Rivera


Status: 

Closed


1
0
Sign in
to vote
Type: Bug
ID: 790324
Opened: 6/17/2013 10:38:48 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description


This is the closest place to Windows Phone 8 I can get. Sorry if it is not the right place.

I have found a bug in the WP 8 runtime that crashes the app when a type is not found in a assembly namespace that is identified as Strong Named. Basically, if you use the Type.GetType() method to locate a type that does not exist in the assembly (and that assembly path in your string is marked with a PublicKeyToken value), then the runtime will crash instead of letting you handle the System.IO.FileLoadException. I have found this to be the case *only* in the emulator so far.

Details
Sign in to post a comment.
Posted by Microsoft on 7/22/2013 at 9:57 AM
Thank you for submitting this Connect issue. The issue you reported appears to be on a released Windows Phone Product. As we only accept feedback on Visual Studio & .Net Framework through this site, we have notified the Windows Phone team and are closing this issue. If this issue is severe, causing critical business situations or blocking your product development or deployment, please go to http://support.microsoft.com for assistance. To post a question or receive community support for developing Windows Phone apps, consider posting your question or concern on the Windows Phone Development forum. http://social.msdn.microsoft.com/Forums/en-us/category/wpapps.
Posted by Rashad Rivera on 6/27/2013 at 9:29 PM
Awesome. I can't wait for a fix.
Posted by Microsoft on 6/17/2013 at 8:02 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 6/17/2013 at 10:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.