WASM and PWA manifest file in IIS, a real struggle

[digger73]

Hi

I have been struggling to get an UNO WASM application deployed as a PWA on an IIS server. The WASM site works fine, however looking in the debug of the browser the Application tab I get a "404 - File or directory not found" for the manifest file. In the index.html I have set the href to <link rel="manifest" href="./package_ba19322c307841da59c8f83e92b35a7e9d50b954/manifest.webmanifest" /> which follows the rest of the links defined in the index file, which seems to work fine. I have tried all kind of paths and placing the manifest files in different location but without luck.

I tried to follow the documentation of UNO, but not much help exists there as it just says for WASM "Add an application to the local web site in IIS and set its physical path to: ...\MyApp\MyApp.Wasm\bin\Debug\netstandard2.0\dist or ...\MyApp\MyApp.Wasm\bin\Debug\net5.0\dist", but the WASM exists in a publish folder. Which is the one I deployed to the IIS.

Looking at the PWA part of the documentation PWA, it just states for the manifest file "This file must not be put in the wwwroot folder.", nothing else.

I'm clearly not an expert in WASM, PWA and website part, but trying to find documentation on how to get this to work just seems to be a big struggle. Tried following microsoft guidelines without help as well.

Just to add, the manifest file works when running in debug mode in visual studio.

Does anyone know how to get this to work ?

[digger73]

After a lot of struggle, I found the problem. The mime type was missing in the web.config ""