Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The Razor component type is not always available to the next code blocks #2

Closed
plbonneville opened this issue May 31, 2021 · 3 comments
Labels
bug Something isn't working

Comments

@plbonneville
Copy link
Owner

plbonneville commented May 31, 2021

Expected behavior

The component type should be available to the next code blocks.

  1. #!blazor --name HelloWorld
    <h1>Hello world</h1>
  2. #!csharp
    var component = new HelloWorld();
    component.GetType().Name

Actual behavior

When running in Jupyter, the previous compilation doesn't contain the Razor component type.

This currently works when running in VS Code (on Windows) with both .dib and .ipynb file types. Doesn't work in VS Code when running in a remote dev container.

This works as expected in the unit tests on Windows. The tests don't pass when running on Linux.

@plbonneville plbonneville added the bug Something isn't working label May 31, 2021
@plbonneville
Copy link
Owner Author

plbonneville commented May 31, 2021

This appear to be the same issue as dotnet/interactive#1378

@plbonneville
Copy link
Owner Author

await kernel.SubmitCodeAsync(c);

@plbonneville
Copy link
Owner Author

This was a \r\n vs \n issue. Nothing to see here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant