Bug 25046 - Error in Tasky
Summary: Error in Tasky
Status: RESOLVED INVALID
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 5.1
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Jonathan Pryor
URL:
Depends on:
Blocks:
 
Reported: 2014-12-03 13:19 UTC by je.bissey
Modified: 2017-08-08 17:30 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 INVALID

Description je.bissey 2014-12-03 13:19:01 UTC
C:\Program Files (x86)\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(2,2): Error XA0000: Unexpected error - Please file a bug report at http://bugzilla.xamarin.com. Reason: System.IO.FileNotFoundException: Could not load assembly 'Tasky.Core.Anroid, Version=, Culture=neutral, PublicKeyToken=null'. Perhaps it doesn't exist in the Mono for Android profile? (XA0000) (TaskyAndroid)
Comment 1 asimk 2014-12-08 09:11:14 UTC
I have checked this issue with 'Tasky' sample and not able to reproduce it. I am able to build and deploy tasky sample on device

Screencast : http://www.screencast.com/t/BeXgcVsW

Environment Info: 
VS 2013
XS 4.20.0.28

Please let me know If I missed anything to reproduce this issue. Also, It would be great If you provide me build information where you faced this issue.
Comment 2 Jon Douglas [MSFT] 2017-08-08 17:30:54 UTC
Because we have not received a reply to our request for more information we are closing this issue. If you are still encountering this issue, please reopen the ticket with the requested information. Thanks!