0

I was trying to download httpPlatformHandler and I discovered that it has been deprecated by ASP.NET Core.

Now if you want a web app to sit behind IIS, you have to use ASP.NET Core instead.

How does this change the configuration?

Before what I had was something like the following:\

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <system.webServer>
        <handlers>
           <add
               name="httpplatformhandler_rootWiki"
               path="*"
               verb="*"
               modules="httpPlatformHandler"
               resourceType="Unspecified"
               requireAccess="Script" />
        </handlers>
        <httpPlatform
           stdoutLogEnabled="true"
           stdoutLogFile=".\node.log"
           startupTimeLimit="20"
           processPath="C:\Program Files\nodejs\node.exe"
           arguments=".\node_modules\tiddlywiki\tiddlywiki.js ./wiki --listen port=PORT"
        >
           <environmentVariables>
                <environmentVariable name="PORT" value="%HTTP_PLATFORM_PORT%" />
                <environmentVariable name="NODE_ENV" value="Production" />
           </environmentVariables>
        </httpPlatform>
    </system.webServer>
</configuration>
marc_s
  • 732,580
  • 175
  • 1,330
  • 1,459
leeand00
  • 25,510
  • 39
  • 140
  • 297

1 Answers1

3

I edited the tag to point out that you were misled by an irrelevant article (only ASP.NET Core applications should switch to ASP.NET Core module),

https://stackoverflow.com/tags/httpplatformhandler/info

Lex Li
  • 60,503
  • 9
  • 116
  • 147
  • I see they (or you) also closed the ticket. So, is only deprecated for ASP.NET Core applications? So they're keeping it around? – leeand00 Apr 13 '22 at 19:47