Development time of ASP.NET MVC application with MVVM -


we discussing team different options of web application building using asp.net mvc. 1 of options utilize mvvm everywhere on rendered views (i.e. knockoutjs). approach looks powerful, development effort considered.

i others advise based on experience (or point resource) rough "industry standard" development time comparison. example "using mvvm requires on average n times more/less effort average asp.net web app".

i find knockoutjs very quick develop with. there couple of things i've found make lots quicker.

first thing, use coffeescript rather javascript. ( using web workbench, if end using, switch using sass css). however, there no intellisense or that.... though don't issue. coffeescript lot more concise javascript , marries knockout nicely.

next thing transition of data c# json knockout.

typically here, in controller, data database (using fav orm), project c# viewmodel, , pass view ( razor ) uses , converts json maps knockout viewmodel.

if move of razor view ( controller passes parameters view ). query database , make c# view model in razor view. makes development lot faster can edit view, refresh webpage, edit, refresh ( no compile step ).

while sounds bit confusing written down, reality of doing simple, , tiny amounts of code can build pretty feature rich pages quickly.

depending on doing, i'd knockout based solutions tend 1->10 times faster. there isolated cases particular control in asp.net make thing easier, however, replicating behavior in knockout not more work, , more importantly it's way easier customize things want.


Comments

Popular posts from this blog

java - Play! framework 2.0: How to display multiple image? -

gmail - Is there any documentation for read-only access to the Google Contacts API? -

php - Controller/JToolBar not working in Joomla 2.5 -