SharePoint 2010 Dev Machine Deploy to Stage Machine

Question

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?

Thanks

RJ Cuthbertson · Accepted Answer · 2012-07-10 16:04:22Z

3

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

answered Jul 10, 2012 at 16:04

RJ Cuthbertson

8,3526 gold badges38 silver badges76 bronze badges

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
Commented Jul 10, 2012 at 16:08
1

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
Commented Jul 10, 2012 at 16:17
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
Commented Jul 10, 2012 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
Commented Jul 10, 2012 at 17:34

Add a comment |

Glorfindel · Accepted Answer · 2021-06-24 13:00:41Z

2

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.

Glorfindel

1,0491 gold badge11 silver badges17 bronze badges

answered Jul 10, 2012 at 16:40

Hossein A

1,4891 gold badge16 silver badges31 bronze badges

1

that is fabulous. great news. though, qualified: only for sandboxed solutions.
– 1c1cle
Commented Jul 10, 2012 at 17:45
Did not know this. ^ @1c1cle that's lame and unfortunate.
– RJ Cuthbertson
Commented Jul 10, 2012 at 17:45
True; That is one of limitations of using remote publishing in VS 2012. msdn.microsoft.com/en-us/library/hh370987(VS.110).aspx
– Hossein A
Commented Jul 10, 2012 at 18:09

Add a comment |

2 Answers 2