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

Unable to build Windows Terminal in Powershell #17505

Open
p0lyMth opened this issue Jul 2, 2024 · 0 comments
Open

Unable to build Windows Terminal in Powershell #17505

p0lyMth opened this issue Jul 2, 2024 · 0 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@p0lyMth
Copy link

p0lyMth commented Jul 2, 2024

Windows Terminal version

1.20.11381.0

Windows build number

10.0.22631.0

Other Software

No response

Steps to reproduce

Under Developer Guidance, I made sure that I had the prerequisites:

  • Running Windows 11 Home, 10.0.22631 N/A Build 22631
  • Developer Mode has been enabled
  • Powershell build: 22621, revision: 3672
  • Windows 11 (10.0.22621.0) SDK is installed
  • Installed Build Tools for Visual (VS without the IDE)
  • Skipped .NET framework targeting pack

I updated the repository with git submodule update --init --recursive

In Powershell, Import-Module .\tools\OpenConsole.psm1 works since I updated the Execution policy for my LocalMachine to run scripts. However, Set-MsBuildDevEnvironment and Invoke-OpenConsoleBuild don't work and return a CommandNotFoundException.

Expected Behavior

The following commands from Building the Code should build the application

Import-Module .\tools\OpenConsole.psm1
Set-MsBuildDevEnvironment
Invoke-OpenConsoleBuild

Actual Behavior

Instead both return:

Set-MsBuildDevEnvironment : The term 'Set-MsBuildDevEnvironment' 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
+ Set-MsBuildDevEnvironment
+ ~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Set-MsBuildDevEnvironment:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
Invoke-OpenConsoleBuild : The term 'Invoke-OpenConsoleBuild' 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
+ Invoke-OpenConsoleBuild
+ ~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Invoke-OpenConsoleBuild:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
@p0lyMth p0lyMth added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jul 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Development

No branches or pull requests

1 participant