Lukas Svoboda: Strategy, Architecture, Governance & Technology

Just came across this fascinating video at YouTube. Microsoft takes the Apple Ipod and repackages it according to current Microsoft packing conventions. The results are hilarious but do illustrate Microsoft's general tendency to overemphasize every single little product feature and cram information into it's packaging. Interesting video illustrating some points that Microsoft should consider in it's branding for for the future - especially with the whole Zune release coming soon.

"Yamazaki" or as it's better known: Windows CE 6.0 has been released to market. Windows CE 6.0 will be the base platform for the next version of Windows Mobile. Press information is here, and from Mike Hall's Blog the following is some basic info on new features:

1. Operating System architecture.
   • CE 6.0 now supports upto 32k processes with 2GB virtual memory per process (CE 5.0 supported a maximum of 32 processes with 32MB Virtual Memory per process)
   • Operating system processes moved to kernel space (GWES, Device driver manager, file system manager are all in kernel space - improves performance)
   • New Kernel mode and user mode driver model (CE 5.0 only supported user mode drivers) - kernel mode drivers for performance, user mode drivers for stability - plus you can now have multiple instances of the user mode driver manager (hey, you have upto 32k processes!)
   • Strict partitioning of user mode and kernel mode (no SetKMode!)
2. Tools - The CE 6.0 development tools are integrated with Visual Studio 2005 - this gives you one tool to configure, build, download, debug, and test the operating system and the same tool to write your native (Win32, MFC, ATL, WTL, STL) or managed (C#/VB) applications.

3. Technologies - more information on supported operating system technologies will be made available at launch.

Okay, so I could not resist posting on this. Check out www.rideme.co.nz - not only is it the worst web UI since, well since I took over support of a recent badly designed commercial website (that shall remain nameless) but it's also a case of WTF? I meant what was something thinking with a name called rideme... RIDEME of all things!

I guess the comic really does say it all!

I can across this list on pocketpcadddict.com that contains instructions on hared reseting a huge of amount of current windows/pcoket PC based devices. Very useful... I was looking for details on how to reset my (borrowed) KJAM.

Okay, so the plan once I got RC1 download was as follows:

• Install Vista RC1 x32 on a new partition on my work laptop
• Install Vista RC1 x64 on a dedicated Vista partition on my Dual Opteron home machine

I haven't looked into doing my laptop yet (more on this later when I do it), but I did install Vista x64 for my dual operton machine. Initial thoughts from a quick play:

• Simple easy installation. Much easier for joe-user than XP
• The interface is simply beautiful. The usability is massively improved over XP. I especially liked the simpler shell integration as this is something I still personally use a lot (i.e. I prefer to type c:\ as opposed to opening up windows explorer)
• No Vista x64 drivers for any of my m-audio gear. I have the audiophile 24/96 sound card and an audiosport 4x4 midi box. It meant I couldn't do any multimedia testing - I really wanted to see how well certain multimedia software worked, but I'll guess I'll have to wait.
• Big speed improvements over Vista Beta 2. It seems to run much faster on my dual operton if not fly. 

Couple of interesting notes, that Vista now longer uses boot.ini for multiboot. Instead it has a whole new mechanism which is slighty confusioning if you have a couple of other OS's already loaded on your machine. Some interesting links on how config and change the new boot configuration data can be found here and here

Well it wasn't there last night when I checked, but it Vista RC1 is now on MSDN friday morning NZ time. A full couple of days ahead of schedule! MSDN sure is gonna be slow over the next few days!!!!

Recently I've fielded a few questions from colleagues and customers on what is Unit Testing and how is it done in Visual Studio Team System. I have to say that Unit Testing has become a bit of ambiguous term in the IT industry and so the term means different things to different people. I'm in favour of Unit Testing being re-badged "Developer Testing" as this is the core essence of Unit Testing in my opinion. I.e. it's testing of code done by software developers as part of the development process. The follow set of links is further background and reading:

Unit testing defined: The short definition of unit testing | The wikipedia definition of unit test | A broader summary of unit testing | Softwaredev.com articles on testing

Visual Studio Team System Unit Testing: TheServerSide.net article on testing in VSTS and VS2005 in general | OnDotNet article covering unit testing in VS2005 including VSTS, NUnit and others | MSDN Walk through on unit testing in VSTS

This comment from the TheServerSide.net article sums it up best in my opinion:

"Jay Flowers, a lead developer at Northrop Grumman, said "One does not purchase VSTS for a unit testing framework or for a source control repository. It is purchased because it is an integrated platform to help enforce and encourage your chosen process. The main thing that VSTS offers over the other frameworks available is integration into the software development process."

I firmly believe (aside from testing aspects) Visual Studio Team System is the most cost-effective collaboration platform for Microsoft Development Teams. It may not do every aspect as perfect as some other tools, but it as fully integrated and customisable. The ability to have integrated unit testing is a major selling point of VSTS.

I joined Optimation NZ over a year ago now and since then as Managing Principal I have been focusing on building a team of Microsoft consultants in Auckland. The focus rather than being that of a development team is instead a focus on activities such Architecture/Design, Project Management, Analysis and Microsoft Product Implementation. In recognition of my efforts, I've now been awarded the additional role of National Microsoft Practice Manager, which means I horizontally oversee our Microsoft capability through Optimation's technology, software and managed services teams right across New Zealand.  

In more Microsoft release candidate madness .NET 3.0 has rearched RC status. The link is not yet posted on MSDN as far as I can see, but a quick google search reveals this Microsoft downloand link to download the RC.

Coverage of this can be found on Microsoft Watch.com and ActiveWin.

Over the weekend NZ Time, Windows Vista RC1 was finally released. Full details are on the Vista team blog. Summary details here:

It’s official — Windows Vista RC1 is done!

You’ll notice a lot of improvements since Beta 2. We’ve made some UI adjustments, added more device drivers, and enhanced performance. We’re not done yet, however — quality will continue to improve. We’ll keep plugging away on application compatibility, as well as fit and finish, until RTM. If you are an ISV, RC1 is the build you should use for certifying your application.