Great post in regards asp.net & Json.

I wasn’t familiar with System.Web.Script.Serialization.JavaScriptSerializer which provides serialization and deserialization functionality for AJAX-enabled applications.

While searching the web in regards this issue, I bumped into a great post that outlines the usage of this namespace.

You can check it out here.

Good Luck.

A great post that stands over the subtleties regards these two iteration possibilities here.

At the end of the day it seems that if you want to store objects of structs (primitive types such int, long etc…), in a generic List, you should use normal foreach (or for) instead if you want to avoid problems. Also removing items in the ForEach method is a thing which should be avoided also when it is possible. Otherwise i promise, the time will come when someone copies you code uses the ForEach to add items instead of removing it!

It’s almost a year I didn’t post here something, I know – I has lots of things over my head – mostly work…

As I posted here earlier, we used asp.net MVC 1.0 framework to develop the BackOffice web application of out product at work, and these days I am doing some POC regards the new MVC version (#2) that came official like 2 months ago to check out if there are some improvements to the previous version and if there’s a way to assimilate it easily.

I have to say that developing with asp.net MVC (1.0) is different than classic asp.net webforms, and mostly has benefits over it, especially the Unit testing that became very easy to write and test the controller BL actions and logic.

Until the next post regards asp.net MVC 2, I am attaching a great link that will make order to whom is new to MVC.

http://www.howmvcworks.net/Home/Topics

I will post you soon with asp.net MVC 2 post.