I finally have my Media Center PC set up and does it rock. It blows away Tivo and ReplayTV. It's much easier to use than either of those and has all the features i'd ever want. The TV Recording is great...the music menu is awesome...and the green button makes it all easy!
I am perhaps most disgruntled about Apple's new metadata/search functionality which mirrors some of the importance of WinFS. As Joe Wilcox stated:
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.
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).
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.
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?
|Vue.js by Example (New Lower Price)|
|Bootstrap 4 by Example (New Lower Price)|
|Intro to Font Awesome 5 (Free Course)|
|Building an API with ASP.NET Core (New Course)|
|Building a Web App with ASP.NET Core, MVC6, EF Core, Bootstrap and Angular (updated for 2.2)|
|Less: Getting Started (New)|
|Using Visual Studio Code for ASP.NET Core Projects|
|Implementing ASP.NET Web API|
|Application Name||WilderBlog||Environment Name||Production|
|Application Ver||v4.0.30319||Runtime Framework||x86|
|App Path||D:\home\site\wwwroot\||Runtime Version||.NET Core 4.6.27817.01|
|Operating System||Microsoft Windows 10.0.14393||Runtime Arch||X86|