I’ve had several less-than-stellar experiences installing Web Deploy in the past. Next time I go through this, I decided many months ago, I’m taking notes! ‘Next time’ turned out to be earlier this week. This article is the result of the notes I took during that trial-and-error session....
About a week ago I was happily working away on an ASP.NET Web API project when I noticed something fishy happening. And by “fishy”, I mean incredibly, unbelievably, stupendously frustrating. When initially loaded, the application worked fine. Start the project, execute a command from Postman, get results. But after running for 8 or 10 minutes, results would suddenly stop coming back. It didn’t take long to figure out where it was failing, however why it was failing was another matter entirely....
Recently I’ve found myself looking up IIS process ids juuuuuuust infrequently enough that I haven’t been able to memorize either the command itself or the file location for appcmd.exe, meaning I’ve been looking them up every time I’ve needed them. That, I decided, was too much work, so I actually wrote The Simplest Console App Everk to spit out the information for me. Memorization, schmemorization. Yep, because I’m just that lazy....