Is there a trick to having a Web.config file work locally that can then be published to IIS using Core?

When you publish a core app to IIS, it automatically creates a Web.Config file if one doesn't already exist. Unfortunately, if I change anything in the web.config file  that is created in IIS, it gets overwritten with the default created when publishing again to IIS.  If I create one locally, it publishes it to IIS, but the app won't then run locally for me without taking out the following handler:

<handlers><add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModule" resourceType="Unspecified" /></handlers>

I get the HTTP Error 502.5 Process Failure error if I have the line in the Web.config file.

Any ideas?