Well, at the risk of sounding like a complete idiot, I’ve chosen to share my experience with you in order to help save you from some problems later. I needed to force an uninstall of a feature from my development machine. Well, this isn’t an stsadm command that I have had to use much, so I didn’t remember exactly what the command was. The command is “uninstallfeature", by the way. However, I was thinking that it was “uninstall”.
So, at this point I thought I’d type in “stsadm –o uninstall” and hit enter so that it would tell me what arguments I needed to include, as you can see in the below screenshot with “addsolution".

Obviously, this isn’t the best practice for how to find the arguments for an stsadm command; however, I knew that it would work if I was missing any arguments (see “Important Note” below).,
The Big Problem
Now, here is the BIG problem. Since I had the wrong command (“uninstall” instead of “uninstallfeature”), I got to enjoy a wonderful learning experience. The stsadm command “uninstall” doesn’t have to have any arguments, so if you type it in and press enter, then it will just start to run. And do you know what it does? That’s right: It uninstalls SharePoint from your machine WITHOUT asking for any confirmation. Lesson learned.
Important Note
By the way, to avoid this problem altogether you should always do what I did not do: put “–help” after any command that you wish to see the parameters for. For example: stsadm –o uninstall –help
Technorati Tags: moss,wss,feature,development,SharePoint,stsadm,uninstall,uninstallfeature
Windows Live Tags: moss,wss,feature,development,SharePoint,stsadm,uninstall,uninstallfeature