您如何在Sharepoint環境中處理代碼促銷?

[英]How do you handle code promotion in a Sharepoint environment?


In a typical enterprise scenario with in-house development, you might have dev, staging, and production environments. You might use SVN to contain ongoing development work in a trunk, with patches being stored in branches, and your released code going into appropriately named tags. Migrating binaries from one environment to the next may be as simple as copying them to middle-ware servers, GAC'ing things that need to be GAC'ed, etc. In coordination with new revisions of binaries, databases are updated, usually by adding stored procedures, views, and adding/adjusting table schema.

在具有內部開發的典型企業方案中,您可能具有開發,登台和生產環境。您可以使用SVN在一個主干中包含正在進行的開發工作,其中補丁存儲在分支中,並且您發布的代碼將進入適當命名的標記。將二進制文件從一個環境遷移到另一個環境可能就像將它們復制到中間件服務器一樣簡單,GAC需要進行GAC操作等等。與新版本的二進制文件協調,數據庫會更新,通常是通過添加存儲過程,視圖和添加/調整表模式。

In a Sharepoint environment, you might use a similar version control scheme. Custom code (assemblies) ends up in features that get installed either manually or via various setup programs. However, some of what needs to be promoted from dev to staging, and then onto production might be database content that supports the custom code bits.

在Sharepoint環境中,您可以使用類似的版本控制方案。自定義代碼(程序集)最終會出現在手動或通過各種安裝程序安裝的功能中。但是,需要從開發階段升級到暫存,然后再生產的一些內容可能是支持自定義代碼位的數據庫內容。

If you've managed an enterprise Sharepoint environment, please share thoughts on how you manage promotion of code and content changes between environments, while protecting your work and your users, and keeping your sanity.

如果您管理過企業Sharepoint環境,請分享您如何管理環境之間代碼和內容更改的提升,同時保護您的工作和用戶,以及保持理智。

4 个解决方案

#1


1  

I assume when you talk about database content you are referring to the actual contents contained in a site a or a list.

我假設當您談論數據庫內容時,您指的是站點a或列表中包含的實際內容。

Probably the best way to do this is to use the stsadm import and export commands to export and import content from one environment to another. (Don't use backup/restore when going from one environment to another.)

可能最好的方法是使用stsadm導入和導出命令將內容從一個環境導出和導入到另一個環境。 (從一個環境到另一個環境時不要使用備份/恢復。)

#2


1  

For any file changes (assemblies, aspx) you can use Features and then keep track of the installers. You would install the feature and do an upgrade to push changes.

對於任何文件更改(程序集,aspx),您可以使用功能,然后跟蹤安裝程序。您將安裝該功能並進行升級以推送更改。

There's no easy way to sync the data...you can use stsadm import/export commands as John pointed out. But this may not be straight-forward, especially if the servers are configured differently.

沒有簡單的方法來同步數據......你可以使用stsadm import / export命令,正如John指出的那樣。但這可能不是直截了當的,特別是如果服務器配置不同。

There's also Data Sync Studio product (http://www.simego.net/DataSync_Studio.aspx) you can try.

您還可以嘗試使用Data Sync Studio產品(http://www.simego.net/DataSync_Studio.aspx)。

#3


1  

Depending on what form the database content takes, I would keep the creation of it in code so it's all in one place (your Visual Studio project) and can also be managed via source control. Deployment of the content could either be via a console application or even better feature receiver.

根據數據庫內容的形式,我會在代碼中創建它,因此它可以在一個地方(您的Visual Studio項目),也可以通過源代碼控制進行管理。內容的部署可以通過控制台應用程序或甚至更好的功能接收器。

You might also like to read this blog post and look at the tool mentioned there for another approach.

您可能還想閱讀此博客文章並查看其中提到的工具以獲得另一種方法。

#4


0  

The best resource I can point you to is Eric's paper:

我可以指出的最好的資源是Eric的論文:

http://msdn.microsoft.com/en-us/library/bb428899.aspx

I was part of a team working to better the story around development of WSS and MOSS solutions with TFS, but I don't know where that stands.

我是一個團隊的一員,致力於通過TFS改進WSS和MOSS解決方案開發的故事,但我不知道它的位置。


注意!

本站翻译的文章,版权归属于本站,未经许可禁止转摘,转摘请注明本文地址:https://www.itdaan.com/blog/2008/09/22/724e4368290bb73cbe1ade041a4eb90f.html



 
粤ICP备14056181号  © 2014-2020 ITdaan.com