CVS integration similar to http://ankhsvn.com/ would be a wonderful sample.

Copying VS options from one machine to another (ie, environmental options, debugger options, source control options, edit options, etc). This way when a new machine is built we don't have to spend the next couple days ensuring we've got the options right, which we invariably miss.

We have a little program that runs as a pre-build event to update the build version number in a couple source files -- the build number is based on the date. I wanted to be able to update the version number in a setup project as well, but could not see how to automate that, since it causes a dialog box to pop up. Is such a thing possible?

Frank Hileman,

Is there a way that little program could be shared? I am actually in the process to develop our own program that can do this but only to update the AssemblyFileVersionAttribute.

Frank - I sent your question to Craig Skibo (http://blogs.msdn.com/CraigSkibo). Here's his reply:

You could write code to select the setup project within the solution explorer. When the setup project is selected you can goto the property grid and get/set the version #. You select the item in the solution explorer by getting the UIHierarchy object with code such as this:

dim uihier as UIHierarchy = DTE.Windows.Item(Constants.vsWindowKindSolutionExplorer).Object
uihier.GetItem("Setup1\Setup1").Select(vsUISelectionTypeSelect) 'Setup1\Setup1 is SolutionName\ProjectName

Then you call off to DTE.SelectedItems.SelectionContainer.Item(1), which returns to you the IDispatch/System.Object of the item in the properties window.

Alphabetize the using statements! PLEASE!