<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Windows on Michael S. Collier</title>
    <link>/tags/windows/</link>
    <description>Recent content in Windows on Michael S. Collier</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>Michael S. Collier</copyright>
    <lastBuildDate>Wed, 23 Jul 2025 19:27:02 -0400</lastBuildDate>
    <atom:link href="/tags/windows/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Developing with ARM-based Surface Laptop Copilot&#43;PC</title>
      <link>/developing-with-arm-based-surface-laptop-copilot-pc/</link>
      <pubDate>Wed, 23 Jul 2025 00:00:00 +0000</pubDate>
      <guid>/developing-with-arm-based-surface-laptop-copilot-pc/</guid>
      <description>&lt;p&gt;This week I was excited to &lt;em&gt;finally&lt;/em&gt; get my hands on a new PC for my personal use.  I purchased one of the &lt;a href=&#34;https://www.microsoft.com/en-us/store/configure/surface-laptop-15-inch/8mzbmmcjzqc4&#34;&gt;new ARM-based Surface Laptop Copilot+ PCs&lt;/a&gt;. As a developer focused on .NET and Azure, I was eager to see how well this sleek new machine could handle my day-to-day workflow.&lt;/p&gt;&#xA;&lt;p&gt;While performance and battery life have impressed me so far, I’ve run into a few bumps in the road when it comes to local development, especially in areas that rely on platform-specific tooling or containerized environments. In this post, I’ll highlight a couple of early challenges I’ve encountered and what I did to work around them. I’ll update this post as I learn more and adapt my setup.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
