Bug 14890 - Go to Declaration fails with "File is already open in another project."
Summary: Go to Declaration fails with "File is already open in another project."
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Shell ()
Version: unspecified
Hardware: PC Mac OS
: Low normal
Target Milestone: master
Assignee: Mike Krüger
Depends on:
Reported: 2013-09-20 15:21 UTC by Alex Corrado [MSFT]
Modified: 2013-09-23 04:02 UTC (History)
2 users (show)

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:

Description Alex Corrado [MSFT] 2013-09-20 15:21:35 UTC
I use the Go to Declaration feature a lot, but now I am frequently seeing the error, "File is already open in another project." I do have multiple projects open that contain the same source files, but this shouldn't prevent me from navigating.
Comment 1 Mike Krüger 2013-09-21 00:47:23 UTC
Hm, it's a limitation of 'linked' files and not of go to declaration.
A file can only be open in one project at a time - or too many things won't work. 

Linked files are problematic.

However maybe I can 'switch' the project of open documents for go to declaration. But when using linked files the user should be 'aware' of the problems behind that.
Comment 2 Mike Krüger 2013-09-23 04:02:01 UTC
I think I've found a working solution.