Do I want MVC or Core?

[David]

Hello All!

 

I have a question. I am making a grid and it is going to be connected to our SQL server. It's also going to have Batch Editing as we want our Admins too be able to update just by typing in the grid and not having to hit extra buttons to do it. I have a CRUD made already through ASP.NET.  I'm sure that this will just be the start of the questions, but for now I just need 1 answered! Is it better to go with MVC or Core? 

From what I gathered, MVC is for apps on phones as well as web and Core is strictly web? Or do I have that backwards? Anyway, if you could give me some good advice with which to go about this, I would appreciate it!

[Aleksandar]

Hello David,

The decision for which technology to be used is a matter of personal preference or project requirements. With that in mind, the only thing that I could suggest is to choose the technology that you are feeling most comfortable with and that you think will best suit your workflow and project requirements. Depending on the application architecture of the application you could then use the respective suite of Kendo UI components. 

For general guidance on ASP.NET MVC and ASP.NET Core I would suggest reviewing the linked articles from Microsoft, as they provide the starting point for each of the technologies. There you will find detailed information on the pros and cons of each framework. I also believe you will find useful this summary article as it provides guidance on choosing one or the other for the application in question.

I hope you will find this information helpful.

Regards,
Aleksandar
Progress Telerik

[David]

Awesome, thank you very much for this! I'm a new JR developer, and I feel like I might of bitten off more then I could chew. Fresh out of college, and I'm tasked with this huge project. I'll definitely read up and then start from there. 

[David]

My suggestion is to consider .NET Core for all new projects.  Microsoft seems, and I stress seems,to be trying to get you out of the fat .net stack and into mobile frameworks.  Basically if its mobile oriented it should be .core oriented.

I would caution to consider your overall project however.  I have a large product that is a blend of .NET Standard, .NET Core, and .NET 4.7x.  .NET Standard has the advantage of being callable from just about everywhere.  .NET Core is used for the GUI's, and the .NET 4.7x framework code is used for those libraries I must access which have no equal in .Core or .Standard.  Things like Exchange Services, windows services, and certain 3rd party tools requires the normal .NET Framework.

Also remember that you have different version numbers 2, 2.1, 2.2, 3.1, etc. to consider in your plans to rule the world.  I sometimes think we have too many choices.....

 

[David]

I agree with you on the to many choices. Basically, I'm making a crud operations MVC app that updates our SQL database so as we can stop with the massive reprint of reports that has batch editing.Being able to write directly on the webpage is a plus. I have no deadline, but I know I don't want to take 1-2 months to do this either. My manager has stressed not using core as we do nothing mobile.  I'm just blown away as this is more knowledge to do this then I know.