Is anyone else calling PowerShell from the Post-deployment Command Line?
I’ve performed the following steps but am receiving an error that only gets one
slightly related hit on Google.
Can someone take a look and tell me if there’s anything obviously wrong?
Post-deployment command:
%windir%\sysnative\windowspowershell\v1.0\powershell -file
“$(ProjectDir)PScripts\Upgrade.ps1″ -configuration “$(ConfigurationName)” -url
“$(SharePointSiteUrl)” -filepath “$(TargetDir)$(TargetName).wsp” -name
"$(TargetName).wsp"
Upgrade.ps1:
# Add our Post-Deployment command parameters
Param($configuration, $url, $name, $filepath)
# Check if SharePoint snapin is present and add it otherwise
$snapin = get-pssnapin | where { $_.Name -eq “Microsoft.SharePoint.PowerShell” }
if($snapin -eq $null) {
Add-PSSnapin Microsoft.SharePoint.PowerShell;
Write-Host "Adding SharePoint Snapin" -ForegroundColor yellow;
}
#Global deployment to GAC
Write-Host "Updating" $name -ForegroundColor yellow;
Update-SPSolution -Identity $name -LiteralPath $fileptah -GACDeployment
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of
Paul Noone
Sent: Tuesday, 6 December 2011 3:36 PM
To: ozMOSS
Subject: RE: VS2010 - Multi-server deployment
Thanks mate. I couldn’t agree more but we don’t have the luxury of three farms
for 2010 at this stage.
Your assumptions about the VS commands are correct. They are apparently limited
to singel server setups.
I’ll try using PS to do some post-build stuff. Thanks.
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of
Matthew Cosier
Sent: Tuesday, 6 December 2011 2:21 PM
To: 'ozMOSS'
Subject: RE: VS2010 - Multi-server deployment
Perhaps I’m missing something here, but if you perform an Add-SPSolution, then
an Install-SPSolution targeted at a web application (-WebApplication) in a
farm environment, SharePoint will take care of deploying this to all necessary
servers in the farm (via the timer service).
You’re saying that the VS 2010 deployment commands aren’t doing this? Perhaps
IIS isn’t being reset? Have you told it in the package to perform a
start/stop? You can always ditch the commands and execute a custom set of PS
scripts in the post/pre’s in VS instead. (Also, I recommend using ‘No
Activation’ if you can help it.). Your scripts can then be smarter about
things, and perform an Upgrade-SPSolution instead of Add’s and retracts all the
time, etc.
Plus, I’m not sure if everyone agrees with me on this - but using a farm for
your dev environment is probably overkill anyway - your test environment and
staging however, should almost certainly mimic production as much as possible.
Matthew Cosier
Hazaa
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of
Paul Noone
Sent: Tuesday, 6 December 2011 1:46 PM
To: ozMOSS
Subject: RE: VS2010 - Multi-server deployment
What I mean is that the Deploy command does not work on multi-server farms,
which is what my dev farm is. :)
So instead I Package and then use PS or STSADM to deploy/upgrade/retract. Very
annoying.
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of
Ajay
Sent: Tuesday, 6 December 2011 1:32 PM
To: ozMOSS
Subject: Re: VS2010 - Multi-server deployment
What are you building.. VS 2010 SharePoint tools build a WSP.
I think it has everything devs need.. have not felt need to use any other tool
since started using VS2010
On Tue, Dec 6, 2011 at 3:22 PM, Paul Noone
<paul.no...@ceosyd.catholic.edu.au<mailto:paul.no...@ceosyd.catholic.edu.au>>
wrote:
Does anyone know if this achievable using the standard Visual Studio UI
commands, or do I go back to using WSPBuilder?
_______________________________________________
ozmoss mailing list
ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com>
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
_______________________________________________
ozmoss mailing list
ozmoss@ozmoss.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
