Visual Studio updated and broke my builds, by flagging a bunch of Nuget packages as vulnerable, and stopping the builds with no ability to disable this issue. Well guess what my install of Orchard using dotnet 7, had a few which I gave up trying to find the correct projects to actually update to fix it, due to the dependencies. So I started trying to redo the solution using Orchard's Nuget packages, which seems pretty easy, I have it building, at least, but not functional. So my changes for the comic book website will not be updated until I can fix. I have also worked on geting devops build/ releases working. So I have automated the build/release of this website, so its all automated when I check in my changes it will deploy. I had to redo the Pool Permissions for the folders after updating for some reason. Tooks me a while to remember how to set the permissions properly for IIS pools, but now I have the site working again.
I did finally get SSL cert's for my devops server, which allowed the Agent services to be linked up and work. and had to make sure the proper ports are open. So I have to be careful on firewall rules. The Joy of firewall rules on a brain-dead hardware, best I can do is simple rules. It took me awhile to get git commits working, but I finally did. I am learning the IT end of managing a non Cloud install of Azure DevOps, not exactly what I wanted, I do have experience using the cloud version of Azure Devops. I just wanted a self-hosting solution to replace Source Gear Vault, which I was previously using which was pretty simple. I am currently runinng Azure Devops in a vm, which seems to be hamstringing it. But I think I can help it by adjusting that vm ram and CPU process's upwards, but have to balance it with the other vm's I have on my server.