Bug 19256 - Add warning or error for Xamarin.iOS binding projects, GUID {F5B4F3BC-B597-4E2B-B552-EF5D8A32436F}
Summary: Add warning or error for Xamarin.iOS binding projects, GUID {F5B4F3BC-B597-4E...
Status: VERIFIED FIXED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 1.12.x
Hardware: PC Windows
: High enhancement
Target Milestone: 3.9
Assignee: Joaquin Jares
URL:
Depends on:
Blocks:
 
Reported: 2014-04-23 15:12 UTC by Brendan Zagaeski (Xamarin Team, assistant)
Modified: 2014-12-04 02:54 UTC (History)
8 users (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 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:
VERIFIED FIXED

Description Brendan Zagaeski (Xamarin Team, assistant) 2014-04-23 15:12:18 UTC
As discussed on bug #16555, Xamarin.iOS binding projects are not supported in Visual Studio at the moment.


## Steps to reproduce

Use Visual Studio to attempt to build a Xamarin.iOS binding project that was created in Xamarin Studio on Mac.


## Results

The build output contains a number of warnings plus one error:

error CS0433: The type 'System.Drawing.PointF' exists in both
'c:\Windows\Microsoft.NET\Framework\v4.0.30319\System.Drawing.dll' and
'c:\Program Files (x86)\MSBuild\Xamarin\iOS\monotouch.dll'


## Possible improvement

The current warnings and errors are a little misleading. Perhaps a new warning or error could be created to indicate that "Building Xamarin.iOS binding projects is not currently supported by the Visual Studio extension."

The problematic ProjectTypeGuid is {F5B4F3BC-B597-4E2B-B552-EF5D8A32436F}.


## Warnings

Just for completeness, the current warnings are

> C:\Program Files (x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets(989,5): warning MSB3644: The reference assemblies for framework "MonoTouch,Version=v4.0" were not found. To resolve this, install the SDK or Targeting Pack for this framework version or retarget your application to a version of the framework for which you have the SDK or Targeting Pack installed. Note that assemblies will be resolved from the Global Assembly Cache (GAC) and will be used in place of reference assemblies. Therefore your assembly may not be correctly targeted for the framework you intend.
> C:\Program Files (x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets(1635,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "monotouch". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
> C:\Program Files (x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets(1635,5): warning MSB3270: There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "C:\Windows\Microsoft.NET\Framework\v4.0.30319\\mscorlib.dll", "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.



Thanks!
Comment 1 Dominique Louis 2014-04-28 06:12:10 UTC
This seems to be related to #19253, and looks like we will be removing these from the VS for now.
Comment 2 PJ 2014-05-05 12:35:39 UTC
I'm not sure anyone has been working on comment 1 (remove / update the warnings). Joj is working on a full fix, described in https://bugzilla.xamarin.com/show_bug.cgi?id=19253#c4

Joj says the fix is out of scope for 3.0 in https://bugzilla.xamarin.com/show_bug.cgi?id=19253#c6. 

We could implement the changes requested in the "## Possible improvement" section, but without somebody already working on it I think that request is also out of scope for the release. Please correct me if that is in progress.

For now, updating milestone from 2.0 -> 2.0.1.
Comment 4 Joaquin Jares 2014-12-03 13:50:51 UTC
Fixed in https://github.com/xamarin/XamarinVS/pull/1679