I’ve got some work to do this morning, but come noon, I’m off to the MIX09 conference. I don’t travel much, and rarely alone, but I do love me some Las Vegas, so I’m looking forward to it. There are a lot of folks I’m looking forward to meeting up with when I get there that I’ve corresponded with online a lot. Should be good times. I will, of course, tweetand blog the experience.
I found that being able to right-click a .sln file and open it as Administrator in Visual Studio is a huge help because I always open solutions by finding the solution file and opening from there, not opening Visual Studio first. Anyway, based on the Elevation Power Toys stuff, I write an “Elevate VS Solution” Power Toy that lets you right-click a .sln file and open it as Administrator.
Download the zip file, extract the .inf file, right-click, install. Standard disclaimers (“works on my box!”) apply.
NOTE: I’m no longer maintaining the Command Prompt Round-Up. Instead, visit the Command Prompt Here Generator.
I won’t lie - I’ve been doing most of my development up until now in Windows XP (not by choice) and as I move into Windows Server 2008 territory, there are little gotchas I’m finding as I work as a non-admin user. The one I ran into today is that our build script runs regsvr32 to register and unregister NCover during the build (so different products/projects can use different versions of NCover without having to actually install them). That’s only something an admin user can do.
The problem comes in when I right-click on a folder and choose “VS.NET
2008 CMD Prompt
Here” - it’s
running as me, not an administrator. Even if I do a
runas /user:Administrator "msbuild default.msbuild" from there it’s
not doing what I want it to because the environment’s not set up or
whatever. Point is, I needed “VS.NET 2008 Admin CMD Prompt Here” so
that’s what I made.
I updated my “Command Prompt Here”
include “VS.NET 2008 Admin CMD Prompt Here” so you can download that and
away you go. It basically just does the
before running vsvarsall.bat, but it works great from what I can tell.
Something else I found while I was searching to see if someone else had already done this - the Elevation Power Toys over on TechNet. This is a gargantuan array of scripts and installers for everything from “Command Prompt Here (as Administrator)” to “PowerShell Prompt Here (as SYSTEM)” and more. It’s well worth the time to check out - enough so that I’m not replicating all of that in my own roundup. Go ahead and grab those Power Toys. You’ll be glad you did.
I’ve been working on a few projects lately that have a very time-sensitive aspect to them. That time-sensitivity is accompanied by an overly-short planning cycle, so things are being handled in a more “reactive” manner than I like. I’m a “proactive” person, I like a good plan (though it doesn’t have to be a 500 page doorstop, a plan is a good thing).
Every time one of these “reactive” projects gets going, these included, I always re-discover the importance of keeping a cool head. Rather than lighting your hair on fire to run around with the rest of the folks, stop for a second. Step back, assess the situation, and take your time in solving the problem. Don’t waste time, but take enough time to consider all of the angles of the problem in the context of your proposed solution.
When executing on a solution, work fast, but don’t work quick. The difference is important - fast work will get you done while respecting the time-sensitivity; quick work will find you cutting corners and making errors that you wouldn’t normally make.
That’s the crux of this one - take enough time so you’re not making those stupid mistakes that you wouldn’t otherwise make in a less time-critical project. We all know what happens when you do make those mistakes, right? In software, the solution will get sent back from QA (or doc, or - worse - the customer) as insufficient, incomplete, or incorrect. That’s bad news that will actually put you further behind schedule than had you not cut those corners, not made those mistakes.
One of the positive side effects of keeping a cool head in solving the problem is that it’ll reduce some of the stress you might be prone to due to things being “out of control,” which, in turn, will ease some of the interpersonal communication issues that inevitably arise in these situations.
I think it’s time for me to put the fire in my hair out, step back, take a breath, and solve some problems.
This is my first post on the upgraded blog using Subtext 220.127.116.11. After a failed upgrade, I ran through an upgrade on a full staging environment, got it working, and repeated the process in production… huh, I guess that’s sort of what you’re supposed to do, anyway, isn’t it?
I won’t lie; my heart was pounding near out of my chest while I was doing the upgrade, scared I’d have to call upon my web host to restore me from a backup (I don’t have admin access so I can’t do it myself).
If you see soemthing wrong with the site, leave me a comment or contact me (see the link in the navigation bar) so I can see about fixing it.