SharePoint 2010-创建补充web.config文件

关于未应用于web.config的补充文件:来自 MSDN :“通过运行copyappbincontent stsadm命令行操作,可以将更改追溯应用到服务器的web.config文件。必须在部署中的每个前端Web服务器上运行该操作。“

正如Russ和Breischl建议的那样,您可以使用SPWebApplication对象的WebConfigModifications属性。要将它与您的特性一起部署,请将代码放在特性接收器中。这样,您可以在安装该功能时自动修改web.config。

在功能接收器中,不要忘记调用SPWebApplication对象上的applyWebConfigModifications()属性。

例子: http://weblogs.asp.net/wesleybakker/archive/2009/01/21/web.config-modifications-with-a-sharepoint-feature.aspx

您可以将特性和特性接收器程序集打包到单个WSP程序包中。

创建补充配置文件时,web.config修改为 不自动合并 直到你打电话给 stsadm -o copyappbincontent .

您还可以强制此命令通过 FeatureReceiver .

在探索之后 stsadm 工具在反射镜我发现 copyappbincontent 操作调用 SPWebApplication.WebService.ApplyApplicationContentToLocalServer() ’

public override void FeatureActivated(SPFeatureReceiverProperties properties)
{
    var webApp = (SPWebApplication)properties.Feature.Parent;
    webApp.WebService.ApplyApplicationContentToLocalServer();
}

道具 @ Jason Weber 因为他知道了这一点,但不幸的是,他把他的答案放在了评论而不是问题上。

将其放入名为addwebconfigmods.ps1的文件中

Param ($weburl, $WebConfigModifications )

$url = New-Object System.Uri($webUrl)

[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint") | Out-Null
$webApp = [Microsoft.SharePoint.Administration.SPWebApplication]::Lookup($url)


#delete mods by the owners being added
$ownerstodelete = $WebConfigModifications | Group-Object owner | Select-Object Name

foreach($owner in $ownerstodelete)
{
    $modstodelete = @()
    foreach($mod in $webApp.WebConfigModifications)
    {
        if($mod.Owner -eq $owner.Name)
        {
            $modstodelete += $mod
        }
    }

    Write-Host ("Deleting " + $modstodelete.Count + " mods for owner: " + $owner)

    foreach($delmod in $modstodelete)
    {
        Write-Host (" + Deleting " + $delmod.Value)
        $webApp.WebConfigModifications.Remove($delmod) | Out-Null
    }
}

#this is where we start to add mods
$i = 0;

Write-Host ("Adding " + $WebConfigModifications.Count + " webconfig modifications to " + $weburl) 

foreach($modEntry in $WebConfigModifications)
{
    Write-Host (" + Adding " + $modEntry.Value)

    $mod = New-Object Microsoft.SharePoint.Administration.SPWebConfigModification
    $mod.Path = $modEntry.Path
    $mod.Name = $modEntry.Name
    $mod.Sequence = $i++
    $mod.Owner = $modEntry.Owner
    $mod.Type = $modEntry.Type
    $mod.Value = $modEntry.Value

    $webApp.WebConfigModifications.Add($mod)

}

$webApp.Update()
$webApp.WebService.ApplyWebConfigModifications()

然后用这样的配置创建一个csv文件

Name,Path,Owner,Type,Value
system.serviceModel,configuration,alinean-common,EnsureSection,<system.serviceModel/>
connectionStrings,configuration,alinean-common,EnsureSection,<connectionStrings />
appSettings,configuration,alinean-common,EnsureSection,<appSettings />
serviceHostingEnvironment,configuration/system.serviceModel,alinean-common,EnsureChildNode,<serviceHostingEnvironment aspNetCompatibilityEnabled='true'/>

然后在另一个ps1脚本中,理想情况下是用于部署解决方案的脚本,导入csv配置选项并调用在第一个代码块中创建的函数:

#read config mods from CSVs
$mods = Import-CSV .\config\admin-common.webconfigmods.csv

Write-Host "Applying configuration modifications"
#add web config mods to sharepoint using powershell script
&.\AddWebConfigMods "[sharepoint site url]" $mods
&stsadm -o execadmsvcjobs

我相信 this 会帮助你的。使用webconfigmodifications会被SharePoint记住,并自动写入物理web.config文件中供您使用,从而便于跨多个部署的站点进行维护。

RUSS是正确的,您需要使用WebConfigModifications。 Here 是另一个只使用纯代码的资源。