每个人都使用ASP.NET MVC [英] Everyone's panel with ASP.NET MVC
问题描述
我没有创建我试过的数据库，我是单独创建数据库，还是需要创建数据库？
我尝试了什么：
你好朋友......
如何使用Asp.Net MVC为每个人创建一个面板？
例如，在网站费申请中，每个家庭都可以通过登录他们的帐户在线查看他们的会费和礼宾支付。
数据库结构应该如何？
该项目是一个拥有50套公寓的项目。使用像Repository Pattern这样的模式是否有意义，或者只用一个简单的Mvc来完成它？
谢谢
I did not create the database I tried, did I create the database separately, or do I need one?
What I have tried:
Hello friends ...
How to create a panel for everybody with Asp.Net MVC?
For example, in a Site Fee application, each household will be able to view their dues, concierge payments online by logging into their account.
How should the database structure be?
The project is a project with 50 apartments. Would it make sense to use patterns like the Repository Pattern, or can it be done with just a simple Mvc?
Thank you
推荐答案
这是你的作业，在开始编码之前考虑所有选项及其优缺点是任务的一部分。
而不是想这种模式， 那种模式，或MVC;而不是我需要什么数据库？考虑项目及其需要执行的任务。考虑用户以及他需要对应用程序执行的操作，然后确定他需要如何与其进行交互，以及在何时流动和修改哪些数据。提出整个项目的大纲规范，涵盖所有这些，然后查看实施细节。
提前选择一个模式会迫使项目走上一条可能并不合适的路线 - 而且很难承认我错了并且放弃了大量的工作并重新开始一个不同的方向。所以尽量通过事先确定你需要做的事情来避免这种情况，然后找到适合的模式和结构！
This is your homework, and considering all the options together with their pros and cons before starting to code is part of the task.
Instead of thinking "this pattern", "that pattern", or "MVC"; instead of "what database do I need?" think about the project and the tasks it needs to perform. Consider a user and what he needs to do with the app, then work out how he needs to interact with it, and what data is flowing and being modified when. Come up with an outline specification for the whole project which covers all of this, and then look at implementation details afterwards.
Selecting "a pattern" in advance forces the project down a route that may not be at all suitable - and it's really hard to admit "I was wrong" and throw loads of work away and start again in a different direction. So try to avoid that by working out in advance what you need to do, and then finding pattern(s) and structures that fit!
这篇关于每个人都使用ASP.NET MVC的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
