At 11.13am, the discussion paper was sent out to all FLC staff. That would be the time that our printer ran out of paper!

Anyway, the impact for our team is as follows:

• All developer positions are moved to a new team in ISTS.
• Only one graphic designer position (currently two)
• Only two audio/video postions (currently three)

I’m not interested in moving to ISTS, and I don’t think I’m alone there. Interesting times ahead.

Now we’re off to have a team lunch - a chance to chat and get out of the office for a little while.

Today is the day that the “Managing Change Discussion Document” is published for the Flexible Learning Centre. It’s the plan of how the University intends to change our unit, and more importantly what is happening to the positions (and by extension, the people) who currently work in this unit.

The next step is two weeks for feedback, followed by big meeting for everyone in the FLC to discuss the changes.

I don’t like the suspense of waiting, and I think everyone in the building is a bit nervous at the moment :-(

As has been pointed out elsewhere, ActiveRecord RC3 was compiled against NHibernate 1.2.

I can confirm from personal experience that it isn’t a great idea to try and swap in NHibernate 1.2.1 and assume everything will continue to function.

While it is true that you can using binding redirects to get most of the way there, dont’ forget that some tools like FxCop don’t respect these.

  <runtime\>
    <assemblyBinding xmlns\="urn:schemas-microsoft-com:asm.v1"\>
      <dependentAssembly\>
        <assemblyIdentity name\="NHibernate" publicKeyToken\="aa95f207798dfdb4" culture\="neutral" />
        <bindingRedirect oldVersion\="1.2.0.4000" newVersion\="1.2.1.4000" />
      </dependentAssembly\>
    </assemblyBinding\>
  </runtime\>

I’m listening and watching the apology to the Stolen Generations from Australia’s Prime Minister Kevin Rudd on behalf of the Australian Parliament.

I teach my children that when they’ve done the wrong thing, when they’ve hurt someone, that they should say sorry.

I think it is right and proper that this standard should also apply at the highest levels.

This is an incredibly significant day. I hope it goes some way to helping those affected directly and indirectly.

If you ever get this error from TFS, then double-check that the item you’re requesting does actually exist in the repository. I was having this problem with one of our projects, where I was asking TFS for the latest version of this item:

$/Online Services Solution Template/Main/Source

But after much investigation (including querying the TFS SQL database directly) I discovered that the correct item name was in fact:

$/Online Services Solution Templates/Main/Source

So another way to read that error message would be as “I can’t find an item with that name, are you sure you typed it correctly?”