blocks|key|207005|text|当使用进程内模式时，您的会话数据托管在服务器内存中。您应该在IIS上验证应用程序池回收时间。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|207006|干杯,|207007|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

when using in-proc mode, your session data is hosted at server memory. You should verify on your IIS about application pool recycle time.

Cheers,

blocks|key|3061392|text|您可以尝试SQL+server会话状态模式。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3061393|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

you can try SQL server session state mode .

blocks|key|209200|text|这里的问题是您的应用程序正在执行动态编译，这意味着对标记文件的任何更改都将导致应用程序重新启动。如您所知，任何应用程序重启都将转储InProc会话。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|209201|本地模板上的"Web应用程序“的设置有所不同，因此不会重新启动整个应用程序。尽管如此，预编译还是有好处的。|209202|有几种方法可以解决这个问题。|209203|为什么会发生这种情况|offset|length|style|BOLD|209204|默认情况下，ASP.NET+4.5允许您同时运行"web页面“和"web应用程序”。这可能是导致对aspx的更改触发预压缩的原因(每次发生更改时，“网页”都必须这样做)。更多信息请点击此处：http://msdn.microsoft.com/en-us/library/dd547590.aspx|209205|在新版本中也有相当多的变化来优化web服务器。您可以在此处查看这些更改的详细信息，它们还可以在您升级时解释这些更改。http://www.asp.net/vnext/overview/aspnet/whats-new|209206|无论如何，解决方案仍然是相同的，并且不建议动态更新单个aspx文件。如果这是不可避免的，那么重启最终会在任何设置上发生，所以无论如何都值得使用下面的解决方案之一。|209207|解决方案|209208|编译模式|209209|检查web.config中的CompilationMode。有关更多信息，请查看此帖子http://www.campusmvp.net/compilationmode-avoiding-aspx-page-compilation-to-improve-scalability-in-sites-with-thousands-of-pages/|209210|这也可以在服务器级别上设置，这样您就可以根据环境来获取差异。|209211|会话状态模式|209212|您可以在StateServer模式下或使用Sql+server运行会话状态。如果安装了.net并且只需将其设置为自动启动，则ASP.NET状态服务器将位于您的服务器上。然后，您可以在配置中对其进行切换。|209213|<sessionState+mode="StateServer"+useHostingIdentity="true"+cookieless="false"+timeout="120"+stateConnectionString="tcpip=127.0.0.1:42424"+/>|code-block|syntax|javascript|209214|我们总是使用ASP.NET状态服务器进行开发，在许多情况下，在生产中也是如此。我发现在测试较长的用户路径时(就像具有许多表单的表单向导)，每次重新构建时都会有会话对话，这是非常恼人的。这也意味着你不会在应用重启时丢失会话。|209215|您也可以以同样的方式使用SQL+server。|209216|注意:您必须记住，如果要将类序列化为会话状态并进行更改，则需要手动重新启动状态服务器，否则将出现序列化错误。这种情况很少见，但在生产环境中需要注意。|209217|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/dd547590.aspx|1|http://www.asp.net/vnext/overview/aspnet/whats-new|2|http://www.campusmvp.net/compilationmode-avoiding-aspx-page-compilation-to-improve-scalability-in-sites-with-thousands-of-pages/^0|0|0|0|0|A|0|2N|1H|0|0|1M|1E|1|0|0|0|4|0|0|4|0|17|3K|2|0|0|0|6|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1S|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|1T|8|@$H|1U|I|1V|J|K]]|9|@]|A|$]]|$1|L|3|M|5|6|7|1W|8|@]|9|@$H|1X|I|1Y|1|1Z]]|A|$]]|$1|N|3|O|5|6|7|20|8|@]|9|@$H|21|I|22|1|23]]|A|$]]|$1|P|3|Q|5|6|7|24|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|25|8|@$H|26|I|27|J|K]]|9|@]|A|$]]|$1|T|3|U|5|6|7|28|8|@$H|29|I|2A|J|K]]|9|@]|A|$]]|$1|V|3|W|5|6|7|2B|8|@]|9|@$H|2C|I|2D|1|2E]]|A|$]]|$1|X|3|Y|5|6|7|2F|8|@]|9|@]|A|$]]|$1|Z|3|10|5|6|7|2G|8|@$H|2H|I|2I|J|K]]|9|@]|A|$]]|$1|11|3|12|5|6|7|2J|8|@]|9|@]|A|$]]|$1|13|3|14|5|15|7|2K|8|@]|9|@]|A|$16|17]]|$1|18|3|19|5|6|7|2L|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|6|7|2M|8|@]|9|@]|A|$]]|$1|1C|3|1D|5|6|7|2N|8|@]|9|@]|A|$]]|$1|1E|3|-4|5|6|7|2O|8|@]|9|@]|A|$]]]|1F|$1G|$5|1H|1I|1J|A|$1K|1L]]|1M|$5|1H|1I|1J|A|$1K|1N]]|1O|$5|1H|1I|1J|A|$1K|1P]]]]

The problem here is your application is doing a dynamic compile which means any changes to the markup files will cause the application to restart. Any application restart, as you know, will dump the InProc session.

A "Web Application" on your local template is set differently so it isn't restarting the whole application. There are advantages to having precompilation though. 

There's a couple of ways around this.

Why this is happening

ASP.NET 4.5 allows you to run "web pages" side by side with "web applications" by default. This is likely what's causing changes to an aspx to fire a precomilation (which "web pages" have to do every time there is a change).
More info here:
<a href="http://msdn.microsoft.com/en-us/library/dd547590.aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/dd547590.aspx</a>

There is also quite a few changes to optimise the web server in the new version. You can see details of those changes here and they also can explain the change when you upgrade.
<a href="http://www.asp.net/vnext/overview/aspnet/whats-new" rel="nofollow">http://www.asp.net/vnext/overview/aspnet/whats-new</a>

The solution is still the same regardless and updating single aspx files on the fly is not recommended. If it's unavoidable, then restart will have happened eventually on any setup so it's worth using one of the below solutions anyway.

Solutions

Compilation Mode

Check the CompilationMode in your web.config. For more info check out this post
<a href="http://www.campusmvp.net/compilationmode-avoiding-aspx-page-compilation-to-improve-scalability-in-sites-with-thousands-of-pages/" rel="nofollow">http://www.campusmvp.net/compilationmode-avoiding-aspx-page-compilation-to-improve-scalability-in-sites-with-thousands-of-pages/</a>

This can be set on a server level too so you can get differences by environment.

Session State Mode

You can run your session state in StateServer mode or using Sql server. The ASP.NET state server will be sitting on your server if .net is installed and just needs to be set to auto start. You can then just switch it in the config.

<pre><code>&lt;sessionState mode="StateServer" useHostingIdentity="true" cookieless="false" timeout="120" stateConnectionString="tcpip=127.0.0.1:42424" /&gt;
</code></pre>

We always run using the ASP.NET state server for development and in many cases in production.
I find when testing long user pathways (like a form wizard with many forms) it's very annoying to have session blatted every time you rebuild. That will also mean you don't lose session on app restarts.

You can also use SQL server in the same way.

NOTE: You must remember that if you are serialising classes into session state and you make changes, you will need to manually restart the state server or you'll get serialization errors. This is very rare, but just to be aware of in production environments.

blocks|key|3061435|text|我不打算为此承担责任，但答案隐藏在@Anand对原始问题的第11条评论中|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3061436|在web.config中添加此密钥：|3061437|<appSettings><add+key="PageInspector:ServerCodeMappingSupport"+value="Disabled"+/></appSettings>|code-block|syntax|javascript|3061438|这样问题就消失了。VS也变得更具响应性。唯一的缺点是你失去了来自Page+Inspector的服务器端技巧。|3061439|希望微软能很快提供解决方案..|3061440|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/users/1615515/anand^0|I|5|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|6|7|10|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|11|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|12|8|@]|9|@]|C|$]]|$1|M|3|N|5|6|7|13|8|@]|9|@]|C|$]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]]]

I'm not going to try to take the credit for this but the answer is buried in the 11th comment on the original question by @<a href="https://stackoverflow.com/users/1615515/anand">Anand</a>:

Add this key in web.config:

<pre><code>&lt;appSettings&gt;&lt;add key="PageInspector:ServerCodeMappingSupport" value="Disabled" /&gt;&lt;/appSettings&gt;
</code></pre>

and the problem goes away. VS becomes far more responsive too. Only downside is you lose the server-side trickery from Page Inspector.

Hopefully MS will provide a fix soon..

blocks|key|3061446|text|一个可能相关的问题:+IIS+(以及TFS+)在您从ASP.NET签出文件后重新启动应用程序。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3061447|我在这里找到了解决方案：http://forums.iis.net/p/1200785/2055480.aspx/1?IIS%2BExpress%2Brestarts%2Bsite%2Bwhen%2Ba%2Bfile%2Bis%2Bchecked%2Bout|3061448|导航到：%25USERPROFILE%25\AppData\Roaming\Microsoft\VisualStudio\11.0|3061449|Delete+|unordered-list-item|3061450|+app_offline.htm+file.|ordered-list-item|3061451|创建一个名为app_offline.htm|3061452|的文件夹|3061453|3061454|entityMap|0|LINK|mutability|MUTABLE|url|http://forums.iis.net/p/1200785/2055480.aspx/1?IIS%2BExpress%2Brestarts%2Bsite%2Bwhen%2Ba%2Bfile%2Bis%2Bchecked%2Bout^0|P|C|0|C|2R|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@$9|13|A|14|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|15|8|@]|D|@$9|16|A|17|1|18]]|E|$]]|$1|H|3|I|5|6|7|19|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|1A|8|@]|D|@]|E|$]]|$1|M|3|N|5|O|7|1B|8|@]|D|@]|E|$]]|$1|P|3|Q|5|O|7|1C|8|@]|D|@]|E|$]]|$1|R|3|S|5|6|7|1D|8|@]|D|@]|E|$]]|$1|T|3|-4|5|6|7|1E|8|@]|D|@]|E|$]]|$1|U|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]]|V|$W|$5|X|Y|Z|E|$10|11]]]]

One maybe related issue: IIS (as well as ASP.NET Development Server) restarts the application after you check-out a file from TFS.

I have found the solution here: <a href="http://forums.iis.net/p/1200785/2055480.aspx/1?IIS+Express+restarts+site+when+a+file+is+checked+out" rel="nofollow">http://forums.iis.net/p/1200785/2055480.aspx/1?IIS+Express+restarts+site+when+a+file+is+checked+out</a>

<ol>
<li>Navigate to: %USERPROFILE%\AppData\Roaming\Microsoft\VisualStudio\11.0</li>
<li>Delete the app_offline.htm file.</li>
<li>Create a folder named app_offline.htm</li>
</ol>

I upgraded my development machine to Windows 8 and Visual Studio 2012.

I'm testing my ASP.Net applications (also upgraded to .net 4.5) on a local IIS.

One thing that is annoying me, that hasn't been this way with my last configuration (Windows 7, VS 2010, .net 4.0), is that InProc-sessions are being restarted after changes in markup files.

Example: I'm logged into my local ASP.net application, make and save changes in a *.ascx file, refresh my webbrowser and the session is gone.

How do I turn off the session restart issue?

Edit:
I tried to repro the issue with the new VS 2012 Web Application project template, removed unnecessary content and couldn't repro this issue. 

However, in my real project the issue still remains: Changes to an aspx or ascx file result in the Application_Start event being fired. 

I also stripped down the web.config in my real project to the bare minimum to look like the one in the new project, but that didn't allow me to remove the bug either. Things I commented out in the web.config were DevExpress Controls, custom healthMonitoring, IIS UrlRewrite 2

Applicationpool as Integrated, v4.0 with NetworkService as Identity

ASP.Net Inproc session restarted after markup change in VS2012

Visual Studio

服务器

Windows

我将我的开发机器升级到了Windows 8和Visual Studio 2012。我正在本地.net上测试我的ASP.Net应用程序(也升级到IIS4.5)。令我恼火的一件事是，在我的上一次配置(Windows7，VS2010，.net 4.0)中，InProc会话在标记文件更改后重新启动。例如:我登录到我本地的ASP...

问在VS2012中更改标记后，ASP.Net Inproc会话重新启动
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在VS2012中更改标记后，ASP.Net Inproc会话重新启动EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在VS2012中更改标记后，ASP.Net Inproc会话重新启动
EN