blocks|key|2267481|text|Everywhere+is+different，这就是为什么。这个问题没有万能的答案。看看其他的方法，从他们那里获取任何对你的情况有用的东西。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2267482|entityMap^0|B|2|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Everywhere is different, that's why. There is no one-size-fits-all answer to this question. Look at the other approachs, and take anything that you find useful for your situation from them.

blocks|key|2267535|text|由于您要开发的是MVC应用程序，因此可以很容易地在控制器层下面编写一个DataAccess层。这将使其成为一个分层应用程序。因此，这可能是适合您架构需要的选项。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2267536|对于LinQ-SQL或实体框架问题，我只使用了实体框架。所以对Linq+to+Sql选项不是很确定。但是，当架构发生变化时，Entity+Framework会出现一些问题。当列被重命名时，生成的edmx的更新不会正确发生。因此，我所做的是在每次模式更改后删除并创建edmx，您必须手动更新那里的更改。|2267537|entityMap^0|1J|6|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

Since you are going for an MVC application, you can easily write a DataAccess layer below the Controller layer. That will make it a layered application. So this could be proper option for your architecture need.

For the LinQ-SQL or Entity Framework question, I have used only Entity frameworks. So not sure about the Linq to Sql option. But there are certain problems with Entity Framework when the schema changes. The updation of the generated edmx does not happen properly when columns are renamed etc. So what I do is delete and create the edmx after every schema change and you have to manually update the changes there.

blocks|key|859108|text|一些个人的想法和经验：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|859109|859110|使用nhibernate作为orm，或者等待EF+v4。Tekpub.com有关于使用NH的很好的教程。L2S和EF是一种黑盒:他们做了很多事情，他们有很好的文档，但他们没有可扩展性。如果你想插入一些新的功能或者改变行为，你只能用NH来实现。|unordered-list-item|859111|尽可能多地浏览v4应用程序的示例。你可以在codeplex上找到很多这样的代码。例如:+CodeCampServer，WhoCanHelpMe，Storeddd|859112|如果你正在考虑构建框架(或助手)来解决一些基础设施问题，谷歌首先会考虑；其他比你聪明的人(好吧，在我的例子中比我更聪明)很有可能已经遇到了同样的问题，他们以框架的形式写出了很好的代码(对象映射程序，验证，消息传递，...)，或者只是写了一些关于它的博客。|859113|使用锐利的架构或fubuMvc解决了大部分基础设施工作，但应用程序的其余部分取决于你的业务模型。|859114|测试驱动程序将迫使你编写良好且可维护的代码。尽可能多地使用四人帮的设计模式和可靠的原则。|859115|859116|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|R|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|S|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|T|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|U|8|@]|9|@]|A|$]]|$1|J|3|K|5|E|7|V|8|@]|9|@]|A|$]]|$1|L|3|M|5|E|7|W|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|P|$]]

Some personal thoughts and experiance: 
- use nhibernate as orm, or wait for EF v4. Tekpub.com has good tutorial on using NH. L2S and EF are kind of black box: they are doing lot of things, they have good documentation, but they don't have extendability point. If you want to plug in some new functionality or change behavior, you can do that only with NH. EF in v4 will be in state where NH was 2 or 3 years before. 
- browse as much examples of MVC apps as you can find. Lot of them you can find on codeplex. For example: CodeCampServer, WhoCanHelpMe, Storeddd 
- if you're thinking of building framework (or helper) to solve some infrastructure problems, google for it first; it's high probability that someone else smarter than you (well, smarter than me in my case) already had the same problems, and wrote nice piece of code in form of framework (object mapper, validation, messaging,...), or just blogged about it. 
- using sharp architecture or fubuMvc solves much of infrastructure work, but rest of app depends on you business model. 
- TDD will force you to write good and maintainable code. Try using Gang of Four design patterns and SOLID principles as much as you can.

blocks|key|2267642|text|您会使用Linq+to+SQL还是Entity+Framework？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2267643|如果您想访问直接映射到数据库的对象模型，那么Linq2SQL是很好的选择。例如，如果您有一个"Orders“表，Linq2SQL将创建一个"orders”对象，您可以使用该对象来访问数据。这通常是完全足够的。|2267644|当您想要创建一个可能不直接映射到数据库的对象模型时，实体框架非常有用。|2267645|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|$]]

Would you use Linq to SQL or the Entity Framework?

Linq2SQL is great if you want to access an object model that directly maps onto your database. For example, if you have an "Orders" table, Linq2SQL will create an "orders" object which you can use to access the data. This is often completely adequate.

Entity Framework is useful when you want to create an object model that might not directly map to the database.

blocks|key|2267683|text|检查此Architecture+Guide:+ASP.NET+MVC+%2B+N-tier+%2B+Entity+Framework+and+Many+More|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2267684|如果您想要使用ASP.NET+MVC，但正在努力安排事情，以便自信地用于您的下一个业务项目。这篇文章就是为你准备的。本文将指导您使用ASP.NET+MVC来构建一个小型文档管理系统。|2267685|entityMap|0|LINK|mutability|MUTABLE|url|http://www.codeproject.com/KB/aspnet/ASP_NET_MVC_WITH_EF.aspx^0|3|21|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

Check this <a href="http://www.codeproject.com/KB/aspnet/ASP_NET_MVC_WITH_EF.aspx" rel="nofollow noreferrer">Architecture Guide: ASP.NET MVC + N-tier + Entity Framework and Many More</a> 

If you want to use ASP.NET MVC but is strugling to get things arrange to confidently use for your next business project. This Article is just for you. The article guide you to use ASP.NET MVC to architect a small Document Management System.

I am still trying to figure out the right architecture for a complex ASP.NET MVC web application.

I looked in a lot of example code and everywhere it's done differently.

I would really appreciate your thoughts on this.

Another Question: Would you use Linq to SQL or the Entity Framework?

Thanks,

-Ben

Linq to SQL or the Entity Framework for Enterprise ASP.NET MVC application architecture?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我仍然在尝试为一个复杂的ASP.NET MVC应用程序找出正确的架构。我查看了大量的示例代码，发现每个地方都有不同的做法。我真的很感谢你对这件事的想法。另一个问题:您会使用Linq to SQL还是Entity Framework？谢谢,-Ben

问Linq to SQL还是Entity Framework for Enterprise ASP.NET MVC应用程序架构？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Linq to SQL还是Entity Framework for Enterprise ASP.NET MVC应用程序架构？EN