Well, the procrastination backlog hasn’t helped me write any more posts, but I have change the priorities a bit based on previous feedback. My current procrastination backlog looks like this:
- Write a post about how to use the data contract serializer to store LINQ to SQL results in out-of-process/SQL ASP.NET session state.
- Write a post on how to host the PowerShell runtime in your own application and use it as a macro language.
- Write a rant about how the design process being separated from the development process leads to re-work and Write a post about implementing a rolling log file trace listener that works with the System.Diagnostics API.
- Write a post about creating a trace listener that creates time stamped log files like IIS.
- Write a post on how to expose application specific data via a PSProvider in PowerShell, and how to write custom Cmdlet’s.
- Write a post on how to use PowerShell to control Virtual Server 2005 to backup virtualised TFS environments.
- scheduling delays.
- Write a post on using Team Foundation Server for release management based on a slide deck I already have.
- See whether the world needs a post on how to close a NamedPipesServerStream.
- Write a rant about craftsmanship in writing code and how it impacts maintainability, specifically around the problems associated with code like this: Foo().Bar(baz.Blah().Bleh())
- Write a post about a TryCatch ASP.NET server control for coping with unreliable backends during development.
P.S. I’ve started writing the first one on the list.