How/where does ServiceStack cache the razor views?

 

When a request is first made to a ServiceStack service, it goes in and looks for all Razor views, compiles and caches them. Where is the assembly cached for the compiled views stored? When in release mode, will updating the views themselves rebuild the cached assembly?

I ask these questions because I'm seeing a very strange issue on my production box. I updated my whole site with changes to a bunch of razor views. But for some really strange reason, my old views are being rendered and I don't see any changes to the views.

  • I've rebooted at least a dozen times
  • I've deleted everything (all site files) from the server and redeployed
  • I've updated the views directly on the server to see if any changes can be displayed
  • I've updated the web.config so the app can restart
  • I've changed the Temp ASP.NET folder to C:Temp
  • I've changed a static image file, to see if IIS is the cause. But no, IIS sees the new image file and sends it down to the browser.
  • I've verified that all my files are correct on the server.

    • What could be going on? How can the server render old razor views??

    I know a lot of this is vague, but any help would be appreciated.

    The compiled razor views are cached in an in-memory assembly. Touching the web.config to recycle the AppDomain is all that should be needed. I'm not sure why you're seeing old razor views, maybe it's some intermediary caching either on the browser or a reverse proxy cache server.

    链接地址: http://www.djcxy.com/p/65510.html

    上一篇: ServiceStack Razor视图没有编译

    下一篇: ServiceStack如何缓存剃须刀视图？