If you do SharePoint 2007, you would know that it likes iisreset a bit more than it should. Well, truthfully you could get away with restarting only the Application Pool, but still, you gotta go to IIS Manager, and then click, click, right click, oh crap I clicked the wrong hmm .... blah !! Who wants that :-/. We're lazy right? We want instant gratification YEAH !! Well, lazy enough to read this blogpost?
So what do we do? Well, before that, let me tell ya, I've been reviewing this book for the past 4 months or so, written by Ed Hild, and Susie Adams, who are both proud Microsoft Employees. The book, is all about "Applying SharePoint 2007 & Office Technologies" - so a tad bit beyond just learning SharePoint 2007. I'll spare a full review for later, but for now I must say that it is full of nuggets. Seriously, it's like walking through a diamond mine - they are all over, take your pickin'.
Here's one that I hope they wouldn't mind my sharing with you because it was too good to hold back.
Restarting Application Pools Sucks !! Here is what helps ya -
Run @ Command Prompt
IISAPP /a <ApplicationPoolName> /r
Yup, that's it !! Not only that, if you wish to debug a particular instance of w3wp.exe, and there are 3 of them running - and you are pulling your hair because you don't know which one to attach to... ? Well take heart, you can find the appropriate process ID using the following command prompt.
IISAPP /a <ApplicationPoolName>
.. 2 productivity tips, brought to you via Malik can'tkeepmymouthsut services. Now back to your regularly scheduled programming.