Bug 1050 - NullReferenceException navigating to a file
Summary: NullReferenceException navigating to a file
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: Trunk
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2011-09-26 07:41 UTC by Alan McGovern
Modified: 2012-04-15 04:20 UTC (History)
5 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description Alan McGovern 2011-09-26 07:41:37 UTC
I got his trying to navigate to a file in MD: http://screencast.com/t/UdnClPS7txCj
Comment 1 Jeffrey Stedfast 2011-09-27 12:01:37 UTC
from what I can tell, this has to be the CompilationUnit that is null, but I don't know for sure...
Comment 2 Jeffrey Stedfast 2011-09-28 14:07:11 UTC
Alan: can you add some debugging CWL's or something to main/src/core/MonoDevelop.Ide/MonoDevelop.Ide.NavigateToDialog/SearchResult.cs TypeSearchResult.get_File()?
Comment 3 Alan McGovern 2011-09-30 09:38:52 UTC
This was probably something to do with navigating to a file which hadn't been processed by code completion or something. I can't reproduce this again. We should be able to handle this case, whatever it was, without blowing up though. Maybe we should just bail out if the CompilationUnit is null.
Comment 4 Mike Krüger 2012-04-15 04:20:33 UTC
Shouldn't happen anymore - the types have now a real type <--> filename connection ...