TechEd Day 1 : Keynote speech

As we were ushered in to an imposing auditorium It seemed the three DJs and VJ were entertaining a lonely, featured HP server rack on stage. 

Having a tiny special ‘Early Bird’ section down the front did seem a little pointless when I’d hazard a guess that well over 70% of delegates would’ve been signing up for the conference straight away.

The stage was very, well, orange. The black auditorium with its glossy black camouflage ceiling makes the whole place feel like we were about to get a paintball briefing rather than a Microsoft presentation. Loud percussive beats start about 10 minutes to go to fire up the spirits. It did start to work too.

Continue reading TechEd Day 1 : Keynote speech

Is Microsoft’s future ‘delicious’?

So have you had chance to see Microsoft’s (supposed) answer to Apple’s excellent Get A Mac adverts yet?

Well in case not, I’ve included it after the break. So I get the fact its got people talking because its obtuse, I get the fact that its not tying them to advertising one product but seriously have they thought about what this advert is saying?
Continue reading Is Microsoft’s future ‘delicious’?

SourceSafe: “Only one database connection at a time is supported.”

I’ve been having intermittent problems with Visual Studio 2005 and SourceSafe 2005 occasionally complaining that “Only one database connection at a time is supported” when I load up solutions with multiple projects in them.

A Microsoft Knowledge-base article pointed me to the potential problem. Looking in the mssccprj.scc files for  both .csproj files loaded in the solution, I spotted one of them had an extra entry for a .sln file as well as the .csproj file. Both of the SCC_Aux_Path variables for the .csproj definitions were the same so the knowledge-base fix wasn’t quite correct.

Removing the definition for the .sln file from the mssccprj.scc file has helped remove this problem. Saves doing the usual suggestion of ‘SourceSafe is screwed on your machine, you should get it reinstalled’.

Having a Ballmer

“I would love to see all open source innovation happen on top of Windows”

Ballmer: All open source dev should happen on Windows | The Register

Obviously all that flapping up and down screaming “Developers, developers, developers, developers” (see after the break) has starved Steve Ballmer of critical oxygen supply to his brain of late.

He continued with his declaration that he will buy 20 web companies over the next five years. Wired reports a budget of between $50m and $1bn according to TheRegister.

“Those will be good acquisitions, and they’re important to us,” he said. “And they’re of strategic importance.”

Ballmer: I will buy 20 web companies a year | The Register
That just screams “Well you know we’ve got 10s of thousands of developers working for us, just a shame our culture isn’t providing the flexibility to allow them to come up with interesting new ideas, so we’ll just get other people’s ideas instead”.
Continue reading Having a Ballmer

Test Driven Documentation

Esendex fully embraces the idea of test-driven development (TDD), something I was introduced to during my time at Fujitsu-Siemens Computers.
Microsoft have just released a new MSDN site called the Tester Center Home. Whilst I’m sure its got some useful information on it, the matter-of-fact MSDN style doesn’t invite me to delve into it to find helpful hints and tips on TDD, personally speaking.
Continue reading Test Driven Documentation

Stored procedure error handling in SQL Server 2000

Today, we’re continuing work on our multipart message aggregation upgrade for a future Esendex release.

One part of the investigations this morning has been looking into how we manage the database access as we add parts of an incoming message to it for later processing. As we have multiple servers processing inbound messages, there was the potential for two threads trying to write to the database simultanously with different parts of the same message. Both could look at the database and think there were no existing parts of a multipart message, and decide to try and insert a new multipart message record.

During this work we found out that SQL Server 2000 will still raise an SQLException error despite error handling put in T-SQL.
Continue reading Stored procedure error handling in SQL Server 2000