MOSS MVP

I've moved my blog to http://blog.falchionconsulting.com!. Please update your links. This blog is no longer in use--you can find all posts and comments at my new blog; I will no longer be posting to this site and comments have been disabled.

Friday, February 6, 2009

Downloads

I’ve decided to rework a few things and consolidate some of my downloads into a single posting which I’ll keep updating as I offer up new products.  The first notable change is that there is now only one download for the STSADM and PowerShell source code.  Also, the previous files (stsadm.zip and spposh.zip) have been deleted so if you were linking directly to these files (something I’d prefer people not do) please adjust your links to point to this download page (I may periodically change the download file name to keep people from linking directly to the downloads).  The second thing you should notice is that I now have an x64 build of the PowerShell cmdlets – the core assemblies are compiled to “Any CPU” so the only real change is that the MSI has had it’s target platform changed and I had to manipulate the MSI, post build, so that it would use the x64 version of the InstallUtilLib.dll (see Mark Jones’ post on how to do this).

You can get to the index of all my STSADM commands and PowerShell cmdlets here.

STSADM/Cmdlets Source Code
Download SourceSharePoint 2007 STSADM Extensions and PowerShell Cmdlets Source Code
The source code contains four projects and requires Visual Studio 2008:
  • Lapointe.SharePoint.STSADM.Commands
  • Lapointe.SharePoint.PowerShell.Commands
  • Lapointe.SharePoint.PowerShell.Commands.Setup
  • Lapointe.SharePoint.PowerShell.Commands.Setup64
Download SourceSharePoint 2010 STSADM Extensions and PowerShell Cmdlets Source Code
The source code contains one project and requires Visual Studio 2010:
  • Lapointe.SharePoint2010.Automation
SharePoint 2010 STSADM Commands and PowerShell Cmdlets WSP Files
SharePoint 2010 Server Cmdlets (x86, x64)
To install for the first time run the following commands (make sure you are in the directory where you downloaded the file):
  1. Add-SPSolution Lapointe.SharePoint2010.Automation.wsp
  2. Install-SPSolution -Identity Lapointe.SharePoint2010.Automation.wsp -GACDeployment
To upgrade if previously installed run the following commands (make sure you are in the directory where you downloaded the file):
  1. Update-SPSolution -LiteralPath Lapointe.SharePoint2010.Automation.wsp -Identity Lapointe.SharePoint2010.Automation.wsp -GACDeployment
SharePoint 2010 Foundation Only Cmdlets (x86, x64)
To install for the first time run the following commands (make sure you are in the directory where you downloaded the file):
  1. Add-SPSolution Lapointe.SharePoint2010.Automation.wsp
  2. Install-SPSolution -Identity Lapointe.SharePoint2010.Automation.Foundation.wsp -GACDeployment
To upgrade if previously installed run the following commands (make sure you are in the directory where you downloaded the file):
  1. Update-SPSolution -LiteralPath Lapointe.SharePoint2010.Automation.Foundation.wsp -Identity Lapointe.SharePoint2010.Automation.wsp -GACDeployment
SharePoint 2007 STSADM Extension WSP Files (SP2 is Recommended)
MOSS Only STSADM Extensions (x86, x64)
To install for the first time run the following commands (make sure you are in the directory where you downloaded the file):
  1. stsadm -o addsolution -filename Lapointe.SharePoint.STSADM.Commands.wsp
  2. stsadm -o deploysolution -name Lapointe.SharePoint.STSADM.Commands.wsp -immediate -allowgacdeployment
  3. stsadm -o execadmsvcjobs
To upgrade if previously installed run the following commands (make sure you are in the directory where you downloaded the file):
  1. stsadm -o upgradesolution -filename Lapointe.SharePoint.STSADM.Commands.wsp -name Lapointe.SharePoint.STSADM.Commands.wsp -immediate -allowgacdeployment
  2. stsadm -o execadmsvcjobs
WSS Only STSADM Extensions (x86, x64)
To install for the first time run the following commands (make sure you are in the directory where you downloaded the file):
  1. stsadm -o addsolution -filename Lapointe.SharePoint.STSADM.Commands.WSS.wsp
  2. stsadm -o deploysolution -name Lapointe.SharePoint.STSADM.Commands.WSS.wsp -immediate -allowgacdeployment
  3. stsadm -o execadmsvcjobs
To upgrade if previously installed run the following commands (make sure you are in the directory where you downloaded the file):
  1. stsadm -o upgradesolution -filename Lapointe.SharePoint.STSADM.Commands.WSS.wsp -name Lapointe.SharePoint.STSADM.Commands.WSS.wsp -immediate -allowgacdeployment
  2. stsadm -o execadmsvcjobs
SharePoint 2007 PowerShell Cmdlet Installers
Sample SharePoint 2007 Scripts
CodePlex / Demo Projects
Go to CodePlex projectWeb Part Page History (SharePoint 2007) 
SharePoint 2007 has made great improvements over previous versions in the handling of item versioning. However, many have noticed that web part pages did not benefit from the versioning changes. While page fields and associated meta data is properly versioned, web part changes are not. This is true of publishing pages as well as standard web part pages within a document library. The purpose of this project is to capture these changes and allow a seamless integration with the out of the box restore mechanisms.
Go to CodePlex projectCustom SharePoint STSADM Commands Template (SharePoint 2007) 
A simple template Visual Studio project that can be used as a starting place for creating your own custom SharePoint 2007 STSADM extensions. The project includes utilities and classes to help declare and work with parameters as well as build a WSP solution to deploy your new extensions.
Download projectCustom Site Collection Creation Page (SharePoint 2007) 
A complete custom site collection provisioning application with source code and deployable WSP package. More information can be found here: http://stsadm.blogspot.com/2009/07/custom-sharepoint-2007-site-collection.html
Presentations
Download PowerPointVariations and the MUI in SharePoint 2010
I presented this at the June Colorado Springs SharePoint User Group Meeting and will be doing it again at the October 2010 SPTechCon Event in Boston.
Download PowerPointPowerShell with SharePoint 2010
I've presented this deck at several events including SharePoint Saturday Denver and Atlanta as well as TEC2010. The PowerShell demo code I used can be found in the notes section of the first slide.
Download PowerPointUpgrading to SharePoint 2010
I recently presented this deck at the Colorado Springs SharePoint User Group Meeting and did a trimmed down version of it for a live webcast in March. There's also a recording of the demo (~21MB) which I used during the presentation (the recording does not contain any audio but will help you see what the upgrade experience looks like).
Download PowerPointUsing Content Types to Improve Discoverability (SharePoint 2007)
I presented this deck at the Best Practices Conference in February of 2009. The content is specific to SharePoint 2007 (lots has changed with 2010).
Download PowerPointSub-site or Site Collection: Best Practice Approaches, Considerations, and Lessons Learned (SharePoint 2007)
I presented this deck at the Best Practices Conference in February of 2009. The content is specific to SharePoint 2007 (not a lot has changed with 2010 but there are new considerations).

Use of any downloads is at your own risk. Gary Lapointe cannot be held liable for any damage done to your environment.

You may not repackage or sell any of the downloads or associated source code. Downloading implies that you acknowledge these restrictions.

71 comments:

nunya said...

When I try to install the STSADM extensions, I get an error:

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or ass
embly 'Microsoft.SharePoint, Version=11.0.0.0, Culture=neutral, PublicKeyToken=7
1e9bce111e9429c' or one of its dependencies. The system cannot find the file spe
cified.
File name: 'Microsoft.SharePoint, Version=11.0.0.0, Culture=neutral, PublicKeyTo
ken=71e9bce111e9429c'
at Microsoft.SharePoint.StsAdmin.SPStsAdmin.Main(String[] args)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\M
icrosoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure lo
gging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fus
ion!EnableLog].

Now, I know that it should be referencing version 12. Am I doing something wrong

Gary Lapointe said...

Well that's a new one - I honestly don't know what's up with that (my stuff is obviously built to the 12.* dlls and not the 11.* dlls.

Mark Jones said...

Hi Gary

You have popped a link to my 64 bit MSI blog posting. However, I have now moved my blog so the post is now here : http://www.collaboris.co.uk/blogs/mark/09-04-21/Building_an_MSI_in_Visual_Studio_2005_2008_to_work_on_a_SharePoint_64_bit_installation_with_a_Custom_Action.aspx

Cheers
Mark

Gary Lapointe said...

Thanks Mark!

Vinny Tang said...

I'm trying to install the powershell and I'm getting an error Error 1001 Unable to get installer types in the c:\program files\Gary Lapointe\PowerShell Commands for Sharepoint. PowerShell.Commands.dll assembly -> Unable to load one or more of the rquested types. Retrieve the LoaderExceptions property for more information. Any ideas?

Gary Lapointe said...

Make sure you have PowerShell 1.0 installed and that you downloaded the right version for your environment (x86 or x64).

Jin said...

Hi Gary,

I have downloaded the STSADM Commands template to create my own operations. It was working fine until recently that my team wants to sign the assembly with another key with password protected. (Default used: key.snk)

When I build the program and tries to list down the operation in the Command Prompt, I received an error.

Unhandled Exception: System.ArgumentNullException: Value cannot be null.

What should I do to change the key file?

- Jin

Gary Lapointe said...

If you change the key then you need to update the xml files with the new public key token.

Jin said...

Thanks Gary... I got it. =)
- Jin

Anonymous said...

Do I need Powershell installed to run the commands. I downloaded the Moss only .wsp and tried running the first command as per instructions in the same directory. Gets the 'stsamd is not recognized error'.
am i missing anything

Gary Lapointe said...

You don't need powershell for stsadm. You just need navigate to the 12 hive's bin folder and run from there (or add that path to the path environment variable).

Ron said...

When I try to install the STSADM extensions for MOSS, I get:
"Object reference not set to an instance of an object."
During the addsolution step. Any advice?

Gary Lapointe said...

Make sure you are running as a farm admin.

Ron said...

Thanks.

hbkrules69 said...

Is there a way to use your commands to set or create a new site collection role? Example: I have been asked to create a new role called "Author" and grant all permissions except Create subsites. This is not a web app policy but rather created under each site colleciton, of which we have over 50 :(

Gary Lapointe said...

Unfortunately I don't have any commands that support this directly. You could do using PowerShell though.

Anonymous said...

Great set of tools. They saved me a bunch of time and hassle migrating from WSS 3.0 to MOSS 2007.

Anonymous said...

Bringing Site Columns for document metadata from 2003 to Moss....not sure how. Any ides or canned material?

Harry Rosario said...

I installed the MOSS commands withoout a problem. However when i install the WSS commands I get the following error:
A solution with the same name "lapointe.sharepoint.stsadm.commands.wsp" or id "
2625fbe6-4884-4666-a1ae-6b06f0db8a6f" already exists in the solution store.
Lapointe.SharePoint.STSADM.Commands.WSS.wsp: The Solution installation failed.

Gary Lapointe said...

You only need the one matching your environment - not both.

MOSS_Dev said...

Hi Gary
I have 5 different master pages which needs to be applied to the site on daily basis. I dont have powershell and would like to make a .bat file and use windows scheduler to apply the masterpage. How can I go about this?? Thanks..

Gary Lapointe said...

You can use my gl-setmasterpage command but honestly your requirement seems a bit odd - why do you need to reapply your masterpage every night?

MOSS_Dev said...

We have got 5 masterpages with different color schemes so need to apply different color on different day... So would like to do it automatically.... I tried what you explained in your blog... but getting an error on these lines:

"parameters.Add(new SPParam("url", "url", true, null, new SPUrlValidator(), "Please specify the web url.")); 23: parameters.Add(new SPParam("sitemaster", "sitemp", false, null, new SPNonEmptyValidator())); 24: parameters.Add(new SPParam("systemmaster", "sysmp", false, null, new SPNonEmptyValidator())); 25: parameters.Add(new SPParam("resetsubsites", "reset")); 26: parameters.Add(new SPParam("systemsource", "syssrc", false, null, new SPUrlValidator())); 27: parameters.Add(new SPParam("sitesource", "sitesrc", false, null, new SPUrlValidator()));"

the error msg is missing name space for SPUrlValidator.... I have referenced the Lapointe.sharepoint.stsadm.commands in the project still its not building... can you please help... Thanks Cheers

Gary Lapointe said...

You should just deploy the WSP and call the command rather than trying to call my assembly directly from code (it's not really intended to be used by code). If I were you though I'd change my master page so that it dynamically loads a css file based on the day rather than trying to swap the master page every day (1 masterpage, 5 css files) - changing the masterpage daily is a very unusual way to solve the problem you've identified.

Jayesh Prajapati said...

Hi Gary,
I am looking for STSADM command that change the authentication type of site to FBA and set FBAProvider and RoleProvider is there any command available for that please let me know.

Many many thanks,
Jay

Sanjay said...

Gary,
Can I download an older version of stsadm extension somewhere?

The SP1 (or maybe older) version. Thanks,
Sanjay

Gary Lapointe said...

Unfortunately I don't maintain older versions - what's the specific issue you are having with the current version?

Gary Lapointe said...

I don't have any FBA related commands - not sure if anyone else has published anything.

John said...

I'm attempting to install the PowerShell commands Setup64.msi on a 64-bit OS (W2K3 R2) with MOSS 2007 SP2 and get the following error: "Error 1001: An exception occured in the OnAfterInstall event handler of Lapointe.SharePoint.PowerShell.Commands.SnapIn -> The SPFarm object cannot be null".

BTW - The .wsp loaded fine ;o)

-- JC

Gary Lapointe said...

Currently the cmdlets only install on PowerShell V1 - if you have V2 installed it will give that error.

Farlin said...

Thanks for the awesome post!!! Very good information and it will save us a lot time writing scripts for site creation. I live in Colorado Springs too, so that makes it all the better!

-- Jeremy

Patrick said...

Hi Gary ,
I have just spend some hours trying to use garys stsadm cmd here
http://stsadm.blogspot.com/2007/08/stsadm-commands_09.html

I have a list on a Subsite A that i need to export.(http://myserver:4040/sites/Test/Misc/Lists/SC/AllItem.aspx)
And then import it to another subsite B .(http://myserver2:4040/sites/CCC/Misc/Lists/SC/AllItem.aspx)

I did create the subsite MISC intentionally on site subsite B so that the URL could be the same

But i have some questionns regarding the command:
I used C:\>stsadm -o gl-exportlist

but i noticed in the log file it also did export all other lists and documents lib under the MISC Subsite A:(.

So when i do
stsadm –o gl-importlist
it cmd stops and complain that those lists and document libs don't exist in SUBSITE B which is true.

Later i tried using
C:\>stsadm -o gl-exportlistitem and
C:\>stsadm -o gl-importlistitem

But it did the same.
How can i just export all items in a specific list.
THanks in Advance

Anonymous said...

Hi Gary,

First of all congratulations for this set of tools. Unfortunately, I can't use them and dunno why.
I'm using WSS 3.0 and I installed the WSS tools version without problems.
I can see the new commands just executing stsadmn. However, when I try to use them or run the help with any of your commands, it's like if it were a wrong command what was specified.

Any idea about this?

Thank you in advance.

Akuma

Gary Lapointe said...

Not sure they are not working for you. I know there are sometimes issues when people copy and paste the command and the hyphen gets changed to a unicode hyphen.

Gary Lapointe said...

Patrick - try playing with some of the include and exclude parameters (can't remember what I named them but do a help on the commands and you'll see them) - you should be able to exclude all dependencies and children on the export.

Jonathan Jenkins said...

Hey Gary.

I am unable to download any of the files. I jsut get a Page cannot be displayed error from every computer I am trying this from. I'm not the smartest guy in the world but I am usually pretty good at downloading stuff. Any chance you could help me with this? The tools sound great and could make my life much easier.

Jonathan

Gary Lapointe said...

My site might have been down for a bit - seems to be working now so you might just want to try again.

Reetu said...

Hi Gary,

First of all thanks for the wonderful article.I ran this command on Widows 2003 OS with SP1 on dev server and everything worked fine. I want to run the comand on productio server which has Win 2008 server with SP1. Is it okay to run the stsadm command with SP1 on Win 2008 OS. Thanks for your help.

Regards,
-Reetu

Gary Lapointe said...

Server OS doesn't matter.

Jonathan said...

Gary, Im getting an Object reference not set to an instance of an object error. I am logged on as the farm admin. I have SP1 installed and not SP2, would this cause this error?

Gary Lapointe said...

What command are you running?

Jonathan said...

Sorry, just trying to install the solution

stsadm -o addsolution -filename ....

Gary Lapointe said...

That sounds like there's something wrong with your farm. I'm assuming you're using an account that has farm admin rights and that you have the path to the WSP file path correct and that your farm is actually built (you'd probably get a different error otherwise). You might want to check the ULS logs to see if you can get a stack trace - that might help to narrow down the issue.

Anonymous said...

I am very interested in using these, but since I'm on Windows 7 I'm kind of stuck. Are there any plans to make this v2 compatible?

Gary Lapointe said...

I'm working on the 2010 version which should be released soon.

Anonymous said...

Is there a way to change the ID of this solution? Some must have created a solution with the same name. I get A solution with the same name "duke.sharepoint.stsadm.comands.wsp" or id "2625fbe6-4884-4666-a1ae-6b06f0db8a6f" already exists in the solution store.

Gary Lapointe said...

Looks like someone used my source and modified it - you'll want to retract the other solution and change the solution ID.

Anonymous said...

Hi,
I'm trying to install the commandlets on a 64-bit OS with MOSS 2007, but, like John, I see the following error:
"Error 1001: An exception occured in the OnAfterInstall event handler of Lapointe.SharePoint.PowerShell.Commands.SnapIn -> The SPFarm object cannot be null"
You responded by saying this could be because PowerShell v2 was installed instead of v1. My machine definitely has v1. Are there any other causes for this error?
Thanks

Roy Lee said...

When I install OServer2010, after the MOSS configuration is done, there is a "configuration wizard" just on the left bottom of the central administration. (for 1m Farm)

Is there a command line to done the function as the "configuration wizard"? (so all the servics will be done?)

I am realy need the command line version of the script, for I have not use the powershell of other part of the batch file.

Any suggestion?
Big thanks in advance.

Gary Lapointe said...

Scripting all the service applications is possible but very complex. There are some scripts that have been posted (by myself and others) - I'll eventually post for all of them but I'm not quite ready to do that (and may delay for quite a while as I'm writing a book which will cover this and don't want to blog all my content).

Roy Lee said...

Hi, Gary

Thanks for your blogs, and also looking for the book.

aah, maybe I can help to translate it to Chinese version:)

I am a vendor tester working for Office14 from beijing, and I need install OServer again and again, your scripts help me a lot.

When is your book going to published?

Anonymous said...

After installed, in powershell I get an error;
There were errors in loading the format data file:Lapointe.SharePoint.PowerShell.Commands, C:\Program Files\Gary Lapointe\PowerShell Commands for SharePoint\Console.psc1 Commands for Sharepoint\Lapointe.SharePoint.Format.pslxml : File skipped because of validation exception: "File C:\Program Files\Gary Lapointe\PowerShell Commands for SharePoint\Lapointe.SharePoint.Format.ps1xml cannot be loaded because the execution of scripts is disabled on this system

Gary Lapointe said...

You need to enable script execution.

set-executionpolicy remotesigned

Ong Khong Shing, Sean said...

Would I be able to install/use the STSADM extensions on MOSS 2003?

Gary Lapointe said...

Sean - unfortunately no - the architecture for stsadm (and indeed just about everything else) changed drastically between 2003 and 2007 so none of the stuff I've put together will work on 2003 - time to upgrade :)

Lucas said...

Hi Gary,

Do you know how to read core.resx file programmatically in a similar way you read files located under App_GlobalResources?
Because I'm a having a hard time trying to do that. No doc found on it.

Great code & great blog!

Gary Lapointe said...

Lucas - Here's an example showing how to do it:

SPUtility.GetLocalizedString("$Resources:core,Folder", null, (uint)web.Locale.LCID));

Steve said...

Thank you for creating and publishing the cmdlets. They are extremely beneficial and save me a ton of work and aggravation.

Christian said...

We just upgraded to a newer version of your great tools (MOSS 2007, SP2, CU August 2010). Now the "gl-copylistsecurity" command does not longer work:

Start Time: 16.09.2010 09:33:56.
Progress: Added "xyz" role definition to target role assignment
"zyx".

Error Type: System.InvalidOperationException
Error Message: Der Vorgang ist für ein Objekt, das Berechtigungen erbt, nicht
zulässig.
Error Source: Microsoft.SharePoint
Error TargetSite:Void UpdateAssignment(Int32, Microsoft.SharePoint.SPRoleDefinit
ionBindingCollection, Boolean)
Error Stack Trace:
bei Microsoft.SharePoint.SPRoleAssignmentCollection.UpdateAssignment(Int32 pr
incipalId, SPRoleDefinitionBindingCollection bindings, Boolean addOnly)
bei Microsoft.SharePoint.SPRoleAssignment.Update()
bei Lapointe.SharePoint.STSADM.Commands.Lists.CopyListSecurity.CopyRoleDefini
tionBindings(SPWeb targetWeb, SPRoleAssignment sourceRoleAssignment, SPRoleAssig
nment targetRoleAssignment, Boolean quiet)
bei Lapointe.SharePoint.STSADM.Commands.Lists.CopyListSecurity.SetObjectSecur
ity(SPWeb targetWeb, SPWeb sourceWeb, ISecurableObject sourceObject, ISecurableO
bject targetObject, Boolean quiet, String itemName)
bei Lapointe.SharePoint.STSADM.Commands.Lists.CopyListSecurity.CopySecurity(S
PList sourceList, SPList targetList, SPWeb targetWeb, Boolean includeItemSecurit
y, Boolean quiet)
Finish Time: 16.09.2010 09:33:56.

Any ideas?
The old version still works very well after installation of CU august 2010.

We have been able to replicate this problem on two different servers.

Thanks a lot.

Kind regards,

Christian

Anonymous said...

Hi Gary,

I have been trying to use the CopyList and Import/Export commands and while it claims i have been successful nothing is appearing in the target list - the log files record the list item ids being copied but nothing appears in the target list? any ideas

JC said...

Question on SP2010 cmdlets...I successfully installed the .wsp and can access the stsadm gl- commands but I don't seem to have any visibility to the powershell cmdlets at all. Did I miss something?

Bought the book - great read so far!

-- John

Gary Lapointe said...

Have to ask the obvious first: are you using the SP Management Shell or otherwise loading the snap-in (after installing the WSP)? If you're in the same session as you were when you installed the WSP then you need to remove the snap-in and re-add it.

Jon Fleming said...

I just upgraded to SharePoint 2010 Foundation on Small Business Server 2010. I'm missing your excellent gl-backupsites extension. I tried to install your SharePoint 2010 Server Cmdlets (x86, x64) but Powershell 2.0 doesn't include the Add-SPSolution cmdlet. Am I stuck?

Gary Lapointe said...

If you load the SharePoint 2010 Management Shell then that will have the SharePoint PowerShell snap-in loaded which includes the Add-SPSolution cmdlet. You can then install my 2010 cmdlets and you'll have the Backup-SPSite cmdlet that replaces the gl-backupsites stsadm command.

mark said...

I've found that the sp2010 commandlets install into the GAC but I can't use Add-PSSnapin to include them into the command shell (either a new one or the existing one). Also, an entry for the snapin doesn't show up in the registry here:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellSnapIns

mark said...

I now notice that the commands are added automatically...but it is still strange that I can't use Add-PSSnapin

Gary Lapointe said...

No idea why Add-PSSnapin isn't working for you as that's actually been around since PowerShell 1.0 so there's nothing new there.

Gary Lapointe said...

Mark - just saw your first comment so now your statement about add-pssnapin makes more sense to me :) (downside of reading email from most recent first).

So - my PowerShell commands don't are not a standalone snap-in - they are registered by the Microsoft.SharePoint.PowerShell snapin so there's nothing you need to do other than deploy the WSP. This adds the appropriate registration files that are needed by the SharePoint Snapin so that the cmdlets are registered just as though it were part of the built in snap-in.

Hope this clarifies.

Jon Fleming said...

If you load the SharePoint 2010 Management Shell then that will have the SharePoint PowerShell snap-in loaded which includes the Add-SPSolution cmdlet. You can then install my 2010 cmdlets and you'll have the Backup-SPSite cmdlet that replaces the gl-backupsites stsadm command.

OK, I figured out how to load the SharePoint snap-in, but I still can't install your cmdlets. See http://i2.photobucket.com/albums/y10/JonF/Install.png.

Jon Fleming said...

OK, I figured out why add-spsolution didn't work. It requires the full pathname of the file even though the file is in the current directory. I'm an old-timey command-line guy, but I gotta ask ... who really thinks PowerShell and Exchange Management Shell and SharePoint 2010 shell are better?

Gary Lapointe said...

:)
PowerSehll as a technology is better but it's up to the cmdlet authors to test their stuff properly - and in the case of SharePoint, testing was not exactly optimal. In this case they should have accounted for a relative path but they didn't test that scenario. One way you can get around it is to use the Resolve-Path cmdlet.