Bug 4747 - No code completion for unsaved XML files
Summary: No code completion for unsaved XML files
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Text Editor ()
Version: Trunk
Hardware: PC Mac OS
: Low minor
Target Milestone: ---
Assignee: Mike Krüger
URL:
Depends on:
Blocks:
 
Reported: 2012-04-30 11:04 UTC by Mikayla Hutchinson [MSFT]
Modified: 2012-05-07 10:53 UTC (History)
1 user (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 Mikayla Hutchinson [MSFT] 2012-04-30 11:04:41 UTC
New unsaved XML files do not have code completion. Saving doesn't enable it - they must be closed and reopened.
Comment 1 Mike Krüger 2012-04-30 11:06:32 UTC
I assume it may be that the editor extension isn't attached correctly.
Comment 2 Mike Krüger 2012-05-07 07:23:03 UTC
We need another category for that.

The xml editor extension checked the name with IsPathRooted - that doesn't work for unsaved files. I don't know why the check is there - I just took it out for now to fix that.
Comment 3 Mikayla Hutchinson [MSFT] 2012-05-07 10:53:03 UTC
I don't know, I think it's something we inherited from when I first imported it. It's probably a workaround the mime system only working with actual file, many years ago. We probably need to get rid of all the URI nonsense in the mime system too.