<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>PowerShell on Chief Engineer's Log</title><link>https://sqltechmike.com/tags/powershell/</link><description>Recent content in PowerShell on Chief Engineer's Log</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 20 Dec 2022 09:00:00 -0400</lastBuildDate><atom:link href="https://sqltechmike.com/tags/powershell/index.xml" rel="self" type="application/rss+xml"/><item><title>Creating an install script from WinGet Export</title><link>https://sqltechmike.com/post/get-winget-install-script/</link><pubDate>Tue, 20 Dec 2022 09:00:00 -0400</pubDate><guid>https://sqltechmike.com/post/get-winget-install-script/</guid><description>&lt;p&gt;I recently bought a new laptop, my first new personal machine since 2015, and with that comes the joy of setting up all of my utilities and applications again. My good friend Rob Sonders (&lt;a href="https://twitter.com/RobertSonders"&gt;Twitter&lt;/a&gt;|&lt;a href="https://www.linkedin.com/in/robert-f-sonders"&gt;LinkedIn&lt;/a&gt;) has been raving about WinGet and how it has simplified his life, so I figured this was the perfect time to try it out. So far I have been really impressed with how simple it makes installing software from all kinds of different sources. I immediately recognized how easy this can be used to script the setup of new workstations, and decided to start maintaining a running list of all the applications I&amp;rsquo;ve installed with WinGet.&lt;/p&gt;</description></item></channel></rss>