Jenn and I had the housewarming on Saturday. Started that up about 4:00p (we figured a nice afternoon/evening barbecue, get together hang out, wrap it up around 8 or so…) and closed the place down at a little after midnight when the last guests of the evening - *Jenn’s parents[i] took off.

We had about 30 people show up, and after tallying up who invited who, it turned out there were slightly more of Jenn’s friends than mine. Hmmm. Interesting, considering I put the invite out to a [i]lot* of my friends.

Of the folks invited, three who RSVP’d that they’d be there didn’t show and one of the “maybe” responses showed (actually, two, but the second one didn’t show up until the next day because he got the date wrong).

What I really found interesting was that only one of the guys from my work showed up. That was a little disappointing. Considering I spend the majority of my waking hours hanging out with these guys, I would have hoped more would show. That’s okay; it sort of indicates why Jenn and I generally don’t have parties.

The folks who did show, though, were awesome, and it was great to see each and every one of them. To the people who brought gifts, thank you very much. We already spent all but $0.68 of the Home Depot gift cards we got, and I’m drinking a very tasty cup of coffee this morning.

All in all, it was a blast. We barbecued (and still have more hamburgers and hot dogs than we know what to do with), we talked, we spilled drinks all over my hardwood floors (hehehe… at least it was the hardwoods and not the carpets, right?), we got a little loud and we generally had a great time.

Interesting social note: It was a little like a high school dance - all of my friends on one side of the house and all of Jenn’s friends on the other. I think the next party - if there is one - will probably be just one of those two groups. It’s hard to go back and forth between the two, since I feel a little like a poor host when I do: not quite paying attention to anyone there because I’m too busy floating around.

Good times.

I’m sure I’m the last person even finding this bandwagon to jump on, but this has to be the coolest thing since cool things: pInvoke.net and its associated VS.NET plugin.

Because there’s no reason to learn C++ if you don’t have to.

NOTE: Something you may be interested in is the Command Prompt Here Generator.

I got a comment on my Solvent entry about how a VS.NET command prompt would be a handy thing to have on the right-click menu.

I guess I assumed everyone developing had already fixed their default command prompt so it’s ALWAYS a VS.NET command prompt. I find I have little use for a command prompt that doensn’t have all of the VS.NET environment stuff set up on it.

For those who haven’t, and figured it’d be nice, here’s the registry hack that will automatically run the vsvars32.bat file when you get a command prompt. Note that there is a similar article out there advocating the use of the “/k” option to run the file. I don’t use that; instead, I use the “AutoRun” registry key so regardless of how you access the command prompt - even if you do a Start -> Run and type “cmd” and click OK - you’ll always get a VS.NET command prompt. (It’ll even fix it so if you have the Command Prompt Here power toy installed, that command prompt is a VS.NET command prompt, too.)

It looks like this:

Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor] "AutoRun"="\"%VS71COMNTOOLS%vsvars32.bat\""

Or you can download a text file with that already set. Rename it to have a “.reg” extension, then merge it with your registry.

Download vsnetcmd.reg

I just got sucked in to a four-hour-long meeting tomorrow.

I’m not a big meeting person. I have about a 30 minute (tops) attention span at meetings, regardless of my level of involvement in them, so after about half an hour I’m ready to check out - I’ve lost all interest in whatever topic it is and I’ll pretty much say or do whatever it takes to get out of the meeting.

On top of that, I’m a firm believer that good results are rarely achieved by meetings. Sure, there are a few good meetings that happen, but by-and-large, going to a meeting is like convening a congressional hearing - it takes forever to hear all the sides to every story, and then some arbitrary decision is made by committee that I really don’t care about.

I just don’t do well with meetings.

So I’m not too thrilled about being called into a four-hour-long meeting. I think that’s probably why I’m not in management and my career could potentially be considered “limited” - I want to focus on doing, not planning to plan the plan.

It really doesn’t help that the meeting is about the next phase of this project I just got off of that burned me out 110% on web development of any nature. I was starting to get my groove back, and I even put a couple of cool things (what I think are cool) out here for folks to download and use… I was starting to feel that desire to create cool stuff again.

There goes that. And I was just starting to enjoy myself.

I guess the best I can hope for now is to die in my sleep. Or at least not have unreasonable deadlines on the stuff I have to get done (which is, I think, the aim of the ridiculous four-hour meeting).

Solvent is a set of simple but effective tools for Visual Studio .NET 2003 packaged as an add-in. Why call it Solvent? All the tools work in the Solution Explorer.

Bad science puns aside, here’s a list of what Solvent provides:

• Recursive Expand/Contract: Ever notice when you click the +/- icon next to a folder (or double click on a Solution/Project file), it collapses that particular node in the Solution Explorer… but not any of the sub-nodes? If you have a really large project with a deep hierarchy, wouldn’t it be nice to be able to recursively close all of the items beneath a current node so when you expand it again it doesn’t re-expand everything below it? Now you can.
• Open All SubItems: Easily open all of the subitems within a containing object (folder or project).
• Open Containing Folder In Windows Explorer: Open the folder containing a document or project in Windows Explorer (if you select a folder, it opens that folder, not it’s containing folder).
• Command Prompt Here: Open a command prompt at an object’s containing folder (if you select a folder, it opens the command prompt to that folder).

Solvent adds itself to the Tools menu and to the context menu for items in the Solution Explorer.

Tools Menu:

Context Menu (On a Project):

It’s free, so come and get it!

• Download Solvent 1.1.1 (Setup - MSI)
• Download Solvent 1.1.1 (Source - ZIP)

Installation Note: Be sure to shut down Visual Studio BEFORE you install! If you don’t, you may see the UI elements of the add-in disappear. If you install the add-in and find that the UI has disappeared (and this goes for ANY add-in), go to Start -> Run and enter: devenv /setup That will reset your menus and force add-ins to rebuild. You may lose any customizations you make to the standard menu bars, though (like adding/removing buttons on bars). I’ll add a check for VS.NET on install for the next release.

NOTE: Gaston Milano has a similar product for VS 2005 called CoolCommands. As Solvent does not support VS 2005, you may be interested in checking that out.

Version History:

• 1.0.0: First public release.
• 1.1.1: Updated “Command Prompt Here” to use “cd /d [path]” rather than just “cd [path]” to allow for opening command prompt to drives other than the one VS.NET is installed on. Also released source for download.