ASP MVC - recommended do's and don'ts?
I've been coding WinForms apps for years. About to embark on my first WebApp. Will most likely be using ASP MVC. The app is going to be small at first, but expand over time. This app will simply be exposing one view in an existing SQL database for read/write. Other tables will likely need to be viewed. This will be an internal company app that will only be available for Active Directory users at first. Management will likely want to expose it to users outside the company at some point, so I think I should design it it that way from the start.
- What are the recommended do's and don'ts?
- What are common pitfalls you see new ASP MVC programmers make?
- Should I use EF Core?
- What about Ninject?
- Do I need to design it differently if I want to put it in the cloud?
Thank you.
0 comments:
Post a Comment