Tag Archives: VSCode

Virtual PowerShell Presentation Microsoft User Groups Singapore

Last Friday I presented at the PowerShell Meetup of the Microsoft User Groups based in Singapore. Having been a speakers at the PowerShell Conference Asia, which is also held in Singapore, for the past two years, it was nice to virtually be present in the Microsoft offices again. 

The session I prepared was on the topic of writing PowerShell code, what tools to use and how to leverage the strengths of those tools. I focused the presentation on using both Visual Studio Code, VSCode, and the PowerShell ISE in combination with ISESteroids.

I have uploaded all the materials I used during my presentation to my Events GitHub Repository, which is available here:

GitHub – Jaap Brasser – Events – MSUG Singapore

To get an impression of the event, the event organizer Sebastian Szumigalski was kind enough to provide me with these pictures of the event, be sure to check out his blog it contains a lot of great content. Here are some of the photos to give you an impression of the event.

The PowerPoint slides are also available on SlideShare:

Dutch PowerShell User Group – 10th Edition

Last Thursday we hosted the tenth Dutch PowerShell User Group at Rabobank in Utrecht. It was another full day event starting at 9AM and finishing at 6PM. For this event, we had a diverse range of speakers and as a highlight we had Jakub Jareš visit our user group and giving two presentations on proper testing with Pester and Continuous Deployment for PowerShell.

Due to the enthusiasm of Ben van Zanten, Bartek Bielawski and Daniel Both we had three surprise speakers that added to our already full day of session. Our complete program of the day consisted of the following:

BEGIN END SPEAKER TITLE
09:00 10:00 Jakub Jareš Continuous deployment pipeline for PowerShell modules
10:00 11:00 André Kamman Fighting SQL Server Configuration Drift with Dynamic Pester Tests
13:00 14:00 Jakub Jareš Biggest mistakes when testing with Pester
14:00 15:00 Ralph Eckhard & Sven van Rijen Keep up with NOW! Automate (re-)building your homelab – on steroids!
15:00 16:00 Ben van Zanten Splatting and building new AD forests
16:00 17:00 Jaap Brasser The best tool for the job: Working with VScode and ISE
17:00 17:30 Bartek Bielawski & Daniel Both Distributed configuration management and source control

I have uploaded all the materials I used during my presentation to my Events GitHub Repository, which is available here:

GitHub – Jaap Brasser – Events – DuPSUG 10

For the Dutch PowerShell User Group we maintain a separate repository which we keep updated with all presentation materials as they are made available by our presenters, this is available here:

GitHub – DuPSUG – DuPSUG 10

We would like to extend our thanks to our event sponsor, Rabobank for sponsoring us. The speakers and attendees alike for taking time out of their busy schedules to attend our meeting. To give you an impression of the event here are some pictures of the day:

 

Windows 10 – Start Windows applications from Bash

Working with Bash on Windows, I can say that it significantly simplified the way I can work cross-platform. It has allowed me to use native Linux tools, when working with Linux systems, which is a big step up from using a mix of compiled for Windows Unix tools and GUI applications. Because of this unique functionality Windows 10 has a big lead over any other platform as my day-to-day platform.

For example it is possible to add a new Windows users account directly by using the net.exe tools:

1
net.exe user /add testaccount

Alternatively it is also possible to start Windows PowerShell in Bash to execute a command, for example it becomes possible to use PowerShell to determine which processes are running in the Windows environment and the ps command to determine what is running in Linux:

1
2
powershell.exe -nop -command "Get-Process | Select-Object -First 10"
ps -aux

For me the greatest advantage is the fact that Windows executable files can also be directly called from bash, simplifying the interaction between the different OSes. An example of this is opening explorer in your current working folder in the bash terminal:

1
explorer.exe .

When a path is not accessible for the Windows application, for example anywhere in the Unix file system, a proper error message will be displayed:

1
explorer.exe .

Using this same method it is also possible to add the path to your favorite script editor to the Bash on Windows path allowing them to be directly called from the console. In the following example I will show how to open VSCode directly from Bash:

1
2
3
ls README.md
export PATH=$PATH:/mnt/c/Program\ Files\ \(x86\)/Microsoft\ VS\ Code/
Code.exe README.md

For more information and example of what is possible with the Bash commandline on Windows or I recommend following the Windows Command Line Tools For Developers blog on MSDN.