I thought I'd mention a problem I had with my new Vista installation.
I have a separate partion for my data, so when I upgrade to Vista I didn't do a clean format of the entire drive, but just did a clean install of Vista. Works great!
In response to a question on MSDN, I crufted up a really simple SideBar gadget for Vista using WPF/E as the user interface. (It just shows a simple animation when first added to the bar). SideBar (and perhaps Live) Gadgets are likely to be a fun place to use WPF/E. You can download and install it here (assuming you already have WPF/E runtime installed:
Interestingly Windows Media Player 11's visualizations in Vista don't seem to be Video Hardware accellerated. While I understand that Windows Media Player 11 needs to be backwards compatible, it does make the visualizations looks ugly compared with the rest of the OS. Hopefully they'll change that for Vista RTM, but for now that are just plain ugly (and CPU hogs).
In this blog entry by James Kyton, he talks about the next versions of Windows (Fiji and Vienna...in that order). Fuji seems to be Vista 1.1 as it is adding features that were dropped. Of most interest to me is the fact that the WinFS name is rearing is head again. The article states that for Fiji:
I like this tweak guide a lot (there are other places to find this info too if you need).
If you upgrade to RC1 be aware that SQL Server 2005 requires SP2 before it will work with Vista RC1. Yeah, I know there is no SP2...but that's the case. It just doesn't work. I am trying to hack around the problem so I'll let you know if I find a solution...
I have built a test-vista machine to do some WinFX stuff on and it got me wondering...why do I need to run the WinFX runtime installation on Vista? Isn't this supposed to be pre-installed? Aren't some built-in Vista apps already using WinFX? I am so confused. Anyone know?
In this news.com article, they explore a problem I wondered about when I first saw Avalon two years ago. I am hoping that MS will make this better during optimization. I had heard that the Avalon team was hoping that battery life and mobile GPU's wouild be better when Avalon shipped. Not surprisingly, the battery life of laptops is essentially the same as it was two years ago (IMHO), though Mobile GPU's may be better.
Not really, but this is my favorite from the list:
I really like the realtime (or near real-time) preview of the windows on the Taskbar in Vista. Check it out:
I spent the majority of yesterday moving my primary laptop to Vista. I got a new 100G/7200RPM drive, so I decided to chew up some of the space with a dual boot. I got to late last night (about 6am) when I decided it was a dead proposition and I needed to revert to my XP SP2 desktop. Good news is that a majority of the software I loaded on Vista worked without a hitch. At the end of the day it came to that a few critical pieces of software weren't Vista-ready.
Getting Vista installed was a snap and with the exception of the touchpad driver, everything worked flawlessly (and after installing the XP touchpad driver I was good to go).
After my recent rant on Vista not being ready, I did want to mention a couple of great things I saw in Vista that I haven't heard about before:
I am sure I'll think of more as we go on, but so far I am looking forward to Vista's release.
I know this has been all over the blogosphere by now, but I wanted to make sure people knew about Windows Genuine Advantage being snuck into Windows Update. Here is a ZDNet article that walks through Windows Update to show how deceptive the install is. I am disappointed in Microsoft over installing this tool via Windows Update. While I don't work for Microsoft, I am a fan of what they do in general.
I was setting up my new laptop with Vista today and it looks like everything is finally installed, except my fonts. So I opened the Font folder and picked, "Add New Font". This is what I saw:
This blog post may seem to be a clever way of increasing my web traffic but the fact is that I am growing frustrated with the adoption of Vista and Microsoft's general under-delivering on Vista.
The big caveat is this: I use Vista and really like it. I don't have any real problems (no driver issues) and I find that gaming performance close enough to XP that I can't tell the difference. In addition, I like the new UX sheen of Vista...so why do I ask if its the new Windows ME?
I wasn't surprised to see thsi story on CNet as I wondered whether this would be the case as far back as 2003:
I am in between meetings near the Microsoft Campus today and wanted a coffee so I headed to a nearby Starbucks. I wanted to check my e-mail, ut I had given up my T-Mobile account (at $40/month) because there is so much free wireless in my neighborhood. I wrestled with spending $10 for a day pass just to check e-mail when I noticed that Vista users would get a free trial to T-Mobile hotspots.
After attending most of the Keynote this morning at the PDC I am convinced that Microsoft is headed in the right direction, but it is still a long way off. 2005 or 2006 is too long to plan towards. On other note, Yukon and Whidbey will be here soon. Its about time to start planning for these technologies now.
I'll blog in more detail later tonight about what these technologies mean to you.
While editing Ian Griffiths new WinFX article for ONDotnet.com, he showed me how wrong I am. I've been complaining about the hit on battery life that Longhorn will have since it will use the GPU (Video Card). Of course, Ian correctly mentioned that the high power/heat 3D computation is not needed for Longhorn, but the 2D rendering is. This eleviates all of my concerns about power and Longhorn. I am happy to be wrong...
|Using Visual Studio Code for ASP.NET Core Projects (new)|
|Building a Web App with ASP.NET Core, MVC6, EF Core and AngularJS|
|Building a Web App with ASP.NET5, MVC6, EF7, and AngularJS (Retired)|
|Best Practices in ASP.NET: Entities, Validation, and View Models|
|Front-End Web Development Quick Start|
|Lessons from Real World .NET Code Reviews|
|Node.js for .NET Developers|
|Application Name||WilderBlog||Environment Name||Production|
|Application Ver||220.127.116.11||Runtime Framework||.NETCoreApp,Version=v1.1|
|App Path||D:\home\site\wwwroot||Runtime Version||.NET Core 4.6.25211.01|
|Operating System||Microsoft Windows 6.2.9200||Runtime Arch||X86|