SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Machine 1: Virtual Development box with Visual Studio 2010, SharePoint 2010 Foundations, Designer 2010.

Machine 2: SharePoint 2010 Enterprise (Staging Environment)

Question: Does Machine 2 need to have Visual Studio 2010 installed if I want to deploy features/solutions from Machine 1?


share|improve this question
up vote 3 down vote accepted

No, you can install your .wsp's with PowerShell cmdlets:



share|improve this answer
Thanks for the quick reply. To further my understanding though, if I really want to deploy from Visual Studio, do I then need to have it on both machines? – Sean Jul 10 '12 at 16:08
yes, but don't do that. Visual Studio is not deploying the solutions exactly as a good script will do. You won't be able to ensure it will works the same. – Steve B Jul 10 '12 at 16:17
Thanks! I will keep this in mind. – Sean Jul 10 '12 at 16:25
This is a common scenario at our company. We do all development on a dev box, deploy to a staging environment via PowerShell and test, rework any issues we come into, and then deploy to production (again via PowerShell). – RJ Cuthbertson Jul 10 '12 at 16:30
That's how I am planning to do it now. I am in the infancy of SP2010 research and development at present. Thanks again! – Sean Jul 10 '12 at 17:34

In addition to @rjcup3 answer,

Other options:

  • Install VS 2012. With VS 2012, you can remote publish without needing to install VS on Machine 2 or manually publishing your wsp package to Machine 2. That means, install VS 2012 on Machine 1, create your package, deploy your package to Machine 2.

    Reference: SharePoint Developer Team Blog

  • Check out this blog. But, I have not personally used it.

share|improve this answer
that is fabulous. great news. though, qualified: only for sandboxed solutions. – 1c1cle Jul 10 '12 at 17:45
Did not know this. ^ @1c1cle that's lame and unfortunate. – RJ Cuthbertson Jul 10 '12 at 17:45
True; That is one of limitations of using remote publishing in VS 2012. – Hossein Aarabi Jul 10 '12 at 18:09
Thanks for the addition! – Sean Jul 10 '12 at 18:10

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.