Install Jupyter kernels gives user no control over build process

[Zireael]

Describe the bug

dotnet try jupyter install I'm building a Docker image based on Debian with Jupyter installed through Anaconda.

Can you: 1) add option to specify Jupyter kernel install folder destination 2) Add the whole /try package to Anaconda registry, so that the installation is consistent for virtual environments 3) Not use dot (.) in folder names

When running dotnet try jupyter install, the Jupyter kernels get installed in .net-csharp and .net-fsharp folders.

/home/${USER}/.local/share/jupyter/kernels/.net-csharp /home/${USER}/.local/share/jupyter/kernels/.net-fsharp

The dot (.) gets interpreted on Linux as a hidden folder and it's annoying, since the install location is actually incorrect and I move the folders to Anaconda environment. Them being hidden makes the mv command more wordy.

Did this error occur while using dotnet try or online?

• [x] dotnet-try
• [x] .NET Jupyter Notebook
• [ ] online

What kind of error was it?

• [ ] User Interface (UI): For example the output never displayed
• [ ] Service Error: For example "The service is temporarily unavailable. We are working on it"
• [x] Other: user has no control over build process

Please complete the following:

• OS
  • [ ] Windows 10
  • [ ] macOS
  • [x] Linux (Debian 10, Docker build)
  • [ ] iOS
  • [ ] Android

[colombod]

Could you expand on the second point?

[jonsequitur]

I've created issue dotnet/interactive#27 to track the dot-prefixed folder issue.