I'm going to be at MIX 07 next week. If you want to meet, hang out, etc., leave me a comment, send me an email (programcsharp atnospam hotmail dot com), or give me a ring at (703) 868-2236.

Oh... and lets not forget the bling:

I use a laptop for a lot of my development, and for some reason, from time to time, NumLock keeps turning on when I log on. I discovered this behavior is controlled by a registry key, and I'm assuming some program tweaks it on install. Here's the info:

Key: InitialKeyboardIndicators
All Users: HKEY_USERS\.DEFAULT\Control Panel\Keyboard
Current User: HKEY_CURRENT_USER\Control Panel\Keyboard

The possible settings are as follows:

Off: 0
On: 2

The All Users key sets the NumLock state for the login screen.

Although I hate Visual SourceSafe with a passion, my current job requires it. I much prefer SourceGear Vault, and can't wait until the day I'm back on a Vault SCC system. But for now, I must use VSS. I recently had the problem of VSS integration not working in Visual Studio 2005. I found the following steps, based on reregistering the VSS MSSCCI (MS Source Code Control Interface) dll's:

In the VSS folder (usually C:\Program Files\Microsoft Visual SourceSafe\), register the following dll's:

  • ssscc.dll
  • remotevssscc.dll
  • tdnamespaceextension.dll

Using regsvr32, that would look like:

regsvr32 ssscc.dll
regsvr32 remotevssscc.dll
regsvr32 tdnamespaceextension.dll

Then open VS 2005, and go to the Tools->Options and the Source Control/Plug-in Selection page. You should now be able to select Microsoft Visual SourceSafe from the plugin dropdown.

NOTE: Source control integration is not supported in the express editions of Visual Studio.

Thanks for these instructions goes toMichael Daniel.