Bug 51798 - "Help > Xamarin > Open Logs" is sometimes being disabled in VS2017
Summary: "Help > Xamarin > Open Logs" is sometimes being disabled in VS2017
Status: RESOLVED DUPLICATE of bug 53214
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: General ()
Version: 4.3.0 (C9)
Hardware: PC Windows
: Low minor
Target Milestone: 4.3.1 (C9SR1)
Assignee: Bugzilla
Depends on:
Reported: 2017-01-26 19:29 UTC by Ben Beckley
Modified: 2017-03-17 00:23 UTC (History)
4 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 Ben Beckley 2017-01-26 19:29:18 UTC
I have had this happen to me a few times now after starting the IDE. Unfortunately I do not have any reproduction steps. Basically the option is greyed out and you can not click it. It has happened without even loading a Xamarin project. It has also happened after I go to "Tools > Options > Xamarin > iOS" and connected to a Mac agent. I have not checked to see if it is disabled after immediately starting the IDE though.

I will update the bug with more information as I find out more along with logs.

env info: https://gist.github.com/BenBeckley/6cee46340a916674657bd90ebfcb6f14
Comment 1 Ben Beckley 2017-03-17 00:23:41 UTC

*** This bug has been marked as a duplicate of bug 53214 ***