Early Adopter noticed a new naming convention for controls in the latest community preview of Whidbey:

Goodbye txtUserName, hello UserNameTextBox?

I find the second option to be more readable and more inline with the coding-conventions. You don't use strUserName anymore either, do you?

it was kinda to be expected, but EricGu seems to be the first to mention there will be a new release of Visual Studio 2005 (Whidbey) at Tech-Ed San Diego. Now if only that build works on the WinHec Longhorn build.

From the Chris Sells:

To set your expectations properly, WinHEC attendees and MSDN Subscribers will have access to the M7.2 OS and SDK bits, but will not have access to any matching Visual Studio bits. Neither the PDC Visual Studio installation nor the latest Visual Studio 2005 community drop nor even the upcoming Visual Studio 2005 beta will install or run properly on M7.2 Longhorn. We're hoping for future LH Milestone drops to include the matching Visual Studio bits, but this one doesn't. Luckily, MSBuild is included along with the compilers, so you can still build LH code under M7.2 like the pioneers did when they were blazing the Oregon Trail. It'll put hair on your chest and build strong bones and teeth.

That's a real shame, but I guess we'll have to do... time to renew my friendship with mr. Emacs.

[Update: the ISO is available for download now at the MSDN subscriber download site, but with a size of 733.75 MB you'll need a DVD to burn it on.]

Zeldman unveiled his 2004 spring redesign, if only he would do this blog. Any takers ?

Victor Garcia Aprea sums the changes up nicely:

• No reflection is being used – there is a new code model library. On the pros side, this basically means that the tedious file locking problems should go away. On the cons side, this means Reflector now likes to eat lots of more memory . 
• Whidbey support!! – A major hurra! for this one. All Whidbey new features are now supported (i.e. generics, etc). Plus… you can even load a Whidbey assembly with no Whidbey installed… what more do you want ugh?
• Side by side versioning: this wasn’t possible in previous Reflection versions; now you can load for example v1.0 of System.Web.dll along with v1.1 of System.Web.dll; hint: stay away from loading multiple versions of mscorlib.dll, bad things will happen if you don’t.

My favorite tool, to see how things work in the framework and solve disputes on assumptions. (Not to mention steal trade secrets )

[update: Reflector also works with the compact framework assemblies.]

[download reflector from Lutz]

Moved my blog to the final 1.6 release of dasBlog. And if this shows up on my rss-reader and the site everything seems to work.

[rss]

Thanks Andy Boyd.