4 ms·
We use Microsoft's MVC stack at work, it is wonderful, particularly combined with Entity Framework. Off the top of my head the biggest issue with using Microso
by Someone1234 12y ago
We use Microsoft's MVC stack at work, it is wonderful, particularly combined with Entity Framework.
Off the top of my head the biggest issue with using Microsoft's MVC is not within the framework itself, it is within the wider Microsoft ecosystem.
If you use MVC you now need Microsoft Servers (which cost more), maybe CALs, and you'll eventually need to pay for MSDN (for the latest Visual Studio and tooling, TS Online is wonderful however).
For us it made sense since we're in education so Microsoft gives us tons of stuff for either free or at a massive discount.
If I myself started a small business (with a limited budget) I'd likely look at something which offered a similar experience but without the dependencies (namely Ruby on Rails).
But I'd rate the MVC 5/Entity Framework 6/MS SQL setup alone very favorably. It definitely helps your productivity hugely and if done within the MVC-style will help maintainability somewhat (although you can write anything badly).
It is just the dependencies. That's really the only major downside.
PS - Speed wise it is pretty similar to compiled Java. Faster than [most] PHP (compiled or not).
PPS - If you go this route check out Stack Overflow's wonderful Miniprofiler. Great tool for SQL development (it work with anything Entity Framework can connect to including non-MS SQL servers like Oracle SQL).
- codegeek 12y agothx for your advice. really helpful. I totally understand the cost and dependency issues but i am willing to consider it as long as i can build a good scalable system. Oh and Yes, I love Visual Studio. That's one MS tool I have used heavily before and absolutely love it. The debugging features is second to none in my opinion. i will definitely check out SO's miniprofiler more. looks awesome.