After discovering that my development machine was getting bogged down like you wouldn’t believe, I decided that I could trim some of the processes and services down. One of the biggest offenders was Sql. I don’t need to have sql running ALL the time. So why have it start when I log in?
I first created a few batch files using the net start and net stop commands. I then created this little app that will run in the system tray and read the contents of a folder and create a context menu item for each batch file. Then when I right click the icon in the tray and choose an entry it kicks off the selected batch file giving me quick access to start and stop my processes (or run any command or shortcut for that matter).
I am cleaning up the project and I will put a good clean build up here soon.
I found this work around: http://blogs.msdn.com/astebner/archive/2008/01/13/7104519.aspx
But that wasn’t my problem. There was nothing obvious in the error log either. I did however take the advice and kick off the installer so that I could see a better error rather than trying to sift through log files. I double clicked the exe, let it do it’s thing, and no error. Weird. I got back to my Visual Studio launcher and hit install. It doesn’t indicate that the VS WAC was on of the installed components. It proceeds to “install” it. Goes through without error.
Not sure what the deal is there, but that is a pretty easy fix for the issue and it will in some cases get you going again. Which will be helpful, I can’t afford another day of down time from having to re-image my machine on Friday.
That is right, you fail.
Apparently, your ActiveX control fails to properly identify my Powerpoint 2007 installation.
