Old MC++ FAQ Feed

Some people seem to still be subscribed to my old RSS 0.91 feed for my MC++ FAQ, which was discontinued a long time ago since I moved it to RSS 2.0. For some reason, I had left lying the original xml file, which should be deleted now. Please update your...

SQL Issue Resolved!

I just managed to resolve the issue I was having with SQL Server 2000 on Windows Server 2003. Thanks go to Steve Kass (a fellow MVP), who refered me to KB Article 309398. The problem was that I had installed on my machine Certificate Server before installing SQL. Once I...

Linked from MS.COM

Found out from my referrer list that one of the pages in the Visual C++ MSDN site links to my MC++ FAQ. OK, no biggie, but I thought it was pretty cool :) </p>

SQL2K and WinServer 2003

I know it's possible to run SQL Server 2000 with Windows Server 2003, but you need a service pack. That's fine. But how the heck are you supposed to do it if SQL2K won't install so you can apply SP3 to it? I tried for a couple of hours yesterday...

Upgrading

I'm just coming back up again from upgrading my notebook (well, my only computer at home, really ) with Windows Server 2003. So far, I've got VS.NET 2002 & 2003 (but with no docs.... msdn too big for me to download!), office 2003 beta 2 and a bunch of other...

SoapExtensions per class

Someone was asking today in the ASP.NET newsgroups if there was an easy way to apply a SoapExtension to a complete WebService-derived class, instead of applying his custom SoapExtensionAttribute-derived attribute class to each and every WebMethod. I looked and, afaics, there isn't one [1], since it seems the runtime won't...

dotnetinterop.com

Mattias Sjögren, friend and fellow MVP, has created a new website dotnetinterop.com full of tips and articles on .NET interop facilities (both P/Invoke and COM Interop). If you're using either one, do yourself a favor and stop by :)

Typed Collections

"Until the next version of the .NET Framework (with generics) is released, you might think that you're stuck with framework collections that are typed for elements of type object. Which opens obvious doorways where buglets can slip through.It doesn't have to be that way - here's some basic boilerplate code...

Assembly.GetExecutingAssembly()

BradA points out the use of Assembly.GetExecutingAssembly().Location to find out the path to the executable. One thing to watch out for is that Assembly.GetExecutingAssembly() can return null under some conditions. Off the top of my head, this very likely will happen if you're not running in the default appdomain, or...

IM

Following Brad's lead, if any of you want to get in touch with me over instant messaging, I'm usually available through MSN Messenger at tomasr@passport.com :)