Skip to main content

Make the -LiteralPath shorter in your Add- and Update-Solution cmdlets

I got tired of allways typing a very long -LiteralPath in my PowerShell cmdlets. So I went out on the Internet to visit Google and found this command.

Get-Location, or even shorter, the alias gl.

$curdir = gl
Add-SPSolution -LiteralPath $curdir"\SharePointSolution.wsp"

Comments

Popular posts from this blog

The form cannot be submitted because of an error

Problem I created a reusable approval workflow in SharePoint Designer 2010. I initiated the workflow. Then when I filled in the Assigned To field I got an error pop up saying: "The form cannot be submitted because of an error". Solution Uninstall the KB2553322 for SharePoint Designer. I didn't uninstall KB2553322 for Microsoft Office. Restart SharePoint Designer. Recreate the workflow.

Can't read from source file or disk

When you are using Windows Explorer View in SharePoint you can't MOVE a file from one site to another if it's not directly below the root site, but you can copy the file. See the different scenarios below. Working Scenario Moving files between libraries within the same site. For example: "http://sharepointsite/sites/site1/site2/library1" (source) "http://sharepointsite/sites/site1/site2/library2" (destination) Moving files between libraries across different sites as long as they are directly below the root site. For example: "http://sharepointsite/site1/library1 (source) "http://sharepointsite/site2/library2 (destination) Non-working Scenario Moving files between libraries in sub-sites that are more than 1 level below the root site. For example: "http://sharepointsite/sites/site1/site1/library1" (source) "http://sharepointsite/sites/site1/site2/library2" (destination)

Problem installing service pack 1 for SharePoint Foundation 2010

I have a SharePoint farm with one application server, two WFE servers and one db server. When I ran the configuration wizard after I installed service pack 1 on the application server and the WFE servers I got an error that said that the service pack was missing on the WFE servers. Solution: Open your powershell editor and execute the following command on the WFE servers. Get-SPProduct –local Then run the configuration wizard again.