Bug 46264 - If #r attempted before "restoring packages" completes, "Metadata file '{foo}' could not be found
Summary: If #r attempted before "restoring packages" completes, "Metadata file '{foo}'...
Alias: None
Product: Workbooks & Inspector
Classification: Xamarin
Component: Client: Mac ()
Version: master
Hardware: PC Mac OS
: Normal normal
Target Milestone: (C9)
Assignee: xamarininteractive
Depends on:
Reported: 2016-11-01 19:51 UTC by Larry O'Brien
Modified: 2016-12-07 17:26 UTC (History)
4 users (show)

Is this bug a regression?: ---
Last known good build:

Workbook that fails. (3.12 KB, text/plain)
2016-11-01 19:51 UTC, Larry O'Brien

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 Larry O'Brien 2016-11-01 19:51:22 UTC
Created attachment 18289 [details]
Workbook that fails.

When you re-open a workbook that references a NuGet package, the package restoration can take awhile. If, during that time, you attempt to execute code that references the package, you receive, e.g., :

error CS0006: Metadata file 'System.Reactive.Core' could not be found

Workaround: wait until packages are fully restored.
Comment 1 Sandy Armstrong [MSFT] 2016-11-16 17:20:31 UTC
Yes, we are tracking this, and will fix soon. Thanks for filing.
Comment 2 Sandy Armstrong [MSFT] 2016-12-01 05:13:25 UTC
Fixed (will be in 1.1 or whatever the next release is).