Home Dashboard Directory Help

Windows 8 and Lightswitch by SPART123


 as Not Reproducible Help for as Not Reproducible

Sign in
to vote
Type: Bug
ID: 769034
Opened: 10/29/2012 7:25:43 AM
Access Restriction: Public
User(s) can reproduce this bug


I am having an issue with a light switch project. The project runs fine on Windows 7 with VS2012, but when we move to windows 8, then app does not function.

Basically if we have a search screen, which has a link to open a details screen. If we then close the details screen and then close the search screen we get the message "object not set to an instance of an object".

I have run this with all debug exceptions thrown and the message does not change.

The same app on windows 7 runs fine.

Okay, looks like the problem is related to using a hyperlink to navigate to the detail form from the search grid. The following comes out of the debugger:

System.NullReferenceException occurred
Message=Object reference not set to an instance of an object.
        at System.Windows.Controls.DataGrid.EndCellEdit(DataGridEditAction editAction, Boolean exitEditingMode, Boolean keepFocus, Boolean raiseEvents)

Sign in to post a comment.
Posted by Microsoft on 1/23/2013 at 11:41 AM
Thanks for reporting this issue (and providing such detailed repro steps). Unfortunately, even with those steps, I have not been able to reproduce the problem. To avoid any possible difference in steps in producing the repro, would it be possible for you to share a project that exhibits this problem with us (please make sure you do not include any information/code that you are not willing to share with us). Alternatively, if you could provide a callstack for that shows where the error occurred.

Other things that may cause this to not reproduce on my machine would be different versions of Silverlight (unlikely). I am running 5.1.10411.0 - can you please check if you are running the same version.

Best regards,
Johan Stenberg, Microsoft LightSwitch team.

Posted by Microsoft on 12/6/2012 at 3:47 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by SPART123 on 12/4/2012 at 6:14 AM
Just as a further note to this, I did try running in /safemode and the same error occurs.

Posted by SPART123 on 12/4/2012 at 5:56 AM

This was pretty easy to duplicate on a new project as well. Using Lightswitch in VS2012 create a search screen and a detail screen. On the search screen add a hyperlink and the target is set to the detail screen. Next, make sure you are using the standard blue theme and standard shell.

When you click on the hyperlink the detail screen opens, next, close the detail screen, then close the search screen. The error will then appear on close of the search screen. It is like the edit of the grid cell is firing (EndCellEdit) after using the hyperlink. If I use the edit button instead, the error does not occur.

When I change to the Cosmo theme/shell the problem goes away.

When I run the same project on VS2010 and Lightswitch 11 then problem also goes away.

Note that I am running on a Windows 8 machine.

Posted by Microsoft on 12/4/2012 at 1:11 AM
Thanks for your feedback.

In order to fix the issue, we must first reproduce the issue in our labs. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you repro it with VS12 in safemode? And Could you please give us a simple repro project so that we can conduct further research?

Please submit this information to us within 3 business days. We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 11/29/2012 at 4:52 PM
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)
Posted by caillaud jean-michel on 11/26/2012 at 7:48 AM
Yes, I have found that if I changed from the standard blue theme to the new Cosmopolitan theme the problem goes away. Still appears to be a bug of some kind but at least it works in the cosmo theme!!!!!!!!
Sign in to post a workaround.
Posted by SPART123 on 11/13/2012 at 12:50 PM
Ok, I have found that if I changed from the standard blue theme to the new Cosmopolitan theme the problem goes away. Still appears to be a bug of some kind but at least it works in the cosmo theme!