blocks|key|326771|text|MVC中的会话没有任何变化。GlobalApplication类在Global.asax中仍然存在。页面也存在，您可能希望引用控制器中的存储库，而不是页。向基控制器类添加属性是可以的；我总是这样做。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|326772|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|$]]

Sessions haven't changed at all in MVC. The GlobalApplication class in Global.asax still exists, too. Pages exist, also, that you would want to refer to a repository in a controller rather than a page. Adding a property to a base controller class is fine; I do it all the time.

blocks|key|326785|text|您的数据库将进入控制器的基类。这个基类应该扩展Controller，所有控制器都应该扩展这个基类。下面是一个小小的例子：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|326786|public+class+BaseController+:+Controller
{
++++private+AuthServices+_auth;
++++private+LogHelper+_log;
++++private+Repository+_repository;

++++///+<summary>
++++///+<see+cref="AuthServices"/>
++++///+</summary>
++++protected+AuthServices+Authorization
++++{
++++++++get+{+return+_auth+??+(_auth+=+new+AuthServices());+}
++++}

++++///+<summary>
++++///+<see+cref="LogHelper"/>
++++///+</summary>
++++protected+LogHelper+Log
++++{
++++++++get+{+return+_log+??+(_log+=+new+LogHelper());+}
++++}

++++///+<summary>
++++///+<see+cref="Repository"/>
++++///+</summary>
++++protected+Repository+Repository
++++{
++++++++get+{+return+_repository+??+(_repository+=+new+Repository());+}
++++}
}|code-block|syntax|javascript|326787|注意惰性实例化。它允许我在运行测试之前溜进来，并用模拟设置我的私有字段。|326788|至于会话，您的用户对象仍然可以保存在会话中，就像在传统的ASP.NET应用程序中一样。几乎所有的东西都还在(响应、缓存、会话等)，但是其中一些已经被来自System.Web.Abstractions的类包装，这样就可以对它们进行模拟以进行测试。它们的行为方式仍然相同，尽管您不应该在传统角色中使用它们中的一些(例如，不要使用Response.Redirect，返回一个执行重定向的ActionResult，如RedirectToRouteResult+)。|326789|至于你问题背后的推理..。|326790|不要强调单个db连接。取决于您的实现，这甚至可能是一个糟糕的想法，因为请求可能会相互影响。只需打开你的康奈，使用它，并处理/关闭当它完成。|326791|另外，MVC带来的最大变化之一是拒绝了传统的ASP.NET试图为web开发带来的有状态模型。所有这些框架和视图不再存在(不要注意幕后的人)。你持有的状态越少，你的web应用程序就越不复杂，越健壮。试试吧，你可能会喜欢的。|326792|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|V|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

Your database would go in a base class for your controllers. This base class should extend Controller, and all your controllers should extend the base class. Here's a little example:

<pre><code>public class BaseController : Controller
{
 private AuthServices _auth;
 private LogHelper _log;
 private Repository _repository;

 /// &lt;summary&gt;
 /// &lt;see cref="AuthServices"/&gt;
 /// &lt;/summary&gt;
 protected AuthServices Authorization
 {
 get { return _auth ?? (_auth = new AuthServices()); }
 }

 /// &lt;summary&gt;
 /// &lt;see cref="LogHelper"/&gt;
 /// &lt;/summary&gt;
 protected LogHelper Log
 {
 get { return _log ?? (_log = new LogHelper()); }
 }

 /// &lt;summary&gt;
 /// &lt;see cref="Repository"/&gt;
 /// &lt;/summary&gt;
 protected Repository Repository
 {
 get { return _repository ?? (_repository = new Repository()); }
 }
}
</code></pre>

Notice the lazy instantiation. That allows me to sneak in before running tests and set my private fields with mocks. 

As for the session, your User object can still be saved in the session just as in a traditional ASP.NET application. Almost everything is still around (Response, Cache, Session, etc), but some of them have been wrapped with classes from System.Web.Abstractions so that they can be mocked for testing. They all still behave the same way, though you shouldn't use some of them in their traditional role (e.g., don't Response.Redirect, return an ActionResult such as RedirectToRouteResult that performs your redirection).

As for the reasoning behind your questions....

Don't stress on a single db connection. Depending on your implementation it may even be a bad idea, as requests may step on each other. Just open your connex, use it, and dispose/close it when done.

Also, one of the biggest changes that MVC brings is the rejection of the stateful model that traditional ASP.NET attempted to bring to web development. All that framework and viewstate doesn't exist anymore (pay no attention to the man behind the curtain). The less state you hold onto the less complex and more robust your web application is. Try it, you might like it.

blocks|key|326850|text|如果您使用会话，我建议您有一个session类，这样您只需要在代码中指定一次字符串名称，这也会给您IntelliSence。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|326851|+public+static+class+SessionHandler
{+++
++++//+User+Values
++++private+static+string+_userID+=+"UserID";
++++private+static+string+_userRole+=+"UserRole";

++++public+static+string+UserID
++++{
++++++++get
++++++++{
++++++++++++if+(HttpContext.Current.Session[SessionHandler._userID]+==+null)
++++++++++++{+return+string.Empty;+}
++++++++++++else
++++++++++++{+return+HttpContext.Current.Session[SessionHandler._userID].ToString();+}
++++++++}
++++++++set
++++++++{+HttpContext.Current.Session[SessionHandler._userID]+=+value;+}

++++}

++++public+static+string+UserRole
++++{
++++++++get
++++++++{
++++++++++++if+(HttpContext.Current.Session[SessionHandler._userRole]+==+null)
++++++++++++{+return+string.Empty;+}
++++++++++++else
++++++++++++{+return+HttpContext.Current.Session[SessionHandler._userRole].ToString();+}
++++++++}
++++++++set
++++++++{+HttpContext.Current.Session[SessionHandler._userRole]+=+value;+}

++++}
}|code-block|syntax|javascript|326852|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

If you use sessions I would recommend having a session class, so that you only need to specify the string name once in code and this will give you IntelliSence also.

<pre><code> public static class SessionHandler
{ 
 // User Values
 private static string _userID = "UserID";
 private static string _userRole = "UserRole";

 public static string UserID
 {
 get
 {
 if (HttpContext.Current.Session[SessionHandler._userID] == null)
 { return string.Empty; }
 else
 { return HttpContext.Current.Session[SessionHandler._userID].ToString(); }
 }
 set
 { HttpContext.Current.Session[SessionHandler._userID] = value; }

 }

 public static string UserRole
 {
 get
 {
 if (HttpContext.Current.Session[SessionHandler._userRole] == null)
 { return string.Empty; }
 else
 { return HttpContext.Current.Session[SessionHandler._userRole].ToString(); }
 }
 set
 { HttpContext.Current.Session[SessionHandler._userRole] = value; }

 }
}
</code></pre>

blocks|key|139391|text|您可以创建一个模型绑定程序来封装状态。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|139392|(参见Sanderson关于他的购物车实现的mvc书)|139393|使用模型绑定器，您可以访问具有controllerContext的HttpContext。|139394|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

You can create a model binder to encapsulate state.

(See Steve Sanderson's mvc book on his shopping cart implementation)

With the model binder, you have access to the controllerContext - which has the HttpContext.

I have an application that was written in vanilla ASP.NET that I would like to port over to ASP.NET MVC.

I, however, am confused about the right place to persist objects. I need to persist for a couple reasons:

<ol>
<li>I would like all to have a single database connection, wrapped in a "repository" or "manager" style object.</li>
<li>Each user has a user object that needs to be saved on a per-session basis.</li>
</ol>

Normally, I would say that #1 would be saved as a static item in the Globals.asax that can be hit using <code>Global.Repository</code> or similar.

And I would normally say that #2 should be a property with a session backing store somewhere in the base class of the pages.

Now the reason I am confused is that I have heard that sessions have changed in MVC, and the Global.asax no longer holds the same class. Also, the concept of pages has been removed, so adding a property to the base class of a controller seems... wrong.

What say yall?

ASP.NET MVC Session vs Global vs Cache

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我有一个用普通ASP.NET编写的应用程序，我想移植到ASP.NET MVC。然而，我对持久化对象的正确位置感到困惑。我需要坚持几个理由：I希望所有用户都有一个单一数据库连接，封装在“存储库”或“管理器”样式对象中。每个用户都有一个用户对象，需要在每个会话的基础上保存。通常，我会说#1将作为静态项保存在Globals....

问ASP.NET MVC会话与Global
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ASP.NET MVC会话与GlobalEN