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:
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:
Back on July 20th, Paul Therrott wrote a long blog entry explaining his experience with WGA (I stopped it from installing so I didn't try to work with it). His big problem was that WGA reported that his version was pirated. I think he (and most of us) assumed that WGA was not working correctly.
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).
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.
I've been dealing with this nasty ASP.NET Configuration Error that only happens on my dev machine for several weeks now. Inexplicably, it will think that some random DLL that is part of my project is locked while it is trying to do the aspx compilation. I finally found the solution in the MS Support Database; the solution? Disable the Indexing Service (or exclude the ASP.NET temporary files section). Arg! The problem seems to be when my build copies a copy of a .dll to the temporary files section, it would start to be indexed by the Indexing Service and was locked so that the aspx compilation couldn't overwrite it.
Bad news to all you AMD fans (yours truly included), Microsoft has announced that the upcoming Windows 2003, 64 bit edition will *not* have support for Opteron's 64 bit mode!
Bad move Microsoft. Your new mantra is supposed to be "competition is good", but this reeks of a side deal with Intel. Us, the users, want 64 bit power, but until competition helps lower costs, we can't afford it.
Ok, maybe 64 bit is supposed to be for big iron, but someone once said that 640K would be all the memory we'd ever need. What can we do to get you to change your mind MS?
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.
I've had the WinHEC build of Longhorn for a while now and I have to say I am very pleasantly surprised. It seems that Longhorn is really coming along. I am very focused on WinFS programming, so I have not had too much time to dig into other interesting topics like Avalon (though Chris Sells loves the data binding) and Indigo.
The biggest change that has effected me is the lack of VS.NET. Because of very different development schedules, there is not a version of VS.NET that works with this release of Longhorn. At first I was a bit daunted...I have become so dependent on the tools. I haven't compiled from the command-line in quite a while. Luckily, MSBuild came to the rescue. After having been using NAnt, I was unsure what the big deal with MSBuild was and why it mattered. I am now a big fan. Instead of having to learn their XML syntax, I was delighted to find out that it will build based on a csproj file. This helped me out a lot, because I know how to write those files like the back of my hand (mostly from hacking csproj's to fix annoying problems like licx files remaining after you remove a reference).
As some of you know I lost the screen on my main laptop (HP ZD8000, a lovely machine at 13 lbs) so I sent it into support where they are going to fix it but take 2 weeks to do it. I took over my old laptop from my dear Tricia to try and make it work for a while.
To simplify her world, the laptop only had XP Home on it. After getting the 3,000 things installed I needed to in order to work on my current project I am going to have to upgrade it to Professional. The problem? ASP.NET 2.0.
|Building a Web App with ASP.NET Core, MVC6, EF Core and AngularJS (New)|
|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|
|Implementing ASP.NET Web API|
|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.24628.01|
|Operating System||Microsoft Windows 6.2.9200||Runtime Arch||X86|