<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Chocolatey on ZeroSharp</title><link>https://www.zerosharp.com/blog/categories/chocolatey/</link><description>Recent content in Chocolatey on ZeroSharp</description><generator>Hugo</generator><language>en-gb</language><copyright>Copyright © 2012–{year} Robert Anderson</copyright><lastBuildDate>Thu, 22 Sep 2016 21:04:00 +0100</lastBuildDate><atom:link href="https://www.zerosharp.com/blog/categories/chocolatey/index.xml" rel="self" type="application/rss+xml"/><item><title>Boxstarter and checksums</title><link>https://www.zerosharp.com/boxstarter-and-checksums/</link><pubDate>Thu, 22 Sep 2016 21:04:00 +0100</pubDate><guid>https://www.zerosharp.com/boxstarter-and-checksums/</guid><description>&lt;p&gt;&lt;a href="https://www.zerosharp.com/provisioning-a-new-development-machine-with-boxstarter/"&gt;I&amp;rsquo;ve blogged before&lt;/a&gt; about using BoxStarter to efficiently provision a new development machine.&lt;/p&gt;
&lt;p&gt;This is working very well for our developers. Maintaining the installation script takes a bit of effort but the benefits are worth it.&lt;/p&gt;
&lt;p&gt;Recently, the chocolatey developers have been making things more secure and recent versions now require a checksum with any downloaded package. For now, there seems to be some difficulty using &lt;code&gt;Install-ChocolateyVsixPackage&lt;/code&gt; within BoxStarter scripts.&lt;/p&gt;</description></item></channel></rss>