Paraesthesia

Looks like great stuff!

As a side note, though, you might want to check out the not-so-obvious numpad * and numpad - keys -- they do recursive expand and collapse out of the box on VS 2002 and 2003.

Hey, that's good to know... though I can get the * key to work (cool!) the numpad - only collapses the current level, not recursive. Doesn't work for the guy in the cube next to me, either (both on VS.NET 2003). Regardless, good stuff to know. Thanks!

I may integrate that, but then, on the machine that I have Visual Studio .NET installed on, it's a very rare occasion (never) when I don't want a VS.NET command prompt.

As such, I posted a registry hack to make it so every time cmd.exe runs, it'll automatically run the vsvars32.bat file.

Hope this helps.

It's great.. But why "Command Prompt Here" always opens to folder "C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE" in my VS.NET 2003"?


Help!.. Thanks in advance

Matthew

When you select "Command Prompt Here," Solvent executes:
cmd /k cd "folderpath"

(And, yes, it does put the quotes around the folder path so spaces are okay.)

If it opens to the IDE folder every time, it indicates one of a few things is happening.

One is that Solvent may be unable to determine the folder it's supposed to open to (like if you right-click on something in the Solution Explorer and Solvent can't figure out the folder). I doubt this, though, because if anything happens such that Solvent can't figure it out, you won't even see the option to open the command prompt (or "Open Containing Folder" or anything involving the current directory).

One is that you're using a project type I didn't test against, but I tested against C#, VB.NET, J#, C++, and MSI setup projects (as well as "solution items" that are not project-specific) so if you're not using one of those, you're outside my realm of supportability.

The last one, and the one I'm betting on, is that you have something else set to execute when you run your command prompt (a different "cmd /k" command set up in your registry, maybe?) and it's not allowing Solvent to execute the directory change as it'd like. You can look in the registry under "HKLM\SOFTWARE\Microsoft\Command Processor" for some of the keys that might be affecting you, but pending on your setup, it could be any other number of installed shell extensions, etc., that is causing you grief.

If you need additional assistance, I'm more than happy to talk to you outside this comment section. Please send me an email (see the bottom left-hand column near the copyright notice for an address) if you have further questions. Note that I don't think I can debug your problem remotely, and if you have any sort of non-standard setup, I can't really help you with that. I've got a lot of people successfully running this already and not a lot of time to spend on it (sorry). The most I can do is tell you what Solvent is doing and hope you can suss out what's up from there.

Matthew - Are you opening a folder on a drive other than C: ? If so, try adding a /d to the cd command:

cmd /k cd /d "folderpath"

This will tell (and allow) cd to switch to a folder on a drive other than C:.

Doh! You're totally right. I bet that's what it is. Let me hook that up and I'll put out a new version.

Yes!! I am opening a folder on driver E..
and the command:

cmd /k cd "folderpath"

works !!

Sorry.. Correction for previous message I posted:

cmd /k cd "folderpath" not work..
cmd /k cd /d "folderpath" works!.