blocks|key|899768|text|根据本文，您可以自定义会话状态提供程序：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|899769|http://www.exforsys.com/tutorials/asp.net-2.0/asp.net-2.0-customizing-the-session-state-mechanism.html|offset|length|899770|这里的信息可用于设计环境感知会话状态提供程序，该提供程序可以根据.config文件中的配置或其他一些环境键选择连接字符串。|899771|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|2U|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@$D|Q|E|R|1|S]]|A|$]]|$1|F|3|G|5|6|7|T|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|C]]]]

According to this article, you can customize the session state provider:

<a href="http://www.exforsys.com/tutorials/asp.net-2.0/asp.net-2.0-customizing-the-session-state-mechanism.html" rel="nofollow">http://www.exforsys.com/tutorials/asp.net-2.0/asp.net-2.0-customizing-the-session-state-mechanism.html</a>

The information here could be used to design an environment-aware session state provider that could select the connection string based on a configuration in the .config file, or some other environmental key.

blocks|key|1114539|text|如上所述，我认为您不应该在web.config中同时拥有开发和生产连接字符串。您可以使用Web部署项目来解决这个问题。可以使用web部署项目来替换基于生成的配置设置。例如，您可以有两个名为connectionStrings.dev.config和connectionStrings.prod.config的外部配置文件。如果你在Debug中构建，它将使用dev.config，但如果你在Release中构建，它将使用prod.config。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1114540|它与VS08和VS10略有不同。下面是一些参考：|1114541|VS+2008+-+http://johnnycoder.com/blog/2010/01/07/deploy-aspnet-web-applications-with-web-deployment-projects/|offset|length|1114542|VS+2010+-+http://www.hanselman.com/blog/WebDeploymentMadeAwesomeIfYoureUsingXCopyYoureDoingItWrong.aspx|1114543|entityMap|0|LINK|mutability|MUTABLE|url|http://johnnycoder.com/blog/2010/01/07/deploy-aspnet-web-applications-with-web-deployment-projects/|1|http://www.hanselman.com/blog/WebDeploymentMadeAwesomeIfYoureUsingXCopyYoureDoingItWrong.aspx^0|0|0|A|2R|0|0|A|2L|1|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@$F|W|G|X|1|Y]]|A|$]]|$1|H|3|I|5|6|7|Z|8|@]|9|@$F|10|G|11|1|12]]|A|$]]|$1|J|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]|R|$5|M|N|O|A|$P|S]]]]

As mentioned above, I think you should not have both dev and prod connections strings in the web.config. You can use a Web Deployment Project so solve that issue. You can use a web deployment project to replace your config settings based upon the build. For instance, you could have an two external config files called connectionStrings.dev.config and connectionStrings.prod.config. If you build in Debug, it would use the dev.config, but if you build in Release, it would use prod.config.

It's a little different from VS 08 and 10. Here are some references:

VS 2008 - <a href="http://johnnycoder.com/blog/2010/01/07/deploy-aspnet-web-applications-with-web-deployment-projects/" rel="nofollow">http://johnnycoder.com/blog/2010/01/07/deploy-aspnet-web-applications-with-web-deployment-projects/</a>

VS 2010 - <a href="http://www.hanselman.com/blog/WebDeploymentMadeAwesomeIfYoureUsingXCopyYoureDoingItWrong.aspx" rel="nofollow">http://www.hanselman.com/blog/WebDeploymentMadeAwesomeIfYoureUsingXCopyYoureDoingItWrong.aspx</a>

blocks|key|899875|text|事实证明，有一种相当简单的方法可以做到这一点。会话状态提供了一种称为Partitioning的功能，您可以在该功能中将状态分散到多个SQL+Servers上。您可以提供一个根据会话id+(SID)选择SQL+Server的函数。诀窍在于，您可以在一台服务器上使用此功能，只需动态选择服务器即可。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|899876|web.config配置如下所示：|style|CODE|899877|<sessionState+mode="SQLServer"+
++++++++++++++partitionResolverType="YourNamespace.PartitionResolver"+
++++++++++++++cookieless="false"+
++++++++++++++timeout="60"+/>|code-block|syntax|javascript|899878|选择SQL+Server的函数如下所示：|899879|public+class+PartitionResolver+:+IPartitionResolver
{
++++public+void+Initialize()+{}

++++//+The+key+is+a+SID+(session+identifier)
++++public+String+ResolvePartition(Object+key)
++++{
++++++++return+<grab+your+config+here>;
++++}
}|899880|这种方法允许我们继续使用一个web.config进行生产和开发。|899881|entityMap|0|LINK|mutability|MUTABLE|url|https://web.archive.org/web/20130111000949/http://msdn.microsoft.com/en-us/magazine/cc163730.aspx^0|Y|C|0|0|0|A|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@$A|11|B|12|1|13]]|C|$]]|$1|D|3|E|5|6|7|14|8|@$A|15|B|16|F|G]]|9|@]|C|$]]|$1|H|3|I|5|J|7|17|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|18|8|@]|9|@]|C|$]]|$1|O|3|P|5|J|7|19|8|@]|9|@]|C|$K|L]]|$1|Q|3|R|5|6|7|1A|8|@]|9|@]|C|$]]|$1|S|3|-4|5|6|7|1B|8|@]|9|@]|C|$]]]|T|$U|$5|V|W|X|C|$Y|Z]]]]

As it turned out, there was a fairly easy way of doing this. Session State provides a feature called <a href="https://web.archive.org/web/20130111000949/http://msdn.microsoft.com/en-us/magazine/cc163730.aspx" rel="nofollow noreferrer">Partitioning</a>, where you can spread your state over multiple SQL Servers. You can provide a function to select the SQL Server based on the session id (SID). The trick is that you can use this feature with ONE server, just to choose the server dynamically.

The <code>web.config</code> configuration looks like:

<pre><code>&lt;sessionState mode="SQLServer" 
 partitionResolverType="YourNamespace.PartitionResolver" 
 cookieless="false" 
 timeout="60" /&gt;
</code></pre>

The function that chooses the SQL Server looks like:

<pre><code>public class PartitionResolver : IPartitionResolver
{
 public void Initialize() {}

 // The key is a SID (session identifier)
 public String ResolvePartition(Object key)
 {
 return &lt;grab your config here&gt;;
 }
}
</code></pre>

This approach allowed us to continue using one web.config for both production and development.

We have an ASP.NET web site that uses SQL Server session state. The state is configured in <code>Web.config</code> like:

<pre><code>&lt;sessionState mode="SQLServer" sqlConnectionString="data source=TheServer;
 User ID=TheUser;password=ThePassword;" cookieless="false" timeout="480"/&gt;
</code></pre>

But there are three environments (development / staging / production). All the other connection strings are configured like:

<pre><code>&lt;configuration&gt;
 &lt;connectionStrings&gt;
 &lt;add name="Development_Db1" connectionString="..."/&gt;
 &lt;add name="Production_Db1" connectionString="..."/&gt;
 &lt;/connectionStrings&gt;
&lt;/configuration&gt;
</code></pre>

At runtime, we pick one to connect to the database based on hostname. Unfortunately, the Session State connection string appears to be hard coded in <code>web.config</code>.

Is there a way to configure SQL Server session state at runtime, or make it refer to a connection string from the <code>connectionStrings</code> section?

Configure ASP.NET Session State at runtime

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我们有一个使用SQL Server会话状态的ASP.NET网站。在Web.config中，状态配置如下：<sessionState mode="SQLServer" sqlConnectionString="data source=TheServer; User ID=TheUser;password=ThePa...

问在运行时配置ASP.NET会话状态
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在运行时配置ASP.NET会话状态EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在运行时配置ASP.NET会话状态
EN