Improve installer to register web part


Hi Tim,
My suggestion would be to have the install carry out:
stsadm -o addwppack -filename "C:\Program Files\Smiling Goat\FeedReader\smilinggoat.feedreader.cab" -globalinstall -force
In addition, it might be advantageous to spell the line out above exactly to the user to save any potential confusion.
Closed Jun 28, 2008 at 12:21 AM by timheuer


terrytalley wrote Oct 12, 2006 at 11:21 AM


I agree with Ben on this point. Being new to SharePoint, I really had a difficult time with the installer failing all because I didn't place the file path name in double quotes. On the positive side, it was a lesson learned, but on the negative side, I expected the .msi to carry all this out. Nonetheless, it works great now and I'm all the wiser. Thanks!

meadowsoft wrote Dec 21, 2006 at 4:12 PM

I too agree - after I figured out the path to the CAB file (which was not in the readme) and after I figured out the path to the stsadm executable, I hit the doublequotes issue.

Now, if the install location for either item was in a nonstandard place, this would have been of greater concern, and possibly would be more diffucult to include as part of the installer. I would just enable a checkbox in the installer to search the local machine for instances of SPS and install it automatically.



timheuer wrote Jun 28, 2008 at 12:21 AM

We are using the WSP model ging forward. The problem is in the initial beta testing we gave explicit directions as you both have stated and got the same (but opposite) feedback -- people didn't install to the default location.