Url: http://www.winternals.com/Faq.aspx
Url: http://www.amazon.com/gp/product/0735621411
Url: http://produkkt.abraxas-medien.de/kkrieger
I have been attempting to try out some new software from Microsoft (including Glidepath and Visual Studio Database Edition). Both of these require SQL Server Express installed. Problem is that I install a Developer Edition of SQL Server 2005 (as well as 2000) because it is more feature friendly than SQL Server Express. Why does Microsoft insist I have a third Database server? Why can't it prompt me to tell it what database to use, or at least attempt to find SQL Server 2005 as the default instance on the current machine? Just stoopid in my opinion. It's keeping me from trying out and possibly exhaulting these new interesting projects.
Url: http://www.bestweekever.tv/2006/07/07/bwe-mac-ads/
Url: http://pluralsight.com/blogs/fritz/archive/2006...
Url: http://www.gamespot.com/news/6153617.html
Url: http://www.msnbc.msn.com/id/4043608/
Url: http://www.atlantadotnet.org/
Url: http://www.gamespot.com/pc/action/dukenukemfore...
I was installing the new Google Earth when I noticed that Google is becoming Yahoo/Real/Microsoft these days. Why can't we just have options in your setups that don't try and cross-promote? Its cheap and makes me lose faith in companies.
Url: http://blogs.zdnet.com/BTL/?page_id=3170
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 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.
Url: http://wildermuth.com/viewrant.aspx?id=2053
Url: http://news.teamxbox.com/xbox/11108/Halo-3-Behi...
I have been a fan of Typed DataSets since the PDC Beta of .NET. I’ve been asked to detail my recent criticism of Table Adapters in the .NET 2.0 Typed DataSets. Here are the points that I am most concerned with:
I was having a chat with David Sceppa about TableAdapters recently when he mentioned that in the final VS 2005 bits, the TableAdapters will use timestamp fields for concurrency. I told him flatly I didn't think it worked, but I was wrong. If you create a Table in a Typed DataSet in VS 2005 and include the timestamp field in the select statement, it will use the timestamp field for concurrency. Awesome!