To see the CLR versions currently in use on a machine you can run CLRVer -all. This will show the version being used by each process that is running.

Found a website that may be helpful: TutsBuzz 

Not sure I will use the programming side much, but the graphics side looks interesting to me. I have yet to dedicate a great deal of time to becoming good at graphics creation/editing, but, in the past, I have found tutorials like this a quick way to get up to speed.

I recently came across this tid-bit of information and thought I would document it for myself. Windows Forms controls are not thread safe. Therefore, when attempting to update a control from another thread you must take special precautions. An example of where this would be helpful would be in updating a progress bar or other UI control when running a batch process on another thread. To accomplish this, the InvokeRequired property of the control should be used along with the Invoke or BeginInvoke method. Invoke required will return True when the caller is on a different thread then the control was created on. In that case, you then need to call Invoke with a delegate that will get run on the control's thread.

I recently installed Visual Studio Team Foundation Server and I must say this was the worst install experience that I have ever had with a product. Microsoft intertwined this product with so many dependencies and made it so brittle that I am concerned that my move to team for source control was a mistake. However, I am going to give it a shot to see how it works. We are about to make the move at work (full-time job) and figure I should investigate. So far, I am not too impressed with the client. It is missing many key features and/or makes them difficult to accomplish. I'm still at the new stage so we will see how things play out.

 One word of advice for anyone who is installing team server: Read the documentation and carefully follow EVERY step for the installation. Do not deviate, even in the slightest, or you will get burned. It is ridiculous how touchy the install process is. I seriously doubt that I can afford to stay on Team System at home for my source control due to its fragility. Maybe 2008 will be better.

I recently installed Forefront Client Security on my network. I had to roll back WSUS to version 2.0 for the install to go through and then install WSUS 3.0 afterwards. Unfortunately, the Client Update for Microsoft Forefront Client Security would not automatically go down to computers until the actual client was installed manually from the DVD; it said not applicable. Maybe that is the way that it was supposed to work, but my understanding from reading the documents was that it was supposed to be the initial client install. Regardless, my network is fairly small so I just installed the client manually. Everything is up and going now and appears good to go. Hopefully it continues that way.

 I have not had anti-virus or anti-spyware on any of my computers for a very long time. For the longest time I was the only one that did much of anything on my computers and the network was secured so I was not concerned about viruses or malware. However, my wife has begun doing more work (and play) from home and she does not always know what is best when surfing the web and how to avoid being the victim of a scam/phish/virus. So here I go, off with Forefront which is a fairly new Microsoft product. Hopefully it won't make me regret it.

This site has some good tutorials for Paint Shop to enable you to create decent graphics when you aren't really a graphics person. (i.e., me).

I came across an excellent run down of the limitation of System.Gadget.Settings for those who are writing gadgets for Windows Vista. Instead of recapping the article, I will simply point to it here. The author provides a settings management class to replace the one that is used by default, allowing one to get around the maximum string length for a setting of 2048. I plan on using this class in the development of my gadgets to store JSON for settings to make the code more concise and straight forward.

Source from: RaspenJho

Imports System

Imports EnvDTE

Imports System.Diagnostics

Public Module Collapse Sub CollapseAll()

' Get the the Solution Explorer tree

Dim UIHSolutionExplorer As UIHierarchy

UIHSolutionExplorer = DTE.Windows.Item(Constants.vsext_wk_SProjectWindow).Object()

' Check if there is any open solution

If (UIHSolutionExplorer.UIHierarchyItems.Count = 0) Then

' MsgBox("Nothing to collapse. You must have an open solution.")

Return

End If

' Get the top node (the name of the solution)

Dim UIHSolutionRootNode As UIHierarchyItem

UIHSolutionRootNode = UIHSolutionExplorer.UIHierarchyItems.Item(1)

UIHSolutionRootNode.DTE.SuppressUI = True

' Collapse each project node

Dim UIHItem As UIHierarchyItem For Each UIHItem In UIHSolutionRootNode.UIHierarchyItems

'UIHItem.UIHierarchyItems.Expanded = False

If UIHItem.UIHierarchyItems.Expanded Then

Collapse(UIHItem)

End If

Next

' Select the solution node, or else when you click

' on the solution window

' scrollbar, it will synchronize the open document

' with the tree and pop

' out the corresponding node which is probably not what you want.

UIHSolutionRootNode.Select(vsUISelectionType.vsUISelectionTypeSelect)

UIHSolutionRootNode.DTE.SuppressUI = False

End Sub

Private Sub Collapse(ByVal item As UIHierarchyItem) For Each eitem As UIHierarchyItem In item.UIHierarchyItems

If eitem.UIHierarchyItems.Expanded AndAlso eitem.UIHierarchyItems.Count > 0 Then

Collapse(eitem)

End If

Next

item.UIHierarchyItems.Expanded = False

End Sub

End Module

The IISApp command is a handy tool that when run from the command line will display the process IDs for applications pools running in IIS. Very useful when you are attempting to attach a debugger to the process.

Handy tool for IE. IE7 Open Last Closed Tab is a plug-in for Internet Explorer 7 that makes "Alt-X" reopens the last closed tab. This is very useful when you accidentally close a tab that you didn't mean to close. Instead of trying to find it in your browser history, you hit "Alt-X" and it automatically reopens in a new tab. It also supports a Quick Tab Style View, shown when you hit "Alt-Q", which gives you thumbnails of the previous tabs you've closed (like the built-in IE Quick Tabs, but for previously closed tabs).

http://www.windowsmarketplace.com/details.aspx?view=info&itemid=3119163