Windows 10: Visual Studio Code/PowerShell not working

ShawnK421 · Oct 18, 2020

So I have been programming on and off for past couple years, and have decided to work on learning C++ and C# using Microsoft Visual Studio Code not the one that is preinstalled on the computer. When I opened it up and wrote a basic program, I ran the terminal to see an output like I would with any other program or language. When I did it opened the terminal for about a second and closed, while in the bottom right an error here is a link to the photo with the message: https://imgur.com/a/oEhnMhI appeared. I went searching through forum pages to try and find an answer to the issue, but then I realized that the error said something about PowerShell, so I shifted my focus there. I tried opening the PowerShell to find that it closed immediately after it was opened. I figured that this was the issue that I was looking for and tried looking up solutions to that issue. I tried things that I saw but nothing worked, so I came on here to make my own post to see if anyone knows a solution to my problem. I hope I was informative enough in describing the problem, and if anymore information is required I will reply with it.

Thank You

Specs Just in case:

OS - Windows 10 Home

CPU - AMD Ryzen 5 3600

RAM - 2 x 8 g.skill Trident Z 16GB DDR4-3200 CL16

Storage - Kingston A400 240 GB 2.5" Solid State Drive Seagate Barracuda Compute 2 TB 3.5" 7200RPM Internal Hard Drive

GPU - NVIDIA GeForce RTX 2060 SUPER 8 GB Founders Edition

PSU - EVGA SuperNOVA G3 550 W 80+ Gold Certified Fully Modular ATX Power Supply

:)

Brink · Oct 18, 2020

Announcing PowerShell for Visual Studio Code 1.0

Today we are extremely excited to announce that the PowerShell extension for Visual Studio Code has reached version 1.0! We are shipping this update to line up with the PowerShell Core 6.0 Beta.1 release to provide the official PowerShell development experience for all supported platforms:

Windows 7 through 10 with PowerShell v3 and higher

Linux with PowerShell v6 (all PowerShell-supported distribtions)

macOS and OS X with PowerShell v6

Feature Overview

We’ve been working hard over the last year and a half to put together a first-class development experience for PowerShell that includes the following features:

PowerShell ISE-like interactive development experience with the PowerShell Integrated Console

Rich debugging experience including variables view, call stack, watch window, and various breakpoint types

Integrated script analysis and code fixes provided by PSScriptAnalyzer

Code navigations that allow you to find definitions and references of functions across your script files

Highly configurable code formatter based on community best practices

New file and project creation using Plaster templates

Editor scripting API through the $psEditor object model

You can find instructions for installing VS Code and the PowerShell extension at our GitHub repo.

You can also watch this YouTube video for an overview of using the PowerShell extension and Visual Studio Code (warning, loud audio at the beginning):

qmO9X96v5kM

What does 1.0 mean?

As you probably have already discovered, the PowerShell Team has shifted to an open-source development model for the majority of our projects. This has enabled us to move extremely quickly, responding to customer feedback by releasing updates on a regular basis. Our focus now is on delivering value and quality quickly and incrementally rather than spending months polishing a single version for release.

With that in mind, we have a bit more flexibility on what it means to ship a 1.0 release of our tools. In the case of the PowerShell extension, increasing the version to 1.0 indicates a few things:

The development workflow of the PowerShell extension is stable enough to deliver a rich, interactive experience across all supported OSes – Windows, Linux, and macOS

Our public APIs are stable and will not have breaking changes in future 1.x releases

We will support the PowerShell extension and Visual Studio Code via issues reported through our respective GitHub repositories

Originally we were planning to release a series of beta releases similar to those of PowerShell Core before finalizing our 1.0 release. It turns out that the Visual Studio Marketplace currently does not support pre-release version names like 1.0.0-beta.1, so the clearest option was to continue forward with 1.0 so that we can indicate our level of committment and support of the extension.

What’s coming next?

We’ve got a lot of great improvements planned for the PowerShell extension, many of which will be coming online within the next few releases.

PowerShell “Project Model” via Plaster – We will be expanding Plaster to provide a rich toolset for developing PowerShell modules in any editor supported by PowerShell Editor Services. More details on this effort will be shared in the near future.

PSReadline support – We will add support for PSReadline in the Integrated Console to give the best possible command-line experience within the editor.

Expanded $psEditor APIs – We will make the editor even more scriptable with new APIs added in future updates.

Localization – English is currently the only supported language but we will eventually be adding
other languages as requested by our community and partners.

User Guide – We are currently producing a complete User Guide for the extension that will help new
users become productive quickly!

Instructional Videos – We will be producing a series of videos explaining how to use the PowerShell
extension for script, module, and DSC resource development. Subscribe to the https://www.youtube.com/channel/UCMhQH-yJlr4_XHkwNunfMog to be notified as they are released!

What does this mean for the PowerShell ISE?

The PowerShell ISE has been the official editor for PowerShell throughout most of the history of Windows PowerShell. Now with the advent of the cross-platform PowerShell Core, we need a new official editor that’s available across all supported OS platforms and versions. Visual Studio Code is now that editor and the majority of our effort will be focused there.

However, the PowerShell ISE will remain in Windows supporting Windows PowerShell with no plans to remove it. We will consider investing effort there in the future if there is a high demand for it, but for now we think that we will be able to provide the best possible experience to the PowerShell community through Visual Studio Code.

Keep the feedback coming!

We’ve been receiving a lot of great feedback from the community over the last couple of years which has helped us to prioritize our efforts and deliver a great development experience for everyone. Please feel free to give us your feedback and feature requests at our GitHub repo and click “Watch” to keep up to date with the latest developments.

Thanks a lot for your continued feedback and support, we couldn’t do it without you!

David Wilson – @daviwil
Senior Software Engineer

PowerShell Team
Click to expand...

Source: Announcing PowerShell for Visual Studio Code 1.0! | Windows PowerShell Blog

Brink · Oct 18, 2020

Supporting JUnit 5 in Visual Studio Code

After supporting the widely adopted JUnit 4 with the Java Test Runner extension for Visual Studio Code, we’ve received suggestions to add additional test frameworks, like JUnit 5 and TestNG. We’ve added initial support for JUnit 5, including running, debugging test cases as well as test report. Please give us a try and let us know your feedback.

Expression Evaluation based Conditional Break Point

After introducing expression evaluation in our January release for the Java debugger extension, we are bringing the functionality to conditional break points. Now, you can set your breakpoint to break when an expression evaluates to true. We believe this could be a very useful feature when debugging your Java application using Visual Studio Code.

Other Updates

We’ve also added new features to our Java on Visual Studio Code extension lineup, including:

Java Test Runner

Trigger tests from test explorer on different levels

Add command to open log file

Add setting to specify the position of test report

Tomcat

Add several context commands in Tomcat Explorer

Add support for JVM customization and Tomcat server configuration

Add command palette entries for user input

Maven

Add support for auto-update maven project explorer when pom.xml is updated

Try it out

Please don’t hesitate to try Visual Studio Code for your Java development, and let us know your thoughts! Install the Java Extension Pack which includes Language Support for Java by Red Hat, Debugger for Java, Maven, and the Java Test Runner.

Additional resources

If you’re working on Spring Boot, there are also extensions for Spring Boot Tools and Spring Initializr we’ve developed in partnership with Pivotal.

Learn more about Java on Visual Studio Code.

Explore our step by step Java Tutorials on Visual Studio Code.

Xiaokai He,
Program Manager
Click to expand...

Source: Supporting JUnit 5 in Visual Studio Code | The Visual Studio Blog

Brink · Oct 18, 2020

Emmet 2.0 in Visual Studio Code

August 7, 2017 Ramya Rao, @ramyanexus

In the July 2017 release of Visual Studio Code (version 1.15), we're shipping a better Emmet experience which has been in preview for the past 2 releases.

It's features include:

Emmet abbreviation expansions in suggestion/auto-completion lists.

Multi-cursor support for most Emmet actions.

Updated support for custom Emmet snippets.

As part of this update, we have re-written all of the Emmet actions using new npm modules from @emmetio.

An important change is that the Tab key is no longer the dedicated keyboard shortcut for expanding Emmet abbreviations. Instead, Emmet abbreviations will now appear in the suggestion list. They can be selected like any other smart completion and on selection, the abbreviation will be expanded.

This may take some getting used to but we think you'll see the benefits of Emmet abbreviations being treated as suggestions or smart completions. You can still bind any keyboard shortcut (other than Tabkey) to the editor.action.emmet.expandAbbreviation command or use Emmet: Expand Abbreviation from the Command Palette.

Read on to learn about the Emmet 2.0 changes in Visual Studio Code.
Click to expand...

Read more: Emmet 2.0 in Visual Studio Code

Windows 10: Visual Studio Code/PowerShell not working

Visual Studio Code/PowerShell not working

Visual Studio Code/PowerShell not working

Visual Studio Code/PowerShell not working

Visual Studio Code/PowerShell not working - Similar Threads - Visual Studio Code

VISUAL STUDIO CODE not working

VISUAL STUDIO CODE not working

VISUAL STUDIO CODE not working

Visual studio code c++ compiler not working

Visual studio code c++ compiler not working

Visual studio code c++ compiler not working

Visual Studio Code

visual studio code

Announcing PowerShell for Visual Studio Code 1.0