Sharepoint 2010/13

Hi All,

Suppose Sharepoint 2010/13 farm installed in Production environment and being used by Users.

Now I got requirement to change some features which can be changed in out of the box so no WSP solution required.

Lets say, items need to change like any list ( add new column ,  add new customized form , designed in SP designer , changed some Java script logic , add new JS etc. )  and its working fine in Dev environment.

Now how should I take it to Test & Prod environment ? I think one way is to Content DB transfer ? but considering Prod  environment getting  continue  data  so how can we install specific changes  without loss of prod data ? Do I need to make WSP for those items in Visual Studio to give it Admin of Prod environment ?

Hope I am able to clear problem , if yes please reply ...Many Thanks....

,

May 30th, 2015 10:14am

Hi Anupam,

The answer to your question is - It Depends.

It depends on what changes your are trying to move to Test/Prod site. If the changes are related to creating new artifacts, then best approach should be - Use the SP PowerShell script to propagate the changes or you can use the new WSP as well.

Also, you can opt for upgrading the solution/feature to make the changes (upgrading is a bit trickier though).

But if you making changes to existing artifacts such as Site Column or List Column, then you should plan it carefully as it may result in loss of data that you would certainly not want.

Here are some helpful links -

1.http://stackoverflow.com/questions/5512310/best-practices-for-updating-sharepoint-2010-production-site

2. https://www.simple-talk.com/dotnet/.net-tools/using-features-and-solutions-to-deploy-your-sharepoint-customizations/

Hope it answers your question.

Free Windows Admin Tool Kit Click here and download it now
May 30th, 2015 8:56pm

Hi Ashish,

Thanks for reply , could you please elaborate more on as you said in previous reply

"you can opt for upgrading the solution/feature to make the changes (upgrading is a bit trickier though)."

I have used upgrade solution command after changing WSP so it works fine. So in what scenario it could be "bit trickier though"

July 18th, 2015 9:11am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics