Information

  • Branch-Per-Feature Source Control. Part 2: How (Theory) – Derick Bailey continues looking at using branching for every feature in your source code control, looking in his part at how you actually implement this in theory with nice clear diagrams showing the branch and merge processes needed to make it work
  • NHibernate 2.1 Changes Overview – Patrick Smacchia runs the newly released NHibernate 2.1 through NDepend and compares it to the previous V2 release revealing the level of change involved in the creation of 2.1. Patrick also raises some concerns about the NHibernate code bas based on the NDepend metrics which Ayende responds to in his post Answering to NHibernate codebase quality criticism, where he makes the good point that code metrics are only a good indicator if the metric and the software being developed share the same principles and ideas
  • Introducing CodePaste.NET – Rick Strahl unvails his first ASP.NET MVC project. CodePaste.NET is a site for sharing snippets of code with people over social networking sites like twitter and facebook. With syntax highlighting for a number of languages and formats and comments this one looks like a useful tool
  • Business Apps Example for Silverlight 3 RTM and .NET RIA Services July Update: Part 7: ADO.NET Data Services Based Data Store – Brad Abrams fills in the gap in his series on Silverlight 3 Business Applications with part 7 which looks at using the Cloud based ADO.NET Data Services to store his data
  • Braindump on the Event Aggregator Pattern – Jeremy D. Miller shares a brain dump of his ideas on the Event Aggregator Pattern which will be forming the basis of a chapter in his book on presentation patterns
  • Simplify calling ASP.NET AJAX services from jQuery – Dave Ward looks at using the consolidation feature of JQuery’s $.ajax call to make calling ASP.NET AJAX Services easier
  • Sending mails, development machine, without actual mail server – Amr ElGarhy shares a useful tip about getting the framework to write emails to disk instead of sending them via SMTP using just config. This is a great little setting I think I will be making some use of in development lots.
  • Instantiating types with no public constructors – Kirill Osenkov looks into some details of the Activator.CreateInstance methods and looks at a technique that will allow you to create instances of types which do not have public no parameter constructors
  • Creating Games with Silverlight: A Simple Shooter – The Coding4Fun blog walks you through the creation of a simple Silverlight based in space shooting game, with code provided in C# and VB.NET. For added 1980’s computer magazine sample game feel, print the article out and copy type the source code 😉
  • Attaching SQL Server database without log file – Gunnar Peipman shows how you can manage to re-attach a SQL Server database with just having the MDF and not the LDF transaction log. Throwing away the LDF is not a good idea, however sometimes it is necessary to re-attach a database this way and this technique may come in handy in those instances
  • SOLID – L: Liskov Substitution Principle – Sebastian at Coding Efficiency has been posting a series of posts on the SOLID Principles. Now in the middle of the series taking a look at the Liskov Substitution principle, how concise and clear posts have been giving a nice overview of SOLID
  • Good Lazy and Bad Lazy – Mark Needham talks about Developer laziness and how it can be both a good thing and a bad thing
  • Don’t castrate your architecture – Ayende talks about how a traditional Web-Business-Data-Database application architecture may not be the best choice when working with NHibernate as you loose a lot of the good powerful features of NHibernate by introducing too many tier boundaries.
  • Use Code Analysis to measure the quality of sample code – Habib Heydarian shows how Visual Studio 2010 Team Systems code analysis feature can help identify problems in sample code allowing you to better judge the quality of the sample. That said, I’m of the belief that sample code should be simple and illustrate just the principles which are being demo’ed – too much validation (and other things you would have in production code) in a sample can hide the actual point of the sample.