We had a problem with the virtual file system . When we moved the root directory in another place, the razor pages could not find the css… Probably the ServiceStack internally uses the default VirtualSources.
The problem was solved when we copied the css in the directory of the fileSystem. This problem was not identified during debugging time, as from VS, the razor pages were rendered correctly. We don’t want to cache the resouces in memory.
If you replace the existing Virtual File Sources then it can’t find files that are no longer resolvable. If you didn’t want to replace the existing Virtual File Sources, then you should add it to the existing list of Virtual File Sources instead by overriding GetVirtualFileSources() and adding any additional Virtual File Sources as shown in the docs.