Hi Darren,

I tend to go for the URL rewrite approach. Something like this:

<rewrite>
  <rules>
    <rule name="Favicon Site 1">
      <match url="^favicon.ico$"/>
      <conditions>
        <add input="{HTTP_HOST}" pattern="^mysite1.com$" negate="false" />
      </conditions>
      <action type="Rewrite" url="/favicons/site1.ico"/>
    </rule>
  </rules>
</rewrite>

If you need more logic than the rewrite rules allow, you could tie in to the Application_BeginRequest event in an HTTPModule or global.asax at which point you can do whatever you need to establish the correct favicon and to swap it out using Context.RewritePath().

Hey Paul thanks for your rewrite rule.

I was hoping to avoid the need for a developer to update the rewrite rules and deploy code when a new site gets added. It feels a little odd that there is an Admin UI that allows you to create a new Site but there are still some things that need code changes.

It's a pretty minor issue, I'm not sure if it's worth finding a more dynamic solution. We have had some new Sites added on Production recently that have 100% reuse of code, but that is quite rare, I think most new sites include some new code, we'll just need to include updating the rewrite rules as a task for each new site.

Thanks again.