DEV Community

Cover image for Publishing SPA application (ASP.NET Core + Angular) on IIS Server
Flavio Campelo
Flavio Campelo

Posted on • Updated on

Publishing SPA application (ASP.NET Core + Angular) on IIS Server

📮 Contact 🇧🇷 🇺🇸 🇫🇷


Backend App (ASP.NET Core)

Publishing on IIS

You can use this documentation for publishing by command line or this one to know more about dotnet publish command.


# publishing to linux-x64
dotnet publish -r linux-x64 --self-contained true

# publishing to win-x64 ready to run app
dotnet publish -c Release -r win-x64 --self-contained true -p:PublishReadyToRun=true

# publishing using a profile
dotnet publish -p:PublishProfile=FolderProfile
Enter fullscreen mode Exit fullscreen mode

You can also set a runtime identifier to your app for some of your .csproj files

Image 3

You should to install Hosting Bundle to use an core app on IIS.

Be sure to host your app as a sub-application or a new web application because iis virtual directory isn't allowed for hosting an ASP.NET Core app.

Enabling SSL to use HTTPS

On IIS Manager you can use a certificate to enable IIS. Here's a sample of how to create a certificate.

It's recommended to use a valid certificate from a trusted authority in production. Then you can select your application and a certificate as identified by the following image:

Image 4

After that, you can change your settings to require SSL.

Image 5

Image 6


For error 403.16

If you have a 403.16 error with a message like The client certificate used for this request is not trusted by the Web server., you can use this documentation to help you to configure your certificates.

For error 500

If you try to use an ASP.NET Core as a virtual directory, you will probably have this issue. So, be sure you're using a sub-application or a new web application instead. Read this microsoft documentation for further details.

Image 8

Frontend App (Angular)

Publishing on IIS

There are sereral parameters to build an application in production. Angular deployment documentation could show you more options about that.

You can add a new line in the package.json file to create a new alias for the command like that:

Image 10

And then, run this command.

npm run prod
Enter fullscreen mode Exit fullscreen mode

Or execute the full command in the command line. For the both options, the results will be the same.

ng build -c production --base-href /my-app/
Enter fullscreen mode Exit fullscreen mode

my-app modifies the base element in the index.html

Image 1

You should have a web application or a virtual directory with the same alias name

Image 2

Installing URL Rewrite

To support deep-linking, capability to navigate directly to a page by typing the url into the address bar instead of using Angular routing, we should to install URL Rewrite. Deep-linking causes a problem for IIS because the URL that the user attempts to access is not known to the server and therefore the user receives a 404 response. The solution is for the server to always return the root of the application, even if the user requests a path within the application.

Angular on iis

Then, you can create a new web.config file with the content below:

      <rule name="Angular Routes" stopProcessing="true">
        <match url=".*" />
        <conditions logicalGrouping="MatchAll">
          <add input="{REQUEST_FILENAME}" matchType="IsFile" negate="true" />
          <add input="{REQUEST_FILENAME}" matchType="IsDirectory" negate="true" />
        <action type="Rewrite" url="/my-app/" />
Enter fullscreen mode Exit fullscreen mode

You can also add a web.config file to your angular project. And then, insert a new line in your angular.json file that points to this new file under project name → architect → build → options → assets.

Image 7

Typos or suggestions?

If you've found a typo, a sentence that could be improved or anything else that should be updated on this blog post, you can access it through a git repository and make a pull request. If you feel comfortable with github, instead of posting a comment, please go directly to and open a new pull request with your changes.

Discussion (0)