The Morning Brew #161
Posted by Chris Alcock on Tuesday 19th August 2008 at 08:08 am | Tagged as: .NET, Development, Morning Brew
Information
- Practical Concurrency Patterns: Immutability (Freezables) – Sasha Goldshtein continues his series on concurrency with a look at immutable objects and how they really help in concurrent environments.
- Poor man’s syntax highlighting – Ayende shows how simple very basic syntax highlighting is using the rich text box control for winforms.
- The Tarantino Project – automated database migrations and more\ – Jeffrey Palermo announces the Tarantino Project, an interesting looking project which currently deals with database migrations on SQL Server, and helpers for sites deployed in web farms, with Configuration, scheduling, etc coming soon. They are also on the lookout for developers to help with Oracle Support for the database migrations.
- Using LINQ to SQL XML Mapping Files – Step by Step – Dan Wahlin looks at creating LINQ to SQLXML Mapping files by hand to allow better control over the mapping between classes and database tables
- Only In A Database Can You Get 1000% + Improvement By Changing A Few Lines Of Code – SQLDenis talks about the dramatic differences in performance that can be obtained by making queries make good use of indexes
- I’m Missing My Default Parameter Values – Mike Taulty laments the lack of optional parameters in C#
- Fluent NHibernate – Configuration – Chad Myers shows off the configuration capabilities of Fluent NHibernate. Personally I’m not really convinced that this bit is strictly necessary as the raw NHibernate way of doing this in code isn’t much longer and only tends to need to be written once in any given project, although the fluent interface does look quite shiny
- Constrained Generics and Return Values – Jason Bock talks about an how clever compilers are these days when it comes to things like evaluating the validity of statements where generics are involved.
- Why you should always unsubscribe event handlers – Davy Brion talks about one of the most common causes of memory problems caused by the Garbage collector not being able to remove object because other objects still hold references to them via event handlers.
[…] The Morning Brew #161 (Chris Alcock) […]