my new (working) HP Mini

The replacement for my DOA HP Mini PC arrived today. I originally ordered the PC on June 30, and had hoped to set it up over the July 4 weekend, but now I guess I’m setting it up this weekend. (It does, at least, boot up, so that’s good.)

I think there’s going to be some bureaucratic back and forth on it, in terms of the warranty and registration. My HP account now shows the old broken PC under my name, but not the new one. And the serial number on the new one is not recognized. I had the same problem with the serial # on the previous PC. I get the feeling that HP has some weird cobbled-together system, where the serial # on a new PC doesn’t show in their online systems until a few days (or weeks) after it has shipped. So I think I’ll let it sit, then come back and check again in a week or so.

I may also need to straighten out the three-year extended warranty that I bought with the PC. I never got an email acknowledgement about that, and I don’t know if it’ll automatically attach itself to the new PC, or what. So I’m going to give that a week or so too, then follow up.

Here are some random notes about the basic setup and features on it:

  • It works fine with the IOGear KVM that I bought for it.
  • It appears to have an internal speaker, so I don’t need to worry about hooking up external speakers yet. The internal speaker is obviously not very good, but it’s enough so that I can hear basic audio for now.
  • I bought an external DVD burner to use with it, but haven’t tried it out yet.
  • From the specs, I wasn’t sure if it had Bluetooth or not. It does. So I might pair my AirPods with it, at some point.
  • I also wasn’t sure if it had WiFi or not; it does. I’m planning on sticking with a wired connection, but it’s good to know I can use WiFi if I have to.
  • The initial setup wasn’t too bad. It’s been a while since I’ve set up a PC from scratch. It’s definitely smoother than it used to be. Windows pulled over most of my preferences, settings, and even some installed software from my old desktop. So there’s less stuff to configure and install than there used to be.
  • It came with something called HP Wolf Security, which is probably useless, but I guess I’ll leave it installed. I think it might be a subscription thing that expires after a year. I’ll worry about it then, I guess.
  • I’m starting with OneDrive set to download files on-demand, so my 400 GB worth of files are all still in the cloud and the 1 TB drive is mostly empty. I’ve been slowly getting more comfortable with relying on the cloud; I used to have my desktop PC set to keep all of my files local, so I could back them up. But I turned that setting off a while ago, and have been clicking the “free up space” option on some folders here and there, when I start to run low on disk space. So I guess now I’m just going to let that go entirely and trust the cloud. (Maybe I should shop around for some service that backs up OneDrive to somewhere else…)

Overall, I got a bunch of the basics done today, in the background, while I was working from home. I’ll try to get some of the harder stuff done tomorrow.

I’m not sure when I’m going to switch over and consider it my “main machine.” I guess the most critical piece of software I have now that isn’t largely cloud-based is Quicken. So there’s going to have to be a point where I stop using Quicken on my old PC and start using it on my new one.

And I also need to figure out what I’m going to do with my music library. I still have 100 GB worth of MP3 files on my old PC. It’s all basically synced up to Apple Music at this point, so I could just install Apple Music on the new PC and trust that my library is safe in Apple’s hands.

DOA new PC

The new PC I ordered earlier this week arrived yesterday. I was pretty enthusiastic about getting to spend the three-day weekend getting it all set up. (Yes, I know, I’m a nerd.) But, alas, it arrived DOA.

When I hooked it up, it emitted a series of beeps that, according to this article, means that the computer could not detect its CPU. (Which is of course very bad…) I initially tried to contact tech support, but the support page wouldn’t recognize my serial number. I tried figuring out if there was a different way to get through to support, but there really isn’t.

So I eventually gave up and called order support and arranged to return it. I’ve got that all arranged now, but of course everything is closed today, so I can’t drop it off until tomorrow. And they won’t ship the replacement PC out until they get the broken one back, so it’ll be another week, I’d guess, before I can try this again.

One of the reasons I decided to buy a new PC direct from HP is that a lot of the other options I looked at seemed a bit iffy. (Third party sellers on Amazon and eBay, mostly.) I thought I’d be less likely to get a dud if I bought direct from one of the big PC makers. And I thought support would be smoother too. Oh well.

So now I guess I’m mostly going to be watching Wimbledon this weekend. And maybe doing some reading. So that’s not so bad.

I ordered a new PC

After going around in circles for a while (see yesterday’s post), I actually made a decision and ordered a new PC this morning. It’s an “HP Elite Mini 800 G9”, ordered direct from HP. Total cost was just under $1000.

The MSRP on it is nearly $3500, so it looks like I saved almost $2500. But of course $3500 is a pretty ridiculous price for a mini PC, even if it’s a pretty good one. I don’t really understand the pricing on any of this stuff anymore.

My initial thought was to get a refurbished PC, and spend around $500. But then I decided that I could afford to get a new one, if I could keep the cost around $1000. If I’m lucky, I’ll be able to keep this one as long as I’ve kept my current PC (almost ten years). And if that’s the case, then it might be the last desktop PC I ever buy! It’s weird thinking about that, but it’s possible.

I also ordered a couple of accessories from Amazon: An HDMI to DVI cable, so I can use it with my old monitor, and an HDMI KVM, so I can have both my old and new PCs hooked up at the same time. I almost made a mistake on the KVM. I was going to buy a DVI KVM, thinking that I needed DVI input for my old desktop. In that case, I’d use the HDMI/DVI cable to connect the new PC to the KVM. But then I realized that my old desktop PC actually has an HDMI output port! So I can instead hook both the old and new PCs to the KVM via HDMI, then use the HDMI/DVI cable to go from the KVM to the monitor. Overall, that should be easier to manage (I think), and should leave me in a good place if I decide to replace my monitor. (The monitor, by the way, is even older than the PC; I think I bought it in 2010. So I probably should replace it.)

I’m hopeful that things will work out OK with the KVM. I knew a fair bit about KVMs back around, say, 2000-2010. But I haven’t used one in 15 years. My knowledge on a lot of this hardware stuff is out of date.

I’m hopeful that the new PC shows up before the end of the week. If it does, then I can set it up over the three-day July 4th weekend.

going down a mini PC rabbit hole

All the talk about the end of support for Windows 10 has got me looking at new PCs. My current PC is a Dell XPS 8900, bought from Costco in 2016.

I ruminated about this in a blog post from about a month ago, and I still haven’t quite decided what to do.

Part of me really doesn’t want to give up on my ten-year-old Dell. It still works! I replaced the hard drive with an SSD quite some time ago, so that’s not an issue. It’s got a CD/DVD drive, which I like. And I have no particular problems with Windows 10 that would be solved by upgrading to Windows 11.

I’ve gone back and forth with a lot of ideas:

  • Simple: replace my Windows 10 tower PC with a new Windows 11 tower PC.
  • Complex (and probably a bad idea): Keep using my current PC, but wipe the hard drive and install Ubuntu on it. Move away from Windows, and become a “Linux person”.
  • Kicking the can down the road: Keep using my current PC, and keep using Windows 10. Pay for security updates from either MS or a third party.
  • Get a Mac Mini, and gradually transition to using that as my primary desktop PC. Eventually, wipe and recycle the Dell.
  • Get a new mini PC, running Windows 11. Move my stuff over to that. Wipe and recycle the Dell. Remain a “Windows person” but stop being a “tower PC” person.

So it’s that mini PC track I’ve been on this weekend. I’ve learned a few things. First: new PCs, even mini PCs, are often very expensive these days. I’m looking at stuff from Dell and HP, and it’s $2000 or $3000, if I want 32 GB of RAM and a 1 TB SSD. I don’t know if that’s tariffs or what.

So I’m looking at refurbished stuff. There seems to be a pretty big ecosystem around selling and buying refurbished Mini PCs. I guess they’re mostly units that were used by large companies, and were dumped at end of lease. And it seems like a lot of the ones being sold on Amazon and eBay are not just refurbished, but have also had the original parts (SSD and RAM) replaced. So there’s a lot of stuff out there that looks pretty good, on paper, but might be a little iffy, and it’s hard to compare one guy’s mini PC to another guy’s, even if they appear to be the same model. I guess I should just “spin the wheel” and pick one. For my purposes, anything with enough RAM and a 1 TB SSD should be fine.

Since my current PC and monitor are so old, I’m thinking a bit about the extra complications I’m going to have when I switch to a new PC.

  • My monitor has one DVI port and one old analog VGA port. Any new PC is going to have either DisplayPort or HDMI out, so I’m going to need a DP/HDMI to DVI cable.
  • These mini PCs generally only have headphone ports for audio output. Audio is yet another rabbit hole here. I think the default setup now is to route the audio through the HDMI output, with the video, then have a soundbar under your monitor. But of course that won’t work for me. I may need to buy USB speakers.
  • If I want to keep using a CD/DVD drive, I’m going to need to buy an external USB one.
  • I actually have two 1 TB drives in my current PC: the SSD that I use as the main boot drive, and the original hard drive, which I now use for File History backups. I also have a 2 TB external USB drive that I use for backups (via Bvckup Pro). I’ll keep using the 2TB external, but I’ll need to think about whether or not I want to set up a second external drive for the File History backups.
  • And, if I’m going to keep both PCs going for awhile, I might want to get a KVM, so I can switch between them. The “M” part of that gets a little complicated. Do I want to get a DVI KVM? Am I going to keep the old DVI monitor for long, or should I punt and just get a new HDMI monitor?

As usual, I’m really spinning my wheels on all this stuff. I’m also starting to consider that maybe my end-state will be a mini PC running Windows 11, and a Mac Mini, stacked on top of each other, both connected to a KVM.

Windows 11, and more audio stuff

I feel like I’m blogging too much lately, but I also feel like I have a lot of stuff rattling around in my head, and I need to get it out.

I’ve mentioned in a recent post that we’re in the middle of a company-wide Windows 11 upgrade at work. They finally got around to pushing it out to my desktop on Wednesday and my laptop on Thursday. The desktop upgrade broke networking, which was a bit of an issue. I won’t get into the details, but I had to unplug the PC and walk it over to our help desk so they could get it working again. That cost me a couple of hours, between the upgrade and all the troubleshooting and back and forth.

The laptop upgrade was easier. I had a similar networking issue, but I knew how to fix it now, and could do that myself, in that instance. Also, I could continue working on the desktop while the laptop was updating itself. (With the desktop, I hadn’t brought in the laptop that day, so I was stuck fooling around on my phone while the upgrade was running, and while I was waiting on the help desk…)

Windows 11 hasn’t broken any of the tools I rely on for work. It’s made one or two things slightly harder to do. I don’t think it’s made anything easier. (I’ve probably said this before, but my criteria for OS upgrade success these days isn’t “does it make things better?” but rather “does it break anything important?” and “how much more of a pain is it vs. the old version?”)

I’ve been toying with the idea of upgrading my home desktop PC to Windows 11, despite the fact that it’s not really supported. (The CPU is too old.) I set a registry value that is supposed to bypass the CPU check. But that still wouldn’t allow me to run the installation assistant. So, then, I made a bootable installer on a USB stick, but that won’t let me upgrade, just do a clean install. So, anyway, that was all a waste of time.

Back on the audio stuff: There were three football games airing exclusively on the NFL Network yesterday, and I wanted to watch them. (Maybe not all of them, but I wanted to kill a little time with football playing in the background.) My NFL+ subscription lets me do that, but I couldn’t get the audio working in the NFL app on my Apple TV. This is one of those things that should just be a minor irritation, but I was in enough of a mood when this happened that I got really frustrated with it. I actually could get sound, weirdly, if I switched from my TV speakers to AirPlay output to my Sonos speakers. (I’m using a Sonos soundbar as my TV speaker anyway, but I have it directly hooked up to the TV, so the Apple TV isn’t normally aware that it’s even using the Sonos.) I’m definitely not the only person to have this issue with the NFL app. I’ve found references to it on Reddit and the Apple forums. And the NFL+ site has an article about troubleshooting audio problems, but it’s typically generic and useless.

The frustration was mostly around how complex something as simple as watching TV has gotten… It used to be that you could just turn on your TV, and, you know, watch a football game. Now I have to turn on the TV, switch the HDMI input to the Apple TV, turn on the Apple TV, launch the app, watch it lock up, force quit the app, relaunch the app, wait for it to load, find the right button to press to get into the right feed… Yeah, I know I’m an old man. I should be happy I have so many options for quality entertainment.

And a little more on my new Beats Studio Pro headphones: I found a good video review of them from MKBHD. And I used them last night to watch 65 on Netflix. “Loud dinosaur movie” was a good choice for checking them out. They worked well for that, and successfully drowned out the Christmas music outside.

I’ve been awake today since 5:30 AM. It’s almost noon now. I haven’t done much useful, but I made myself a nice breakfast, went for two walks, listened to some music, read some comics, and had a croissant for a snack, so life is good, I guess.

Quicken Classic

I’ve been using Quicken for a long time, and I’ve been complaining about it for nearly as long. (My earliest Quicken complaint on this blog is likely this one from 2004.) And, once in a while, I get frustrated enough with it that I start looking for alternatives. There were two things that happened recently that have got me interested in that again.

First, they’ve changed the name of the desktop product to Quicken Classic. Here’s a video where their CEO tries to explain that. The name change itself doesn’t really matter to me, but it makes me worry a bit that they’re de-emphasizing the desktop product even more than they already have. Their web product is called Simplifi, and it might be worth thinking about switching to that, but I’m not keen on that idea. I’m pretty sure I’d lose all my history and wouldn’t have nearly the same functionality I have with the desktop app.

The second thing that got me thinking about moving off Quicken again is some continuing issues with the link to my 401(k) account. I’ve searched the web and found a bunch of other people are also having trouble with Fidelity, which is the provider for the 401(k). In my case, the funds got pretty mixed up, so I deleted and re-created the account in Quicken. That got me a bit further, but there was still a weird thing going on where it looked like I had twice as much money in the account as I actually do. I might have fixed that now, but I won’t really know for sure until I sync the account again.

When I have trouble with Quicken, I start getting “the grass is greener on the other side” thoughts, but then if I stop myself, I realize that Quicken is still the biggest player out there, so if Quicken is having issues with Fidelity, then smaller players like Banktivity and MoneyDance probably are too.

Maybe it’s time to give up on this stuff entirely and just switch to keeping a summary spreadsheet, where I update some high-level numbers once a month.

buggy iTunes on Windows, and alternatives

Part of my normal work-from-home routine is to fire up iTunes on my personal desktop PC and play music throughout the day. (On and off, depending on what I’m doing, of course.)

My desktop is a Windows 10 box, so I’m still stuck with iTunes. There’s a preview version of the new Apple Music client available in the Windows Store, but I’ve been leery about trying it. I’m afraid it might do something horrible to my local library, which is almost 18,000 songs, and around 125 GB, at this point. I’d prefer to wait until a 1.0 release.

But iTunes has been locking up on me a lot recently. So I got a bit fed up today and decided to give an alternative client a try. I’d previously tried Cider, but didn’t like it enough to keep it. That was a while ago, though, so I decided to give it another try. It used to be an open-source project, and you can still download that, but the new version is (I guess) closed source, and costs $4 in the Windows Store. I went ahead and bought it and tried it out today, so I thought I’d post some notes on it.

First, it’s mostly just a shell around the web interface for Apple Music. So if you go to music.apple.com and sign in to your account, that’s basically what you’re getting, with some added bells & whistles. It doesn’t deal with your local library at all. (I don’t mean to belittle it here; the bells & whistles might be really handy for some people.)

My major issue with it right now is that it’s got a “dark mode” interface, and no way to switch to a light mode. And I find that hard to deal with. So it’s definitely not something I’m really happy with. But it has done what I needed it to do today: let me stream music to my PC without locking up, like iTunes was doing.

It has occurred to me that another solution would be to stream Apple Music from my iPhone to my desktop via AirPlay. I have something called AirServer on my PC, and it works pretty well for streaming audio from my phone to my PC. Though that, also, is not a great solution.

Or I could go back to CDs! I do still have a CD player in my PC. I could just play CDs via VLC or Windows Media Player or something like that…

Oh well, I’m starting to overthink this stuff again. Time to get back to work…

Some software notes

Two weeks in, and we’re still cleaning up after the security incident at work over the July 4th weekend. I’ve gone into the office most days since then, and I think all that extra exposure to other humans has gotten me sick. I’ve been mostly useless since Friday. I’m hoping I can go back to my usual schedule this week (M/W/F at home, Tue/Thu in the office). Or maybe work from home all this week, if I don’t start feeling better by Tuesday.

Anyway, all the security shake-ups over the last two weeks have gotten me thinking about some of my software choices, and I thought I’d write up some notes on that.

LastPass vs 1Password

I’ve been using 1Password for my personal password storage since 2014, and I’m still happy with it. But I just (finally) got added to our company’s corporate LastPass account, so I can use that for work. And that comes with a free personal LastPass Families account, so I went ahead and signed up for one.

Short version: I don’t think I’ll be using it for anything. I think it’s probably fine for casual users who need a simple password management solution, but it’s not nearly as good as 1Password. I guess my biggest gripe with it is that it’s very much oriented towards in-browser use. There’s a native Windows 10 client, but it’s very limited and just not very good at all. Again, I think it’s probably fine for a lot of people, but it’s just not good enough for a power-user like me.

LINQPad

I mentioned in my last post that I was thinking about upgrading my LINQPad Pro license. I went ahead and did that, and upgraded to the “Premium” version. The NuGet integration works well.  Access to NuGet is still blocked from my developer VM, so I can’t use it there yet, but I can use it on my desktop PC, where I’ve also installed it. I haven’t tried the debugger yet, but I’m curious to see how well that works.

And the dev VM is still so locked down that I couldn’t actually activate the new license over the internet, but the developer provides a way to get around that, so that was appreciated.

TextExpander vs AutoHotKey

On Windows, I generally use AutoHotKey for my keyboard macros and text expansions. I’ve been using it since 2007. I don’t have the actual AHK product installed on any of my work machines, but I have a compiled script that I do run on my work machines. It was starting to look like that might be an issue last week, due to some new security software they were running on our machines. It now looks like it’s OK, but that got me briefly looking at other solutions that might work, and which I might be able to get whitelisted at work.

So I went back to TextExpander, which I used to use on my Mac, circa 20142016. I stopped using TextExpander when they went to a subscription model, since I was having some trouble with it anyway, and it didn’t seem to be worth the money. But that was a while ago, and they now have a Windows client too, so it seemed to be worth looking into it again.

I signed up for a 30-day trial and installed it on my personal desktop PC and MacBook. It works fine, and does some interesting stuff, but it still has some of the same issues with secure input fields that it had when I last used it. That’s not really TextExpander’s fault, but it does limit its usefulness on the Mac. On Windows, it seems to work well, but it’s not nearly as powerful as AutoHotKey. (Or at least it doesn’t seem to be.)

On the Mac side, this has got me thinking again that I should really try Keyboard Maestro. It looks to me like it’s closer to what I want than TextExpander is, and it’s a one-time purchase rather than a subscription. Maybe when things have settled down a bit, and I’m feeling better, I’ll finally give it a try.

I still have some time on the 30-day TextExpander trial, so I’m going to continue messing around with it. Maybe I’ll figure out how to do some fancier stuff with it, and/or how to work around some of its limitations. I really like the idea of having a single macro program that works across Mac and Windows, so that’s a motivation not to give up on it yet.

 

Visual Studio extensions and tweaks

I’ve been spending some time at work recently messing around with my Visual Studio setup. I’ve been fine with my current setup for awhile, but I started getting restless recently. I guess it started when I started reading Clean Code, and watching the associated videos. That got me thinking about automated refactorings, which got me looking at JetBrains Rider and Resharper. And looking at Resharper reminded me of the existence of CodeRush.

I’ve occasionally thought about trying out something like Resharper or CodeRush, but I never got around to it. There are a number of reasons for that, mostly around the cost and the possible performance penalty. But I noticed recently that CodeRush is now available for free, so I figured I’d give it a shot. (And I think Roslyn made it easier for extensions like CodeRush to work without a big performance penalty.)

My normal VS setup, which I’ve stuck with for a while now, is pretty basic, with Mads Kristensen’s Web Essentials, and DPack Rx. I use DPack primarily for the numbered bookmarks, and Web Essentials for a number of random things. CodeRush includes numbered bookmarks, so I thought I’d try removing DPack, installing CodeRush, and seeing how that worked out. So far, I’ve found that CodeRush’s numbered bookmarks don’t work quite as well as DPack’s. There are a number of other interesting features in CodeRush, but I’m not sure if any of them are compelling enough for me to keep CodeRush installed.

I also briefly considered uninstalling Web Essentials, and then just reinstalling the specific extensions from that collection that I’m actually using. But I couldn’t quite talk myself into that, so I’ve still got the whole collection installed.

On a related subject, I recently listened to an episode of .NET Rocks with Mads Kristensen on VS 2022 extensions. And another one with Mark Miller (author of CodeRush). I’m not currently subscribed to .NET Rocks in my podcast client, but I do check in on it occasionally to see if there’s anything interesting.

Getting back to the general subject of VS extensions and setup, I also revisited my work setup and tried to decide if I could switch from VS 2019 to VS 2022. I do my VS development at work on a VM that’s running Windows Server 2012 R2. That probably seems weird, but it’s necessary for Dynamics AX development. And VS 2022 isn’t supported on Server 2012, though I could probably get it to work. So I’ve been going back and forth on whether or not I should try to install it on my current VM, or maybe ask my boss for a new Windows 10 VM to use for VS 2022. I’ve decided to stick with VS 2019 for now, but I may need to ask for a new VM at some point. In part because I have a .NET 5 project in VS 2019, and .NET 5 is no longer supported. And .NET 6 isn’t supported in VS 2019. So it’s all kind of complicated. Asking for a new VM shouldn’t be a big deal, but I’m a little nervous about it, since I just got a new boss, and I’m now in a different sub-division of the IT department, and the rules about this stuff might be a little different than they were under the old boss, so I want to feel things out a bit before I start asking for stuff.

I did install VS 2022 on my personal laptop back in May. I do like it, and would love to be able to switch over to it. (Unlike some previous versions of VS, they don’t seem to have made any really bad UI decisions that make me want to stick with the older version…)

I also spent a little time messing with the default font in VS on Friday. I’ve stuck with Consolas for quite some time now. But  I was watching a LinkedIn Learning video on Friday where the teacher’s setup was using Cascadia Code, and it looked kind of nice. I’d read about Cascadia Code when it came out, but I never got around to trying it. So I switched over to it for a little while, but then decided to switch back to Consolas. The whole code ligature thing is interesting, but Consolas just seems to work better for me.

All of this fiddling around made me think about the balance between sharpening the saw and… pointless procrastination. (It’s bothering me that I know that there’s a clever metaphor similar to “sharpening the saw” that basically means “pointless procrastination”, but I can’t remember what it is.)

Well, I’ve now killed a bunch of time on a hot Saturday morning, drinking iced coffee, waiting on my grocery delivery, and writing a rambling blog post. My plan for the rest of the day revolves mostly around watching the last two episodes of Stranger Things on Netflix. Life is good, I guess.

Clean Code, Visual Studio, Windows 11, and a bit more on ebooks

I wanted to add some more notes about the whole Kindle, EPUB, MOBI, etc. thing that I’ve been blogging about in my last few posts. As I mentioned a few posts back, I’ve been working my way through the Clean Code learning path in O’Reilly. Since I’m probably going to lose access to O’Reilly before I’m done with that, I thought I’d buy a copy of the Clean Code book, so I could finish reading it at my leisure, and to have it for later reference. With tech books, I usually like buying a DRM-free ebook directly from the publisher, when possible. In this case, I initially had some trouble finding that, but eventually figured out that it’s purchasable through the InformIT site. I bought the Robert C. Martin Clean Code Collection ebook, which contains both Clean Code and The Clean Coder. I had a discount code, so it was about $40 total.

I copied the EPUB, MOBI, and PDF files for the book to OneDrive. There are a number of ways I can read an ebook on my iPad, if it’s DRM-free and available in multiple formats. For this one, I wound up sending it from OneDrive into my Kindle app, as a MOBI file. That method still doesn’t support EPUBs. And it will copy the file up into my Kindle library, which is nice. I don’t think I’d ever copied anything into the Kindle library that way before, but it worked fine. I also copied the PDF into GoodReader. The code listings in the MOBI version look a little weird, which is a common problem with tech ebooks, so it’s nice to have the PDF handy as an alternative.

Clean Code has some example refactorings that are fairly interesting. They’re all in Java, but I thought it might be interesting to take the original Java code for one of the examples, convert it to C#, get it working, then work through some refactoring that’s similar to what Uncle Bob does in the book/videos. I found some of the code for the examples in GitHub under the Clean Code Kata user account. (I’m not sure if that’s an “official” account for Bob Martin or his organization, but either way, the code is there.)

This idea to convert some of the examples to C# and work through them was prompted in part by a desire to set up a .NET dev environment of some sort on one of my personal machines, and to maybe experiment a bit with some of the more recent .NET stuff, like .NET 6 and VS 2022. I realized that I don’t currently have any dev stuff at all set up on my desktop PC, my MacBook, or my Lenovo laptop. The MacBook is new, so I just haven’t set any dev stuff up yet. The Lenovo was bought in 2020, and I haven’t gotten much use out of it at all. And I’ve been trying to keep the desktop PC free of any heavyweight dev tools, since I just want to keep it clean for personal productivity stuff. After going back and forth on a few possible setups, I decided to install Visual Studio 2022 (Community edition) on my Lenovo laptop. I considered just installing the .NET 6 SDK and Visual Studio Code, which would have been much more lightweight, but I’m used to using the full VS product, and I can’t see a reason not to use it. And the Lenovo is the best place to install it, since I can wipe out that machine entirely and start fresh if things get too messed up. I’ve also recently upgraded that laptop to Windows 11, so this was also an opportunity to (finally) give that a try.

Of course, I’ve had other things to do this weekend too, so I’ve only gotten as far as installing Visual Studio and git, and tweaking some settings. Maybe I’ll actually do some programming next weekend. (Or maybe I’ll get distracted by something else, and the whole thing will fall by the wayside.)