Open ismasanchez opened 2 years ago
Disappointed with current state of .net support in JupyterLab :( Basically it is a proof of concept, unusable for anything without context help. Polyglot notebooks in VSCode are great, but don't like the fact that VSCode is right now the only editor were c# notebooks are really usable.
Disappointed with current state of .net support in JupyterLab :( Basically it is a proof of concept, unusable for anything without context help. Polyglot notebooks in VSCode are great, but don't like the fact that VSCode is right now the only editor were c# notebooks are really usable.
Totally agree. Wanted to switch from LinqPad to polyglot due to charting. But it is totally unusable for now. Intellisence support is almost absent. You need to remember full type names including namespaces and all variables to write the code. So will probably adopt Plotly.Net to work with LinqPad.
As for me intellisense especially in playground-like and data analysis solutions is a core feature, without which the product is almost unusable. IMHO this is prio 1. What sense in developing another features, if writing of simple snipped to analyze data takes 10x time comparing to writing same code in VisualStudio?
When using C# kernel with JupyterLab, signature help is not showing. I've found from other issues that it looks as if it has already been merged, but I can't see the signature help in my computer.
I can get the list of properties/methods (it could be improved if is separated with some icons like in VS Code):
Using python signature help would something like:
Dotnet interactive version installed: 1.0.260601+9d1ecd3c06ba93e59bfef3842d2660c08d9e2ce5 Dotnet version: 6.0.100 Jupyterlab version: 3.2.5