Everyone's panel with ASP.NET MVC

Question

1.00/5 (1 vote)

See more:

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

Posted 23-Apr-18 21:13pm

Yunus Bulduk

Updated 23-Apr-18 21:42pm

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2018-04-23T21:43:00

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!