<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>nuget on Carter Griffin</title><link>https://blog.grifflab.org/tags/nuget/</link><description>Recent content in nuget on Carter Griffin</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 08 Feb 2026 20:26:33 -0700</lastBuildDate><atom:link href="https://blog.grifflab.org/tags/nuget/index.xml" rel="self" type="application/rss+xml"/><item><title>Azure Devops + Internal Nuget server for powershell module publishing</title><link>https://blog.grifflab.org/2026/02/08/azure-devops-internal-nuget-server/</link><pubDate>Sun, 08 Feb 2026 20:26:33 -0700</pubDate><guid>https://blog.grifflab.org/2026/02/08/azure-devops-internal-nuget-server/</guid><description>&lt;p&gt;Recently, I found myself needing to distribute code to any windows server host in our environment such that any relevant account local to any host would be able to reliably run my code. Before traversing the internet to figure out how to do this, I considered a couple of low hanging options -&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;Home the modules in some network-accessible file share&lt;/li&gt;&#10;&lt;li&gt;Just push the module out to each target host via work pipeline&#10;&lt;ul&gt;&#10;&lt;li&gt;generic psremoting, ansible, etc&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;/li&gt;&#10;&lt;li&gt;Push module to public psgallery (lol)&lt;/li&gt;&#10;&lt;li&gt;Home modules in fileshare and deploy to all targets via gpo&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;p&gt;The first option, while valid, didn&amp;rsquo;t feel robust enough for our environment - versioning would be dependent on a local git repo at best, and I could not reliably pin old versions without duplicating repo version structure in persistent storage.&lt;/p&gt;</description></item></channel></rss>