"Object reference not set to an instance of an object" opening a file in the solution explorer - by Jerome Laban

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


2
0
Sign in
to vote
ID 500551 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 10/23/2009 7:02:51 PM
Access Restriction Public

Description

Cannot open a text editor if the font used is "Proggy Opti Small" (http://www.proggyfonts.com/index.php?menu=download).

A null reference exception pops up without any further details after double clicking on a C# file icon in the Solution Explorer.

From analysing previous exceptions with a debugger, a few other exceptions thrown in System.Drawing.dll are masked by the NullReferenceException. (ArgumentException: Only TrueType fonts are supported. This is not a TrueType font.) 

I'm marking this issue as blocking because the error is not detailed enough for the user.

Also, selecting a new font does not fix the issue right away. A complete restart of visual studio is mandatory.

If non TrueType fonts are not supported, they should not be displayed as a choice in the font selector.

A memory dump is available if necessary.
Sign in to post a comment.
Posted by Sean [MSFT] on 10/30/2009 at 10:12 PM
Jaylee512,

Thank you for reporting this issue. As you suspected this is a result of raster fonts not being supported with Visual Studio 2010 and WPF 4.0. For further information on this issue, please check out our blog post: http://blogs.msdn.com/visualstudio/archive/2009/10/27/VS-2010-Beta2_3A00_--Workaround-for-Raster-Font-Settings-Issue.aspx

I'm resolving this issue as fixed and you shouldn't be able to get the release version of Visual Studio into this state as it will filter out raster fonts.

Thanks!
-Sean Laberee
VS Platform Team
Posted by Microsoft on 10/26/2009 at 5:00 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)