So, from my experience, masterpages sometimes can lag when you do updates. This is not a new occurance, you make a change, you build, you go to test and the MasterPage is still looking for the old control.
因此,根据我的经验,当您进行更新时,masterpages有时可能会滞后。这不是一个新的出现,你做了一个改变,你建立,你去测试,MasterPage仍然在寻找旧的控件。
Anyone have any tips/tricks they use when this happens? Usually it goes away after a while, but I don't have a while.
当发生这种情况时,任何人都有任何提示/技巧吗?通常它会在一段时间后消失,但我没有一段时间。
I am using VS 2008.
我正在使用VS 2008。
4 个解决方案
#1
2
The three main options for forcing IIS to reload everything are
强制IIS重新加载所有内容的三个主要选项是
- If running from Visual Studio, close out the ASP.NET Development Server, which forces it to re-open with the next run
- Change the web.config file (forces an IISReset)
- Call IISRESET directly from the command line
如果从Visual Studio运行,请关闭ASP.NET Development Server,这会强制它在下次运行时重新打开
更改web.config文件(强制IISReset)
直接从命令行调用IISRESET
#2
0
Sounds like a caching issue. Do you restart IIS after you build? Are you building in place or publishing? Is this a web app?
听起来像是一个缓存问题。构建后重新启动IIS?你在建立或出版?这是一个网络应用程序?
Try making a small change to the web.config file when you build and see if that helps. It will reset the server for you and basically make things new again. :)
在构建时尝试对web.config文件进行一些小改动,看看是否有帮助。它将为您重置服务器,并基本上重新制作新的东西。 :)
#3
0
When testing in IE, I find I have to actually click the refresh icon, not simply go to the address bar and hit enter again (like in Firefox) to have IIS push the updated content to me.
在IE中测试时,我发现我必须实际点击刷新图标,而不是简单地转到地址栏并再次按回车(如在Firefox中)让IIS将更新的内容推送给我。
#4
0
If I see something in my browser that is 'stale' I hit control-f5 which forces a full trip back to the server to retrieve everything. This always gets me the latest version of everything without having to restart iis, play with the web.config, etc.
如果我在浏览器中看到“陈旧”的东西,我会点击control-f5,强制完全返回服务器以检索所有内容。这总是让我得到一切的最新版本,而无需重新启动iis,使用web.config等。
#1
2
The three main options for forcing IIS to reload everything are
强制IIS重新加载所有内容的三个主要选项是
- If running from Visual Studio, close out the ASP.NET Development Server, which forces it to re-open with the next run
- Change the web.config file (forces an IISReset)
- Call IISRESET directly from the command line
如果从Visual Studio运行,请关闭ASP.NET Development Server,这会强制它在下次运行时重新打开
更改web.config文件(强制IISReset)
直接从命令行调用IISRESET
#2
0
Sounds like a caching issue. Do you restart IIS after you build? Are you building in place or publishing? Is this a web app?
听起来像是一个缓存问题。构建后重新启动IIS?你在建立或出版?这是一个网络应用程序?
Try making a small change to the web.config file when you build and see if that helps. It will reset the server for you and basically make things new again. :)
在构建时尝试对web.config文件进行一些小改动,看看是否有帮助。它将为您重置服务器,并基本上重新制作新的东西。 :)
#3
0
When testing in IE, I find I have to actually click the refresh icon, not simply go to the address bar and hit enter again (like in Firefox) to have IIS push the updated content to me.
在IE中测试时,我发现我必须实际点击刷新图标,而不是简单地转到地址栏并再次按回车(如在Firefox中)让IIS将更新的内容推送给我。
#4
0
If I see something in my browser that is 'stale' I hit control-f5 which forces a full trip back to the server to retrieve everything. This always gets me the latest version of everything without having to restart iis, play with the web.config, etc.
如果我在浏览器中看到“陈旧”的东西,我会点击control-f5,强制完全返回服务器以检索所有内容。这总是让我得到一切的最新版本,而无需重新启动iis,使用web.config等。