Bug 59257 - Modified csx not reloaded by Workbook
Summary: Modified csx not reloaded by Workbook
Alias: None
Product: Workbooks & Inspector
Classification: Xamarin
Component: Client: Mac ()
Version: 1.3.0 RC 2
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: 1.3
Assignee: xamarininteractive
Depends on:
Reported: 2017-09-06 13:33 UTC by David Ortinau [MSFT]
Modified: 2017-09-07 18:05 UTC (History)
3 users (show)

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

workbook with csx in package (3.98 KB, application/zip)
2017-09-06 13:33 UTC, David Ortinau [MSFT]

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 David Ortinau [MSFT] 2017-09-06 13:33:21 UTC
Created attachment 24598 [details]
workbook with csx in package

I have a workbook that loads a models.csx file. When I modify the csx in VSCode and re-run the load code block, the file is either not being reloaded, or the entire workbook context is not being "reset". 

#load "models.csx"

When I modify a file that is loaded and I re-run that code, the workbook should recognize the change.

Modifications are not recognized in the document.

close and reopen the workbook.
Comment 1 Aaron Bockover [MSFT] 2017-09-07 18:05:50 UTC
This is actually something lacking in Roslyn itself, but I have worked around it in Workbooks. This will be fixed in 1.3.0 stable.

I've filed an issue upstream with Roslyn: https://github.com/dotnet/roslyn/issues/21964