0

My team from Microsoft already has a SharePoint site up and running. My job is to take a portion of it and migrate it to TFS. My Manager told me that I have to find a staging environment for sharepoint so that I don't mess with the real site incase I mess up. However, on all of my searches I can't seem to figure how to set up a staging environment in Visual Studio for SharePoint and how to migrate info from SharePoint to TFS. If my question is way too loaded, please let me know what is wrong with this question so it can be more specific.

Improve this question
2
  • what i understand...you have a on prem sharepoint site, and want some development on it. for that you want to move that site collection into TFS server and you want to know what is procedure?
    – Waqas Sarwar MVP ♦
    Jul 14, 2015 at 21:25
  • Sorry, I should have specified that what I was asking is actually two separate jobs. First, there is a portion of the sharepoint site that I will be migrating to TFS and I am not sure how to do this process. Second, I am also updating the sharepoint site, but I want to first set up a staging environment so that when i'm testing the changes, it won't mess up the actual site. I am not clear on how to set up this staging process either.
    – Chloe Claridad
    Jul 14, 2015 at 21:34

1 Answer 1

Reset to default
1

Sorry, but this doesn't sound quite right. A staging environment should match the configuration of the prod environment. I wouldn't just tell someone to create a staging environment, I'd give them the script that configured prod so they could just run the script to duplicate the environment. Without the script, you'd at least need to know the service pack level of prod, in addition to knowing what web apps exist, what settings they're configured with, etc. (to be clear, a staging environment isn't set up in visual studio, it's a full install of SP running on a different box (or, boxes)).

As far as taking a portion of the site and moving it to TFS? This doesn't make sense. TFS will store developer assets, such as custom web parts, apps, workflows, etc. But, you don't just take them from SP. They've been deployed to SP, so you would need a copy of the source code to move to TFS.

So, if you need a staging environment, you'd first need to know what prod is: SP 2013, SP 2010, Office 365? Then, unless its office 365, you get a spare server and spare SQL instance and install SP, configuring it as it exists in prod. Then, ramp up on building Solutions or Apps.

Good luck.

Improve this answer
1
  • Definitely this. Staging should also be cloned as a copy of production for each full feature release. You never want production and staging to be out of date as staging is as much about testing your deployment process as it is testing as close to production as possible.
    – Michael A
    Jul 14, 2015 at 23:10

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

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