@rhessinger

I hate to keep noising up this Otter-related thread, but here are my findings...

I finally solved my issues and have some more tips that should be added to your IIS migration documentation now that you've switched from .NET Framework 4.x to .NET 6.

1. I'm not sure if you still need to mention installation of .NET Framework / ASP.NET 4.x stuff via Windows Features anymore (this one is just speculation, as I'm not well versed in IIS and am not sure if any of your codebase still relies on any lingering .NET Framework 4.x bits).

2. After installing the aforementioned Hosting Bundle, my errors then became about SQL Authentication. Errors in the Windows Event Viewer showed that it was attempting to connect to the SQL server as the computer AD account, not a user/service AD account. Following step #4 from Microsoft's "ASP.NET Core 6.0 Publish to IIS Tutorial", I modified the ProGet Application Pool (which your guide gives creation instructions) to modify the "Identity" under "Process Model" in the "Advanced Settings" of the Application Pool. In my case, I changed this to he same AD Service Account that was previously being used to launch the your self-hosted web service

Lastly, in your current IIS guide in steps 2.3 and 2.4, you say to use the SC (Service Control) command using the Command Prompt. By habit, I am now always using PowerShell and did not realize that SC fails silently under PowerShell. Perhaps replace these with PowerShell Commands, or make note that the commands provided do not work under PowerShell. You did say "Command Prompt", which is correct. So, technically it's on me, but who knew that SC would fail silently under PowerShell -- I sure didn't. The PowerShell equivalent commands are "Stop-Service" and "Remove-Service".

Thanks for everything, I feel bad even talking to you all since I'm a freeloading unpaid user. I just hope I've repaid a tiny bit of your kindness with these documentation tips.

-mike

@atripp

Thanks, I've been giving the switch to IIS a go for the past couple of hours, but am having lots of odd issues. I can't go into them now (going to bed), but one thing of note is that either your IIS guide or installer should include ASP.NET Core Runtime 6.0.x Hosting Bundle. That slowed me down for a bit.

Can you do that step-by-step documentation for enabling HTTPS ASAP? Microsoft released Visual Studio 2022 v17.3 yesterday which includes Nuget v6.3, and with it comes a new compiler warning NU1803, which is thrown when using a Nuget server via HTTP and not HTTPS. Because many of our projects are configured to "Treat Warnings As Errors", it has broken lots of our code. I'm trying to figure out how to enable HTTPS (without going through the trouble of enabling and dealing with IIS), but really can't find anything in the documentation, and just a smattering of loose advice in the forums that's hard to follow. As uptake of this latest update to Visual Studio takes hold, I think you're going to have more and more ProGet users looking for this guide.

Thanks,
-Mike