.Hibri

The long awaited , update to Vista was released on Tuesday. After my experienced with it, I have to say it is the most painful service pack ever from Microsoft. Remember the times when all you had to do is install the service pack, do one reboot and all is done ? well not anymore. Prepare to leave things overnight , expect it not to install, and take another hour reverting changes, and expect to have no indication of what went wrong. This was my experience while installing Vista SP1.

I downloaded the standalone install, let in install. It goes up to stage 3, and when it is 100% complete, the screen shows "Install was not successful, Reverting changes". This process goes on for about an hour and 2 reboots. The reversal is actually good, it brings back my  system to the pre- SP1 install state. After trying this since Tuesday and getting no where, I took the step of re-installing Vista.

I used the Upgrade option, as not to loose any of my settings or files. I then applied SP1 to this "fresh" installation and it worked !!.  SP1, includes all updates since the Vista release, and I think the setup process gets confused on a Vista system, that is fully patched.

Therefore, the "works-for-me-anecdotal" method to get SP1 to install, is to re-install Vista, and then apply SP1. Do not use windows update after the Vista re-install. Disable any anti-virus  and anti-spyware.

Haven't noticed any major performance improvements yet though. Though it seems a bit faster. Resume from hibernation is noticeably faster. I had issues where the system would hang when resuming. Will wait and see.

Fingers crossed....

Today, at work I was treated to a rare opportunity to attend a talk by Martin Fowler. I may or may not get the chance to hear someone who can profoundly inspire developers. with simple( sometimes obvious) nuggets of wisdom, that will make us build better software.

The talk didn't have a specific title, but centred around the theme of software design and how we go about it. His talk mostly focused on how keeping things simple can help build better software. This concept is obvious, but many of us loose sight of it.

look at what has already been done.

Similar problems have already been solved, someone out there knows how to solve it.  This is the basis of all the design patterns that have been collated by Eric Gamma et al and Martin Fowler himself.  Patterns are nothing new, they are not the future. They are practices that have been used in successful software in the past, and we can draw on the lessons learnt during the past 30 (or more)  years of software development.

spread knowledge backward

it's important that older, experienced developers pass on their knowledge to new or less experienced developers. He made an interesting point on how software architects at Thoughtworks pair up with less experienced developers. A good software architect is one who does not have to make any decisions. On a related subject Martin said "burn your architecture document". If the developers have to refer back to a document, it means that they haven't fully absorbed the architecture of the system being built, and there are gaps in their knowledge.

keep things simple, expect and prepare for change

This is what inspired me the most. Software is soft( malleable). It always changes, expect and be ready to change. Importantly be prepared to undo change. Work with what you know, and do not worry about changes that can happen. Postpone decisions till you absolutely need to make them. Organise work into incremental chunks of changes.

There is a lot more I took away from the talk. Might take a while to digest it all :). However these are concepts that are stressed in the books listed below, specially in The Pragmatic Programmer.

If you haven't read any of Martin Fowler's books, I strongly suggest you do so immediately, along with a few other books that will inspire ( and shock you) into being a better developer.

Patterns of Enterprise Application Architecture

Refactoring: Improving the Design of Existing Code

Domain-driven Design: Tackling Complexity in the Heart of Software

The Pragmatic Programmer

Kudos to Jason for organising the talk.

VS 2008 throws a COM Exception when loading a web application project. This happens when the project was made in VS 2005 and upgraded using the Upgrade Wizard. It loads web application projects made natively without a problem. There is a work around if this happens to you.

Via http://www.codeattest.com/blogs/martin/2008/01/comexception-loading-solution.html

"In order to load the Web Application Project you must make sure that the URL that the project is using, is valid and can be resolved. This can happen pretty often since when you download a project from source control for the first time, it is highly unlikely that you will have the web site already set up."

If this happens to you, the project will not load and will be grayed out in the solution explorer. Right click and edit the project, (or edit the .csproj file in notepad) look for the WebProjectProperties element. Check if the IISUrl child element points to a valid location. The server should exists, and the virtual directory should point to the same location as the web application project.