classic asp.net or MVC?
-
HI guys , need to discuss approach for starting a new project. our new project is something big application kind of enterprise application and may be multi database. just wanted to know which approach will be better for such application where we have lot of interconnected modules / reports / emails / invoices / (heavy data in future) / file management etc. classic asp.net or MVC. i am familiar with asp.net application and it will be easy for me at some level. MVC is good but i am not sure as have not worked on MVC. so which is the best practice for such projects. please add pros and cons of both? and if this is not a proper forum to ask this question move it to relevant ? Thanks
Ravi Khoda
-
HI guys , need to discuss approach for starting a new project. our new project is something big application kind of enterprise application and may be multi database. just wanted to know which approach will be better for such application where we have lot of interconnected modules / reports / emails / invoices / (heavy data in future) / file management etc. classic asp.net or MVC. i am familiar with asp.net application and it will be easy for me at some level. MVC is good but i am not sure as have not worked on MVC. so which is the best practice for such projects. please add pros and cons of both? and if this is not a proper forum to ask this question move it to relevant ? Thanks
Ravi Khoda
-
HI guys , need to discuss approach for starting a new project. our new project is something big application kind of enterprise application and may be multi database. just wanted to know which approach will be better for such application where we have lot of interconnected modules / reports / emails / invoices / (heavy data in future) / file management etc. classic asp.net or MVC. i am familiar with asp.net application and it will be easy for me at some level. MVC is good but i am not sure as have not worked on MVC. so which is the best practice for such projects. please add pros and cons of both? and if this is not a proper forum to ask this question move it to relevant ? Thanks
Ravi Khoda
-
That's a trick question. They're web technologies, so neither is appropriate for applications.
-
I'd suggest doing it in Silverlight but the fucking thing has be DEPRECATED!
Never underestimate the power of human stupidity RAH
-
HI guys , need to discuss approach for starting a new project. our new project is something big application kind of enterprise application and may be multi database. just wanted to know which approach will be better for such application where we have lot of interconnected modules / reports / emails / invoices / (heavy data in future) / file management etc. classic asp.net or MVC. i am familiar with asp.net application and it will be easy for me at some level. MVC is good but i am not sure as have not worked on MVC. so which is the best practice for such projects. please add pros and cons of both? and if this is not a proper forum to ask this question move it to relevant ? Thanks
Ravi Khoda
ASP.NET is easier to spell, so I'd go with that.
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
-
HI guys , need to discuss approach for starting a new project. our new project is something big application kind of enterprise application and may be multi database. just wanted to know which approach will be better for such application where we have lot of interconnected modules / reports / emails / invoices / (heavy data in future) / file management etc. classic asp.net or MVC. i am familiar with asp.net application and it will be easy for me at some level. MVC is good but i am not sure as have not worked on MVC. so which is the best practice for such projects. please add pros and cons of both? and if this is not a proper forum to ask this question move it to relevant ? Thanks
Ravi Khoda
I'd suggest MVC and Razor - get as much separation between your logic and your interface as you can, because you never know when the interface paradigm will just be changed without warning.
-
HI guys , need to discuss approach for starting a new project. our new project is something big application kind of enterprise application and may be multi database. just wanted to know which approach will be better for such application where we have lot of interconnected modules / reports / emails / invoices / (heavy data in future) / file management etc. classic asp.net or MVC. i am familiar with asp.net application and it will be easy for me at some level. MVC is good but i am not sure as have not worked on MVC. so which is the best practice for such projects. please add pros and cons of both? and if this is not a proper forum to ask this question move it to relevant ? Thanks
Ravi Khoda
Currently i am working on the project as you have described. We have developed that in MVC and Generic Repository. And this application is almost done except the changes and additional features. So as i have experienced that MVC is better for this kind of projects due to Maintenance and Constant changes and additional requirements.
Pratik Bhuva --------------- The night is darkest just before the dawn. And I promise you, the dawn is coming
-
HI guys , need to discuss approach for starting a new project. our new project is something big application kind of enterprise application and may be multi database. just wanted to know which approach will be better for such application where we have lot of interconnected modules / reports / emails / invoices / (heavy data in future) / file management etc. classic asp.net or MVC. i am familiar with asp.net application and it will be easy for me at some level. MVC is good but i am not sure as have not worked on MVC. so which is the best practice for such projects. please add pros and cons of both? and if this is not a proper forum to ask this question move it to relevant ? Thanks
Ravi Khoda
There's another item that's not on your list, which is known as 'ASP.Net Web Pages'[^]...it has all the goodness of Razor engine without all the complexity of MVC. Don't know if you could call it the successor to classic ASP.Net...maybe. It's not to be confused with 'Web Forms'. Web Pages started life with Microsoft WebMatrix but you can also develop your Web Pages sites with Visual Studio. It's meant to be a much simpler and approachable version of ASP.Net to compete with PHP...it is pretty much as easy to use...still need Windows hosting to deploy though.
-
HI guys , need to discuss approach for starting a new project. our new project is something big application kind of enterprise application and may be multi database. just wanted to know which approach will be better for such application where we have lot of interconnected modules / reports / emails / invoices / (heavy data in future) / file management etc. classic asp.net or MVC. i am familiar with asp.net application and it will be easy for me at some level. MVC is good but i am not sure as have not worked on MVC. so which is the best practice for such projects. please add pros and cons of both? and if this is not a proper forum to ask this question move it to relevant ? Thanks
Ravi Khoda
MVC is best...learn the basics first and learn on job..:thumbsup: Its better than classic ASP.Net.
-
HI guys , need to discuss approach for starting a new project. our new project is something big application kind of enterprise application and may be multi database. just wanted to know which approach will be better for such application where we have lot of interconnected modules / reports / emails / invoices / (heavy data in future) / file management etc. classic asp.net or MVC. i am familiar with asp.net application and it will be easy for me at some level. MVC is good but i am not sure as have not worked on MVC. so which is the best practice for such projects. please add pros and cons of both? and if this is not a proper forum to ask this question move it to relevant ? Thanks
Ravi Khoda
ravikhoda wrote:
classic asp.net or MVC
I would say MVC but that is because I have worked with it for the past few years. It is different than anything you have probably worked with, but it is worth learning. If you want to become a "separation of concerns" evangelist look into TDD (test driven development). It is the way to go, but I have to admit that it is hard to get used to at first. It is a different way of thinking about programming and takes some getting used to. If you can be disciplined enough to embrace this paradigm you will reap rewards when it comes to requirements changes or refinement. Try to develop under an agile framework so that you are never trying to develop the grand design all at one go. Break things down to small deliverable chunks and the new architecture will not be so overwhelming. In the end it is how comfortable you are with trying something new. If your management isn't flexible enough to allow you time to learn a new (better IMHO) technology then go with what you know and be done with it. Not as rewarding, but will keep you employed; which after all is the name of the game. Once you lose your pride, the rest is easy.
The report of my death was an exaggeration - Mark Twain
Simply Elegant Designs JimmyRopes Designs
I'm on-line therefore I am. JimmyRopes -
The web isn't suitable for applications.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
ASP.NET is easier to spell, so I'd go with that.
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
