如何在生产环境中删除临时ASP.net文件? [英] How to delete temporary ASP.net files in a production environment?

查看:93
本文介绍了如何在生产环境中删除临时ASP.net文件?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我已经在生产服务器上部署了一个新版本,但是我没有看到此版本中的更改.我发现这是由于临时ASP.net文件夹下的DLL文件的旧版本引起的

I have deployed a new build on Production server, but I dont see the change in this version. I found out that it was caused due to old version of the DLL file under the temporary ASP.net folder

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files 

在DEV环境中,我可以删除,但在Prod中.我被限制访问删除ASP.net临时文件夹中的文件.

In DEV environment, I can delete, but in Prod. I have restricted access to delete files inside the ASP.net temporary folder.

谁能告诉我在部署新文件后如何立即重新创建新的DLL文件?

Can anyone tell me how can I get the new DLL files recreated immediately after I deploy the new files?

谢谢!

推荐答案

将新的DLL添加到bin文件夹时,它们应立即覆盖ASP.NET临时文件夹中的文件.我自己注意到,有时dll(由于发生并发问题而发生)没有加载到内存中.

When you add new DLLs to the bin folder, they should immediately overwrite the files in the ASP.NET temp folders. I have myself noticed that sometimes (I assume that happend becuase of concurrency issues) the dlls are not loaded into memory.

如果您有权访问IIS管理控制台,则可以回收工作进程.那应该确保新的临时程序集已加载.

If you have access to IIS management console, you could recycle the worker process. That should ensure that new temp assemblies are loaded.

此外,如果您更改aspx或ascx文件,则应在temp文件夹中自动替换生成的程序集.如果存在相同的问题,我建议回收工作进程.也许您可以在部署过程中以某种自动化方式将其集成.

Also if you change aspx oder ascx files, the resulting assemblies should be automatically replaced in the temp folder. If there is the same problem, I recommend recycling the worker process. Maybe you can integrate this in some automated way in your deployment procedure.

这篇关于如何在生产环境中删除临时ASP.net文件?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆