Bug 18815 - Intellisense does not work for iOS Binding projects
Summary: Intellisense does not work for iOS Binding projects
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 1.12.x
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: vsx
Depends on:
Reported: 2014-04-04 09:31 UTC by Jeremy Kolb
Modified: 2016-08-12 15:53 UTC (History)
11 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 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 Jeremy Kolb 2014-04-04 09:31:35 UTC
I've successfully compiled Objective-C Binding projects in Visual Studio but Intellisense/Object Browser do not pick up any of the symbols making it impossible to use Visual Studio with these projects.

Comment 1 Udham Singh 2014-04-04 10:09:00 UTC
I have checked this issue and noticed that "Intellisense/Object Browser" is not working properly for iOS "Binding Project", while it work fine for iOS "Library Project" and iPhone "Empty Project" and others iOS project.

Screencast : http://screencast.com/t/7qq46xo2nm

Environment Info :

Microsoft Visual Studio Professional 2013
Version 12.0.21005.1 REL
Microsoft .NET Framework
Version 4.5.51641

Installed Version: Professional

LightSwitch for Visual Studio 2013   06177-004-0444002-02701
Microsoft LightSwitch for Visual Studio 2013

Microsoft Office Developer Tools for Visual Studio 2013 ENU   06177-004-0444002-02701
Microsoft Office Developer Tools for Visual Studio 2013 ENU

Team Explorer for Visual Studio 2013   06177-004-0444002-02701
Microsoft Team Explorer for Visual Studio 2013

Visual Basic 2013   06177-004-0444002-02701
Microsoft Visual Basic 2013

Visual C# 2013   06177-004-0444002-02701
Microsoft Visual C# 2013

Visual C++ 2013   06177-004-0444002-02701
Microsoft Visual C++ 2013

Visual F# 2013   06177-004-0444002-02701
Microsoft Visual F# 2013

Visual Studio 2013 Code Analysis Spell Checker   06177-004-0444002-02701
Microsoft® Visual Studio® 2013 Code Analysis Spell Checker

Portions of International CorrectSpell™ spelling correction system © 1993 by Lernout & Hauspie Speech Products N.V. All rights reserved.

The American Heritage® Dictionary of the English Language, Third Edition Copyright © 1992 Houghton Mifflin Company. Electronic version licensed from Lernout & Hauspie Speech Products N.V. All rights reserved.

ASP.NET Web Frameworks and Tools 2012.2   4.1.21001.0
For additional information, visit http://go.microsoft.com/fwlink/?LinkID=309563

ASP.NET Web Frameworks and Tools 2013   5.0.11001.0
For additional information, visit http://www.asp.net/

Common Azure Tools   1.0
Provides common services for use by Azure Mobile Services and Windows Azure Tools.

Microsoft Web Developer Tools 2013   2.0.40926.0
Microsoft Web Developer Tools contains the following components:
Support for creating and opening ASP.NET web projects
Browser Link: A communication channel between Visual Studio and browsers
Editor extensions for HTML, CSS, and JavaScript
Page Inspector: Inspection tool for ASP.NET web projects
Scaffolding: A framework for building and running code generators
Server Explorer extensions for Windows Azure Web Sites
Web publishing: Extensions for publishing ASP.NET web projects to hosting providers, on-premises servers, or Windows Azure

NuGet Package Manager   2.7.40911.287
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.

PreEmptive Analytics Visualizer   1.2
Microsoft Visual Studio extension to visualize aggregated summaries from the PreEmptive Analytics product.

SQL Server Data Tools   12.0.30919.1
Microsoft SQL Server Data Tools

Windows Azure Mobile Services Tools   1.0
Windows Azure Mobile Services Tools

Workflow Manager Tools 1.0   1.0
This package contains the necessary Visual Studio integration components for Workflow Manager.

Xamarin.Android   4.12.02001 (a1e3982a)
Visual Studio plugin to enable development for Xamarin.Android.

Xamarin.iOS   1.10.47 (3d6a125d)
Visual Studio extension to enable development for Xamarin.iOS
Comment 2 Brendan Zagaeski (Xamarin Team, assistant) 2014-05-02 12:03:46 UTC
This is approximately a duplicate of bug #16555.

See in particular:

In short, Objective-C binding projects are only supported in Xamarin Studio on Mac, and not yet in Visual Studio [1]. The template project that's included with the Xamarin.iOS Visual Studio extension is misleadingly just a plain iOS _library_ project, and is slated to be removed ASAP [2].

> [1] http://docs.xamarin.com/guides/ios/advanced_topics/binding_objective-c/binding_objc_libs/ 
> [2] bug #19253

The reason Intellisense doesn't work is that the resulting `.dll` is empty. That is, compiled library does not contain any types.  This happens because the "ObjcBindingApiDefinition" Build Action is currently equivalent to a Build Action of "None". 

Thanks for the report!
Comment 4 Joaquin Jares 2015-10-20 15:28:34 UTC
What Brendan states is true: in VS up until 2013 only files marked as Compile will have C# intellisense. This has been solved in 2015 and our cs files in binding projects have intellisense. Marking as Upstream because there is not much we can do about it. The only workaround we have is to set it as Compile while editing, which leads to a looooot of bugs.
Comment 5 Jeremy 2016-06-10 22:26:45 UTC

I'm using VS 2015 and I still don't get intellisense for an iOS Binding Project.  Do you know if this is still an issue?
Comment 6 DeeKay 2016-08-12 15:53:33 UTC
Any news on Jeremys question regarding VS 2015? Having the same issue. Only "workaround" is to not use project references and instead use an assembly reference to output-dll of the binding project.

Just in case anyone is using this workaround: It will break Resharper-functionality for the types within the binding project. To resolve this you have to move the binding project into a separate solution.