CODEWITHSUNDEEP
visual-studiosharepointdeploymentwsp
RichardTheKiwi
RichardTheKiwi

Reputation: 107806

Sharepoint wsp deployment why is setup.bat 100 times slower than Visual Studio deployment?

When right-clicking in Solution Explorer and deploy - it takes seconds.

When running setup /uninstall http://site from the \bin folder of the solution, it takes 13 minutes?! There are 8 features to activate, but my question is why does it take so long; and what is the equivalent command to deploy it the way Visual Studio [2005] does to Sharepoint [2007]?

Upvotes: 0

Views: 702

Answers (2)

ukhardy
ukhardy

Reputation: 2104

VS deploys solutions immediately so that you could troubleshoot any problems right away.

You can do that manually for yourself:

Following your setup command, run this:

%stsadmpath%\stsadm -o execadmsvcjobs

Infact this is part of VS deploy commands.

Upvotes: 0

Jason Weber
Jason Weber

Reputation: 1532

When VS deploys a WSP it does so using the equivalent of the -local switch. This flag allows a synchronous deployment since it only occurs on the server the command is being run from. Obviously, this is not an option for a multi-server deploy.

If your BAT file is not using this switch then the jobs are being queued to the Timer service for eventual execution. This may be a part of your issue, although 13 minutes seems too long to be explained by this alone.

Here's one example of an STSADM command that offers the -local switch.

Upvotes: 2

Related Questions