Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Created attachment 21600 [details]
Log file after initial crash
It seems if a user doesn't run Workbooks before trying to open a *.workbook file, it will crash because a first-run initialization isn't fired.
1. Downloaded MSI from link found here: https://developer.xamarin.com/guides/cross-platform/workbooks/install/
2. Installed Workbooks
3. Downloaded "Try Azure for WPF" Workbook from here: https://developer.xamarin.com/workbooks/
4. Double-clicked downloaded "TryAzure-WPF.workbook" file
5. Workbooks launched and crashed: "Workbook failed to load" and "Please see log for details."
Log (see attached for full output):
> [Error][00:00:00.2781326] OpenWorkbook (OpenWorkbook): exception: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.CodeAnalysis, Version=126.96.36.199, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.CodeAnalysis, Version=188.8.131.52, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
I wanted to get the Workbooks version for this bug, so I ran it separately to see if it would give me a chance to find it. Doing so started up some sort of initialization routine.
After this init routine ran, I could open the prior .workbook file fine.
This should be fixed in the 1.3 series.