Bug 26804 - Ignore LinkTarget property in LinkWith attribute
Summary: Ignore LinkTarget property in LinkWith attribute
Status: RESOLVED FIXED
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: master
Hardware: PC Mac OS
: --- enhancement
Target Milestone: Untriaged
Assignee: Rolf Bjarne Kvinge [MSFT]
URL:
: 26865 ()
Depends on:
Blocks:
 
Reported: 2015-02-06 10:29 UTC by Rolf Bjarne Kvinge [MSFT]
Modified: 2015-02-24 12:47 UTC (History)
3 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 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 Rolf Bjarne Kvinge [MSFT] 2015-02-06 10:29:50 UTC
It just confuses people when they upgrade their native libraries with new architectures, and forget to update the LinkTarget property as well.

Also it contains redundant information mtouch can easily figure out by itself.
Comment 1 Rolf Bjarne Kvinge [MSFT] 2015-02-16 12:18:15 UTC
Fixed.

maccore/master: a5654dec3178b735d897da6195696c36a45aabef
Comment 2 Rolf Bjarne Kvinge [MSFT] 2015-02-16 12:28:57 UTC
Correct hash:

maccore/master: 2f6806bed5273238a4f266a6475f924a59185ba1
Comment 3 Rolf Bjarne Kvinge [MSFT] 2015-02-24 12:47:36 UTC
*** Bug 26865 has been marked as a duplicate of this bug. ***