Bug 2726 - md-addins doesn't report unsupported version of MfA
Summary: md-addins doesn't report unsupported version of MfA
Status: RESOLVED NORESPONSE
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Android Add-in ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-01-03 14:16 UTC by Rodrigo Kumpera
Modified: 2016-08-03 15:37 UTC (History)
4 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 NORESPONSE

Description Rodrigo Kumpera 2012-01-03 14:16:56 UTC
The MfA addin checks the version of the installed MfA but doesn't bother to report if an unsupported version is found.

The addin should fail tasks such as build if the version of mandroid is not supported. This is much much better than silently producing broken binaries.
Comment 1 Atsushi Eno 2012-04-23 04:33:39 UTC
With which version of MfA does md-addin fail to build with mandroid? Now our addin is version-aware, so features could be disabled taking it into consideration.
Comment 2 Rodrigo Kumpera 2012-04-23 11:22:12 UTC
I believe I had a 2 releases disparity in the versions. I should probably have reported version numbers.
It was around the time we introduced fastdev that this broke for me as I remember.
Comment 3 PJ 2013-11-19 17:05:30 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 4 PJ 2013-12-05 18:35:54 UTC
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.

Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.