Bug 7179 - Intellisense to suggest the mapping of types from Objective-C
Summary: Intellisense to suggest the mapping of types from Objective-C
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: 3.0.x
Hardware: PC Mac OS
: --- enhancement
Target Milestone: ---
Assignee: Jeffrey Stedfast
Depends on:
Reported: 2012-09-14 12:59 UTC by Allie Miller
Modified: 2012-10-24 18:32 UTC (History)
1 user (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 Allie Miller 2012-09-14 12:59:51 UTC
Case #16850

The customer currently copies and pastes Objective C and CocoaTouch code snippets into MonoTouch code file in MonoDevelop and converts them line by line.

They would like to be able to right-click on Objective C and CocoaTouch types and have Intellisense suggest Monotouch types that it can map to. The result is that they just click through the highlighted 'typ missing' errors to correct most of these. This can help speed up code conversions.
Comment 1 Mikayla Hutchinson [MSFT] 2012-10-24 18:32:21 UTC
Bugzilla isn't really the place to track large feature request like this, this really belongs in UserVoice (http://xamarin.uservoice.com).

This would be incredibly hard to fix - we'd need n objective-c parser to understand the context of each symbol. And if we had that, we'd be better off providing some kind of importer, instead of a command for the user to invoke manually on each symbol.