I spent Thursday night with the VSCmdShell code.  Having just released v0.6 that now defaults to the VS environment paths I was determined to clean some stuff up before the next release.  I refactored the code a bunch to make it more readable, I made issuing VS commands actually work reliably by removing my hack that had been calling them through the Command Window and now just calling dte.executecommand(...) while parsing arguments, and I fixed bugs to the point where I said “Wow, I could see someone using this on a daily basis without cursing me now”.  What did I do next?  Did I upload this stable code?  Did I at least post v0.7 so users could try out a good stable build?  No...

I said “Wow, this is really cool, but wouldn't it be great if I went all out and supported intellisense and defined a settings file to store configurable options in?”.  A classic trap.  So now I'm in the middle of this transformation with a product that proves my concepts but is not yet worth using again.  Nothing is checked in yet, but I'm hoping to check some of this stuff in and release a much improved v0.7 Monday.  For now here is a preview.  The intillisense box, you should imagine, would be filled with available VS command like “File.Openfile” or directory information depending on context. (Yes, this is all running as a tool window inside VS!)