I have set up a few new PCs lately in the course of getting set up on my new job. Here is what I install:
- Windows XP SP3 – Vista too much friction
- Use BlackViper‘s Safe config
- Turn off System Restore
- Pop a shortcut to Start Menu in my SendTo folder for easy/lazy Launchy indexing)
- Set up my folder views and apply to all folders:
- Windows XP continued
- Set up Windows Classic Theme and turn off any fancy UI stuff like animations
- Windows XP continued
- Setup toolbar to locked with just the Show Desktop shortcut
- Launchy – gotta have it
- Virtual CD ROM Control Panel – mount ISOs
- SQL Server 2005 Developer
- Visual Studio 2008 Pro
- .NET 3.5 SP1
- Windows Update including IE 7 and whatever Media Player they have
- Tortoise SVN (reboot here)
- ASP.NET MVC
- Firefox 3
- Adblock Plus
- Better Gmail 2
- Delicious Bookmarks
- Foxmarks
- Split Browser
- Tab Mix Plus dev build
- Firebug
- Reflector
- CCTray
- ClearType
- Proggy Clean – font
- Foxit
- Google Talk – the only IM client that delivers searchable logs in my Gmail – required.
- Notepad++
- VisualSVN
- Testdriven.NET – map run tests to Ctrl-T
- AIR / Twhirl – to waste time
- Paint.NET
- Resharper
- Windows Live Writer
- Paste from Visual Studio (WLW plugin)
- 7-Zip
- Terminals
- Console2
- FileZilla
- wget
- Fiddler
- grep
- µTorrent
- xvid codec
Good list, the only thing I’d add is the SysInternals Suite. I keep a up-to-date copy of it on one of our network shares with a install bat that copies them down locally and makes sure the destination is in my path. SysInternals + SlickRun ( or Launchy in your case ) = Pure Power. Also VS Power Command have been making into my last machine builds lately – http://code.msdn.microsoft.com/PowerCommands
Yeah.. the only reason I didn’t list Sysinternals is http://live.sysinternals.com/ .. previously I would install them, now I just dl on demand. I will check out VS Power Command.
I noticed you didn’t have the Web Developer Toolbar for FF in your list. I highly recommend it. It’s an invaluable tool for help with things aren’t necessarily cosidered *debugging* in Firebug.
JS view is also a niced addon too, it lets you do a view source on the DOM in memory (after all scripts have run and js methods have attached to your objects) vs the default html served on initial request (before any scripted content makes it to the page). FF hasn’t been updated to work with 3.01 or 3.02 yet, so I can’t confirm whether firebug does the same thing.
Pingback: sonson
Regards for this tremendous post, I am glad I detected this internet site on yahoo.