ASP.NET MVC 5 EF6 Structure -


After thinking a lot about it, we go to try ASP.NET MVC to upgrade a complex web form project. Are there. Is of Since we are new to MVC, we have a lot of suspicion.

Our project has an administrative panel or backend with more than 70 pages and then a public site where we show all the information.

1) We are going to use MVC 5 and EF6 with the first database. The way we can make all the units together without writing a single line and how we can update the model when changing the database.

We have seen how you can make CRUD operation with loft facility. In this way we save a lot of time, but is it the best way to do this?

2) We had different layers on web forms and then, at the presentation level we had an "Administrator" folder where the backend pages are in the public page root folder.

How can you manage it in MVC? Since MVC uses VIEWS how can we separate the two parts? Apart from this, similar models are used in different parts, but what about controllers?

3) Does it store the models and controllers in the best structure in their folders? We used to separate this project in different layers, but it was for the web form, we do not know how best method is in MVC, what do you think? If you are different in different projects, can you show us an example?

4) We have also used the teleracic ASP.NET red control for web forms. Those changes are great for web forms and we also have a license for MVC, but is it good to use MVC? Necessary? We have a lot of grids, where we have to do some operations, show images, buttons, upload images ... are there any other options?

Thank you for helping we are new to MVC but we hope we can learn faster because it looks amazing what you can do.

1) We are going to use MVC 5 and EF6 with the first database. The way we can make all the units together without writing a single line and how we can update the model when changing the database.

We have seen how you can make CRUD operation with loft facility. In this way we save a lot of time, but is it the best way to do this?

You do not want to use the loft facility. As if you said that you have more than 200 web pages, if so, you want to split the application into several layers with loose coupling.

2) We had different layers on web forms and then, at the presentation level we had "Admin" folder where backend pages are in the public page root folder. How do you do it in MVC Manage? Since MVC uses VIEWS how can we separate the two parts? In addition, different parts use the same model, but what about controllers?

You can use the area.

3) Is this model and controller folders the best structure? We used to separate this project in different layers, but it was for the web form, we do not know how best method is in MVC, what do you think? If you are different in different projects, can you show us an example?

See open source projects like Nomcommerce, Orchard or Umbrako.

4) Apart from this we have Tele-Formal ASP. Net Red Controls for Web Forms. Those changes are great for web forms and we also have a license for MVC, but is it good to use it in MVC? Necessary? We have a lot of grids where we have to do some operations, show images, buttons, upload images ... are there any other options?

Telescope has the Kido UI If you have DevCraft Ultimate, you can use the Candido UI Professional, which is the MVC wrapper for the Kendo UI. Basically, the cover lets you use HTML helpful instead of hand coding.

Comments

Popular posts from this blog

php - PDO bindParam() fatal error -

logging - How can I log both the Request.InputStream and Response.OutputStream traffic in my ASP.NET MVC3 Application for specific Actions? -

java - Why my included JSP file won't get processed correctly? -