ASP.NET MVC – If only we had it 10 years ago

I realised that one of the technology or rather a group of the technologies that stops me from applying for some jobs is ASP.NET MVC + the usual JavaScript stack.

So I bought 2 books on the subject and have been playing with the technology for couple of days now. And I must say things have improved A LOT since I’ve been doing Web Development.

Back in 2003 I were working on an Order Management System and my boss being a perfectionist and a great fan of Google, requested that we created an order input form, comprised of 6 tabs without any postbacks to the server (‘coz they are evil)

All we had at our disposal was ASP.NET and JavaScript. But somehow we managed to archive what he wanted. We of course had to use some serious black magic to fetch data asynchronously (remember no AJAX back then) instead we realised we could use hidden Iframes to fetch all the required data. And the application (the order entry form) became extremely nice to use.

The traders would no longer have to remember the exact ticker, as long as they knew the name the app would asynchronously go and fetch corresponding tickers.

Once you selected a ticker, you would be presented with some information about the instrument, settlement date and the fees would automatically default based on the market where the instrument was traded on, if it was a bond it will also calculate yield, time to maturity, for convertible bonds it will show you all the greeks and much more (limits, holiday calender per market, settlement periods, compliance stuff, history of changes etc). Not only that but the could switch to a different tab effortlessly to see the executions and modify them if necessary. I’m not going to go to cover the other 95% of features, but the app was brilliant in terms of usability, only Google could complete.

MVC – Enhanced DropDownListFor – Part #2

Jeremy Lindsay

In Part #1, I described a method signature for the Html.DropDownListFor static HtmlHelper method, which was:

@Html.DropDownListFor(m => m.UserId, m => m.UserNames, m => m.Id, m => m.Name)

In this part. I’ll write more about HtmlHelper extension method code to make this work. That’s how you use it in Razor – but what does this method signature look like in the source code? Each of the lambda expressions in the above method signature is an expression which is represented by Expression<Func<T1, T2>> expr. The first parameter will represent the name of the form field rendered, i.e. what the Id and Name values are for the Html <select> element. The second parameter represents the items in the <select> list. The third parameter is the property in the items from the above list which should be rendered in the value attribute of each of the <option> elements of the <select> list. The fourth parameter is the property in the items from the above list which…

View original post 678 more words