In my DAL (Data Access Layer) assembly (a LINQ-to-SQL centric assembly) I used to insert object into the database like this public void CreateMessage(MyApp.Entities.Message message){  Message m = new Message(); // this is the LINQ-to-SQL generated Message class not the business entity cl

A useful custom configuration section for inline unconstrained XML.

Let's see what properties and methods the class should expose and what interfaces should be implemented.

We decided (well my boss decided :P ) that in our Silverlight app that we develop we should not waste time writing WCF services manually to interact with data. So we turned to ADO.NET Data Servics.  I created a small Web App to host the ADO.NET Data Service which exposed the Entity Framework Mode

I've recently migrated/adapted a web site built on ASP.NET 2.0 (.NET Framework 2.0) to .NET Framework 3.5. Oh the goodies of .NET Framework 3.5 : LINQ, lambdas, automatic properties and so on. At first I just set the build option to .NET Framework 3.5 : Everything fine and dandy till

I always wanted to build a class that could have some value in the real life and that could serve as an example for some (good) practices. It seems that I have the opportunity right now. In every country, mine included, there is some sort of identification number, unique for all its citizens. In

I've decided to write a class that would model a SSN-like personal identification number used in Romania. It should be useful both in production code and as a learning material for my readers. In the first part I've shown a preliminary analysys and further analysys in the second part. Va