Publish to CloudFormation from Visual Studio is great, it gives you the possibility of

Question

0

Asked: May 28, 20262026-05-28T04:00:30+00:00 2026-05-28T04:00:30+00:00

Publish to CloudFormation from Visual Studio is great, it gives you the possibility of

0

Publish to CloudFormation from Visual Studio is great, it gives you the possibility of deploying your web site to a single server or a Load balanced stack.

The problem rises when you want to deploy more than 1 web site in a single server, because in each deployment the main web.config located in c:\inetpub\wwwroot gets modified adding UrlRewrite. This redirects all requests from previous deployed web site to the new one.
I.e.
/
–/FIRST
–/SECOND

If I ask for a page on First it’s searched in /Second/First.

The changes applied are as follows:

    <rewrite>
        <rules>
            <rule name="AWS_DEPLOYMENT" stopProcessing="false">
                <match url="^(https?://[^/]+/)SECOND" ignoreCase="true" negate="true" />
                <conditions>
                    <add input="{PATH_INFO}" pattern="^/SECOND" negate="true" />
                </conditions>
                <action type="Rewrite" url="{R:1}SECOND{PATH_INFO}" logRewrittenUrl="true" />
            </rule>
        </rules>
    </rewrite>

Is there a way to get rid of this behavior and leave main web.config as it is?