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.

Come and read and post in regards this issue at allrise.com.

There are some nice arguments there.

This is the Previewed case widget:

To all of you that are new to NHibernate or just curious about this question, the quick answer to that question is because we need members to be virtual in order to do lazy loading action.

More detailed post is here: Must Everything Be Virtual With NHibernate?

I read a nice post by Steve Blank (a recommendation by Erez Eden) that describes how to manage and balance life, family and children during hard work.

Perhaps it could work and you could find free time to raise your kids even the hard work!

Great post is here.

I had a task at work to get a web page content (using System.Net.WebRequest) in order to send the data by demand by email or in other ways.

The web page holds contents like images and more that need to be send by email in order to display the html content properly.

In order to parse the html content and look out for the images in order to download them to the server manually (a thing that will cause a lot of regex work and parsing issues), I found a great open source module (by Sharon Djabnoun, my allrise.com teammate, recommendation) that called HTML Agility Pack. “This is an agile HTML parser that builds a read/write DOM and supports plain XPATH or XSLT (you actually don't HAVE to understand XPATH nor XSLT to use it, don't worry...). It is a .NET code library that allows you to parse "out of the web" HTML files. The parser is very tolerant with "real world" malformed HTML. The object model is very similar to what proposes System.Xml, but for HTML documents (or streams).”

Now, the work on the html content will be very easy and fast – the only thing that I’ll need to do is to fine the images node, download the images to the server, set the directive of the image’s source and send the email with the attachments and the fixed URL content to point the new location of the images.

You can find it here.

After seeking the web for a good ORM mechanism in regards of developing scalable and generic DAL + BL tier (or service), I bumped into a great article that tested the EF (Entity Framework) hosted in WCF service (SOA architecture).

You can read it here. A short summary of this post says that the EF is still premature and couldn’t perform complex actions (like updating multiple tables that doing some transactions).

Performance and Scalability are also has been tested and the results weren’t so good!

So, after getting some advices from friends and colleges I think I’ll use NHibernate in order to publish my ORM relations to the DB.

Any suggestions or comments to this will be complimented to my email.