attempt to fix #4146

[jonsequitur]

No description provided.

[Jafar313]

Hi @jonsequitur,
Thank you for your contribution! Could you please share an estimated timeline for merging this PR and resolving the related issue?

[jonsequitur]

I'm still unable to repro the issue so the fix is speculative. I'll need to do some additional verification that this hasn't introduced any issues and then publish a preview release to see if it resolves the issue for you.

[AbhitejJohn]

Should this be 10.0?

[jonsequitur]

Good catch. Yes.

[jonsequitur]

@Jafar313 I've published the potential fix in the preview version of the extension. Please give it a try.

[Jafar313]

@jonsequitur
After updating the extension to the preview version, I encountered a helpful error message that directed me to check the Polyglot Notebook: diagnostics output. The relevant details were logged in the section below:

Extension started for VS Code Stable.
create-tool-manifest: Executing [dotnet new tool-manifest] in 'c:\Users\mousavi\AppData\Roaming\Code\User\globalStorage\ms-dotnettools.dotnet-interactive-vscode'.
create-tool-manifest: Finished with code 73.
create-tool-manifest: STDERR:
Creating this template will make changes to existing files:
  Overwrite   ./dotnet-tools.json

To create the template anyway, run the command with '--force' option:
   dotnet new tool-manifest --force

For details on the exit code, refer to https://aka.ms/templating-exit-codes#73
Error acquiring dotnet-interactive tool: Error: Unable to create local tool manifest.  Command failed with code 73.

STDOUT:


STDERR:
Creating this template will make changes to existing files:
  Overwrite   ./dotnet-tools.json

To create the template anyway, run the command with '--force' option:
   dotnet new tool-manifest --force

For details on the exit code, refer to https://aka.ms/templating-exit-codes#73
Extension activation failed: Cannot read properties of undefined (reading 'workingDirectory')