Run in Terminal Button doesn't work

[ArianArsenal]

after executing the Run in Terminal button the terminal opens up and runs the code correctly, but after killing the terminal the button in the right corner (Run in Terminal) doesn't open the terminal again unless you close the vs code and open it again.

[oleg-shilo]

Yes. It is a defect. Thank you form reporting.
Fixed now. PLease update the extension.

[ArianArsenal]

Yes. It is a defect. Thank you form reporting. Fixed now. PLease update the extension.

I updated the extension and now the Run button doesn't work and it says CS-Script is busy
also the run in terminal button now gives me an error which I didn't get in the previous version

A fatal error was encountered. The library 'hostpolicy.dll' required to execute the application was not found in 'C:\User\AppData\Roaming\Code\User\cs-script.user\dotnet'.
Failed to run as a self-contained app.

• The application was run as a self-contained app because 'C:\User\AppData\Roaming\Code\User\cs-script.user\dotnet\cscs.runtimeconfig.json' was not found.
• If this should be a framework-dependent app, add the 'C:\User\AppData\Roaming\Code\User\cs-script.user\dotnet\cscs.runtimeconfig.json' file and specify the appropriate framework.

[oleg-shilo]

Yes, it is a problem it is not caused by the extension but by the CS-SCript itself.

The error "CS-Script is busy" means that you have started the launcher but it does hang for some reason.
You can just kill that instance by using this command:

It's not a solution but only the way to resume your VSCode state.

Can you check, what is the deployment of CS-Script that you are using? I speculate that after upgrade the cs-script config got changed accidentally.

What is your output execution output?
THis is what I have:

[oleg-shilo]

And also can you just check the version of your cs-script deployment:

css --version
# or
dotnet "<whatever your path>\cscs.dll" --version

[ArianArsenal]

This is my output

which i also the same result as the deployment version check

[oleg-shilo]

Yep, this means that your cs-script deployment is corrupted. Most likely you are missing this file:

We will investigate why but let's fix your environment first.

I suggest you install CS-Script outside of the extension. It's more flexible and just easier to update when a new version of CS-Script is released.

You can install CS-SCript from Chocolatey:

sudo choco install cs-script

After that, you can instruct the extension to use this new deployment of cs-script:

[oleg-shilo]

And I managed to reproduce the problem by manually deleting that file.
The problem is that the extension does not have a command for redeploying the built-in engine. This is a design limitation and I am going to address it.

But you can still trigger the redeployment manually by deleting the version file:

Though I would still prefer the choco deployment

[ArianArsenal]

Thanks , i manually installed the CS-Script and changed the path to that , it's fixed for now so thank you.

[oleg-shilo]

Great.
The deployment is not transactional. It cannot be. The VSCode can crash in the middle of the deployment when only half of the files are installed. So actually not having a clear re-deployment option is an unnecessary constraint.
So I am going to implement it in the next release.