.NET Editor will stack when use dynamic type variable and Console.WriteLine

dotnet / interactive

.NET Interactive combines the power of .NET with many other languages to create notebooks, REPLs, and embedded coding experiences. Share code, explore data, write, and learn across your apps in ways you couldn't before.

MIT License

2.88k stars 384 forks source link

.NET Editor will stack when use dynamic type variable and Console.WriteLine #3134

Open gewarren opened 1 year ago

gewarren commented 1 year ago

Issue moved from MicrosoftDocs/feedback#3932

Please respond to @1234567Yang.

From @1234567Yang on Wednesday, June 21, 2023 8:13:38 PM

Describe the bug .NET Editor will stack when use dynamic type variable and Console.WriteLine. Example: dynamic a = "1"; Console.WriteLine(a);

To Reproduce Steps to reproduce the behavior:

Go to 'https://learn.microsoft.com/en-us/dotnet/csharp/how-to/parse-strings-using-split#code-try-0'
Open .NET Editor
Use both dynamic keyword and Console.WriteLine();
Click 'run'
See error

Expected behavior The output will stack and continue loading.

Screenshots

Desktop (please complete the following information):

OS: Chromebook(Google Chrome OS Version 114.0.5735.119 (Official Build) (64-bit))
Browser: Chrome
Version 114.0.5735.119 (Official Build) (64-bit)

Smartphone (please complete the following information): Not tested

Additional context No.

gewarren commented 1 year ago

Issue moved from MicrosoftDocs/feedback#3932

Please respond to @welcome[bot].

From @welcome[bot] on Wednesday, June 21, 2023 8:13:41 PM

Thank you for opening an issue! One of our team members will get back to you with additional information.

If this is a product issue, please close this issue and contact the product's support instead. For a list of support websites, see Support for Microsoft products and apps.

gewarren commented 1 year ago

Issue moved from MicrosoftDocs/feedback#3932

Please respond to @gewarren.

From @gewarren on Friday, June 23, 2023 11:33:45 PM

This seems to be an issue with Try.NET. @BillWagner any thoughts how to route this issue?

gewarren commented 1 year ago

Issue moved from MicrosoftDocs/feedback#3932

Please respond to @BillWagner.

From @BillWagner on Monday, August 14, 2023 6:05:51 PM

We should transfer to dotnet/try or dotnet/interactive. @jonsequitur would know which repo is best.

gewarren commented 1 year ago

Issue moved from MicrosoftDocs/feedback#3932

Please respond to @jonsequitur.

From @jonsequitur on Monday, August 14, 2023 6:25:41 PM

dotnet/interactive is the appropriate repo for now.

I'm guessing that dynamic doesn't work generally in the version of the Blazor WASM engine we're using. This may have been resolved in more recent versions of .NET's WASM support. If not, then dotnet/interactive will also not be the appropriate repo, but we can move it there and look into it.