Once again, the seemingly trivial was an incredible waste of time. While I'm documenting this here mostly for myself, it might help someone else too. The other day I was implementing a small webcontrol for one of my projects. Adding the finishing touches, I needed to add the toolbox bitmap (I hate looking at the default gears icon in my toolbox).

If you regularly (or even just occasionally) use jQuery with ASP.NET / Visual Studio 2008, you have to get the IntelliSense help for jQuery. Scott Gu's blog has all the installation information and it works great!

For quite some time, I have been meaning to get a "better" menu for DotNetNuke. I really wanted a menu based on CSS with UL, LI tags, instead of the current menu with TABLEs. I have always been struggling with the CSS for the table-based menu. Well, someone has been listening! DotNetNuke 5 has some major enhancements, which most skinners will love.

Here are a few of the open source or free software products I use fairly frequently.

This problem has plagued us since we started using GDI+ in some of our products (http://www.softelvdm.com).

The issue first appeared when we added GDI+ support for translucent images (with alpha-channel) to our DLL-based tree control for C/C++ (SftTree/DLL). During development of the release incorporating GDI+, we found that during application shutdown, the application started to "hang" forever. 

Ever since I upgraded to a Vista Ultimate x64 system with Visual Studio 2008, I had a problem simply double-clicking on a solution file (*.sln) in Windows Explorer, to open the solution in Visual Studio 2008. Instead, I had to open Visual Studio 2008, use the File, Open Solution menu command, browse to the folder with the solution file. I did this a few times before I got just a bit annoyed.

The same "people" who are now fixing it? Well, the other day I installed an AMD/ATI driver update. One of my development systems kept crashing, so I swapped the graphics card. But driver installation kept crashing and I couldn't get the driver to install.

Since 1995, my company has been selling a small printing tool used to print fixed-font, unformatted text files (like mainframe reports, listings, source code, etc.).While upgrading it for Windows x64 support, I ran across a very curious Windows API behavior, affecting the default printer retrieved using PrintDlg.

I was using a fresh copy of DNN5, creating a few simple web pages. The first time I tried to edit text, I got a "Parser Error - Could not load type Dotnetnuke.HtmlEditor.FckHtmlEditProvider.fcklinkgallery".

I'm a huge fan of DotNetNuke and couldn't wait to get my hands on version 5 once it was released. During installation, I ran into a "THREAD ABORTED" error while the SQL database is updated.