Bug 4541 - Error while closing solution
Summary: Error while closing solution
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: Trunk
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2012-04-19 18:00 UTC by Rolf Bjarne Kvinge [MSFT]
Modified: 2012-04-23 11:29 UTC (History)
1 user (show)

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

stacktrace.txt (11.46 KB, text/plain)
2012-04-19 18:00 UTC, Rolf Bjarne Kvinge [MSFT]

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:

Description Rolf Bjarne Kvinge [MSFT] 2012-04-19 18:00:53 UTC
Created attachment 1707 [details]

Once in a while, when closing big solutions/workspaces, I get a dialog that says:

An error has occurred.
Could not close solution "..."
<stack trace is attached>

I haven't been able to reproduce it consistently though, it only happens a couple of times per week.
Comment 1 Mikayla Hutchinson [MSFT] 2012-04-23 08:16:51 UTC
Mike, could you take a look at this? It involves the new type service.
Comment 2 Mike Krüger 2012-04-23 11:29:09 UTC
The bug was that the NSObjectInfoService did an upcast to dotnetproject without checking.  Some of the things in Project should be in DotNetProject - even if they're unused.

Having a project model that supports references can't be really an error - we've around 100 upcasts to DotNetProject - and each of them may fail.

fixed that one.