June 2006 - Posts
My Xbox 360 apparently has a blog.
-CP
It has been four days and I still not entirely convinced this is a good idea. However, BradA makes good argument in that the reduction of confusion comes from stating what applications require and not what assemblies make up a specific version of the framework. For example, architects would simply state that their application requires .NET 3.0 or .NET 2.0. Sounds simple and elegant, so you can’t blame Microsoft for going down this path. But why couldn’t we have said that applications require WinFX, .NET 2.0, .NET 1.1, or .NET 1.0? Or even WinFX 3.0 or WinFX 2006? To me WinFX (Windows Framework) says it all in a nice clean name that also looks nice in a file path… too bad.
-CP
Most of my Vista Beta 2 issues revolve around network connectivity.
- My T-Mobile EDGE/GPRS card doesn’t work even though Vista installs the appropriate Broadcom GC89 driver.
- T-Mobile Hotspot doesn’t work.
- Many hotel Internet system don’t work. I can get a few working if I use Firefox and I know which site I’m supposed to be redirected to. For instance in several Marriott location I know I need to eventually get to https://login.globalsuite.net
- The whole Network List idea is nice, but needs a usability redesign.
- Outlook 2007 Exchange access is painfully slow. I’ve done the proper console commands and still get less than ideal performance.
-CP
I personally think this naming change is a mess and will create complete confusion in the industry. This is stupid, stupid, stupid! When I get calmed down perhaps I will put together some more complete thoughts on the subject. However, I already hear customers asking these questions:
- Do we need to certify .NET 3.0 as a corporate standard after it took 6 months to certify .NET 2.0?
- Does .NET 3.0 include version upgrade of all components? ASP.NET 3.0? CLR 3.0?
- So, you are saying .NET 3.0 is .NET 2.0 with just some more assemblies?
- So, you are saying we can expect LINQ with Vista?
- Hmmm… what happened to WinFx or Avalon or Indigo?
- CardSpace?
Reduce confusion… jeez. My personal thought would have been to release separately as WinFX and then incorporate when the real .NET 3.0 was released. It doesn’t seem that hard or complicated.
-CP
I'm filled with mixed emotions. I've decided to leave Avanade and pursue other opportunities. On one hand, I am sad to leave what I think is a organization with great potential. On the other hand, I am very excited about my next move and spending more time with the family. They certainly deserve it.
(Just so we are clear, the title of this post was inspired by Tina)
-CP