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

can not install some environment #5120

Closed
1 of 6 tasks
dothuan2114 opened this issue Dec 22, 2024 · 2 comments
Closed
1 of 6 tasks

can not install some environment #5120

dothuan2114 opened this issue Dec 22, 2024 · 2 comments
Labels
Area-Engine Issue-Bug A bug to squash. Needs: Author Feedback Please give us the requested feedback!

Comments

@dothuan2114
Copy link

Prerequisites

  • I have written a descriptive issue title.
  • I have searched all open and closed issues to ensure it has not already been reported.
  • I have read the troubleshooting guide.
  • I am sure this issue is with the extension itself and does not reproduce in a standalone PowerShell instance.
  • I have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.
  • If this is a security issue, I have read the security issue reporting guidance.

Summary

.\myenv\Scripts\Activate

.\myenv\Scripts\Activate : The term '.\myenv\Scripts\Activate' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify
that the path is correct and try again.
At line:1 char:1

  • .\myenv\Scripts\Activate
  •   + CategoryInfo          : ObjectNotFound: (.\myenv\Scripts\Activate:String) [], CommandNotFoundException
      + FullyQualifiedErrorId : CommandNotFoundException
    
    

PowerShell Version

Name                           Value                                                                                   
----                           -----                                                                                   
PSVersion                      5.1.22621.4391                                                                          
PSEdition                      Desktop                                                                                 
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}                                                                 
BuildVersion                   10.0.22621.4391                                                                         
CLRVersion                     4.0.30319.42000                                                                         
WSManStackVersion              3.0                                                                                     
PSRemotingProtocolVersion      2.3                                                                                     
SerializationVersion           1.1.0.1

Visual Studio Code Version

1.96.2
x64

Extension Version

Steps to Reproduce

.\myenv\Scripts\Activate

.\myenv\Scripts\Activate : The term '.\myenv\Scripts\Activate' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify
that the path is correct and try again.
At line:1 char:1

  • .\myenv\Scripts\Activate
  •   + CategoryInfo          : ObjectNotFound: (.\myenv\Scripts\Activate:String) [], CommandNotFoundException
      + FullyQualifiedErrorId : CommandNotFoundException
    
    

Visuals

No response

Logs

No response

@dothuan2114 dothuan2114 added Issue-Bug A bug to squash. Needs: Triage Maintainer attention needed! labels Dec 22, 2024
@JustinGrote
Copy link
Collaborator

Thanks for you submission! Are you sure your script exists in this path? Is this something that only happens in the vscode-powershell extension? It looks to me like your script doesn't exist, did you forget the extension at the end (.ps1), can you tab-complete the path?

This repository is for the PowerShell vscode extension, and is for issues specifically related to its operation. I recommend aka.ms/PSDiscord for general PowerShell assistance, unless you can demonstrate this is a problem specifically with the PowerShell VSCode extension.

@JustinGrote JustinGrote added Area-Engine Needs: Author Feedback Please give us the requested feedback! and removed Needs: Triage Maintainer attention needed! labels Dec 22, 2024
Copy link
Contributor

This issue has been labeled as needing feedback and has not had any activity a week. It has been closed for housekeeping purposes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Engine Issue-Bug A bug to squash. Needs: Author Feedback Please give us the requested feedback!
Projects
None yet
Development

No branches or pull requests

2 participants