简介

==========

MOSS在一定数量上的功能领域是非常依赖timer jobs的. Timer Jobs在一个固定的时间周期上运行, 然而不论如何, 它们总要在一个被赋予的schedule上执行. 如果你想要让某个特别的timer job按照你的想法来运行, 怎么办呢? 这篇文章会告诉你答案.

更换Timer Jobs的Schedule

==========

如果你想要强制执行一个MOSS的timer job, 很不幸, 你不能这样做. 因为每一个timer job都有一个固定的schedule.

有三种类型的schedule:

• Minutes
• Hourly
• Daily

尽管你不能强制执行一个timer job, 你却毫无疑问地可以修改一个timer job的执行时间计划, 它能帮助你完成强制执行一个timer job的愿望. 比如说, Usage Analysis job是一个daily job. 它每天只执行一次. 如果说, 你想要这个job立即执行的话, 你可以把它从"Daily"修改为"Minutes".

所有内建的MOSS timer job都可以使用stsadm命令行的setproperty命令来修改. 要把usage analysis job从每24小时执行一次, 变为每5分钟执行一次, 你可以使用下面的命令:

stsadm -o setproperty -pn job-usage-analysis -pv "Every 5 minutes"

所有其他的内建的timer jobs的名字列在下面:

• job-change-log-expiration
• job-dead-site-delete
• job-diskquota-warning
• job-immediate-alerts
• job-recycle-bin-cleanup
• job-usage-analysis
• job-workflow
• job-workflow-autoclean
• job-workflow-failover

不同频率的格式列表

如果你有一个自定义的timer job的definition, 并且你还想修改它的schedule, 唯一我能想到的方法就是使用Object Model. 因为没有stsadm命令可以帮助你修改自定义的job. 下面就是一个代码例子, 它展示了如何修改一个custom job的schedule, 使它变为按分钟计算的那种schedule:

using (SPSite site = new SPSite("http://servername"))
{ 
    using(SPWeb web = site.OpenWeb())
    {
        SPFarm farm = site.WebApplication.Farm;
        SPWebApplication webApp = site.WebApplication;
        foreach (SPJobDefinition jobDef in webApp.JobDefinitions)
        {
            // if (jobDef.WebApplication == siteCollection.WebApplication)
            // Console.WriteLine(jobDef.Title);
            if (jobDef.Title == "Usage Analysis")
            {
                jobDef.Schedule = new SPMinuteSchedule(); 
                jobDef.Update(); 
                break;
            }
        }
    }

结论

===========

如果你想要执行一个很久之后才会再次执行的MOSS的timer job的时候, 你可以通过修改这个job的schedule来做到. 如果job是内建的, 那么你可以通过stsadm来修改. 如果job是一个自定义的, 那么唯一可行的方法就是通过MOSS的SDK.

运行下面的命令来立即执行administrative timer jobs

stsadm -o execadmsvcjobs

译自:

Forcing Execution of MOSS Timer Jobs

http://blogs.msdn.com/tehnoonr/archive/2009/02/15/forcing-execution-of-moss-timer-jobs.aspx

方法一: SharePoint Designer

====================

1. 在SharePoint Designer中打开站点.

2. 右键单击你想要查看的文档库的tree node, 选择properties.

方法二: Object Model

==================

SPSite对象的StorageManagementInformation方法可以被用来读取整个站点集上的列表, 文档库的尺寸信息.

using (SPSite site = new SPSite("http://servername"))
{ 
    DataTable tbl; 
    tbl = site.StorageManagementInformation(
        SPSite.StorageManagementInformationType.DocumentLibrary, 
        SPSite.StorageManagementSortOrder.Decreasing, 
        SPSite.StorageManagementSortedOn.Size, 100); 
    foreach (DataRow row in tbl.Rows) 
    {
        foreach (DataColumn column in tbl.Columns)          
            MessageBox.Show("Doc Lib Name :" + row["Title"].ToString() + "  Size (bytes): " + row["Size"].ToString()); 
    } 
}

方法三: 用存储过程在数据库中直接捞取

==================

使用这个存储过程, 可以得到按字节的, 站点集中的包括metadata的信息在内的所有文档库的大小.

PROCEDURE proc_GetDocLibrarySizes (
@SiteId uniqueidentifier
);

[MS-WSSCADM]: Windows SharePoint Services Content Database Administrative Communications Protocol Specification

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

SharePoint Document library size

http://sridharu.blogspot.com/2009/02/sharepoint-document-library-size.html

微软在MSDN上公布了SharePoint Products and Technologies Protocols, 文档采用PDF格式打包成ZIP供用户随意下载.

关于SharePoint Protocol的信息, 可以访问http://msdn.microsoft.com/en-us/library/cc339475.aspx. 这个页面上有下载地址.

所谓Protocol文档, 它对微软私有的SharePoint 产品与技术与其他微软产品交互的协议(包括对工业标准的扩展或者其他发布了的protocol)提供了非常细节的技术明细.

这份文档的目的就是为了在细节上描述protocol是如何被SharePoint产品与技术使用的. 每一个协议的明细文档都记录了技术需求, 技术限制, 依赖, 和微软的具体的协议行为.

这里的文档还包括一系列的概览, 和引用了的文档. 提供给您概念背景, 不同协议之间关系和交互方式的概览, 还有技术上的引用信息.

如果你下载了这份协议文档包, 你打开后应该是这样的:

看文件名很难搞清楚其对应的内容. 你需要参考Reference表, 才能找到你感兴趣的部分所对应的文档名. 我把核心内容列在下面, 以供参考.

注意, 这份协议文档还是在不断的更新中, 其中有些文档仅适用于SharePoint 2010, 有些仅适用于SharePoint 2007, 有些二者都适用. 要获得每个文档究竟适用于那个版本的sharepoint, 你可以查看每一个文档的附录部分(有的是附录A, 有的是附录B), 其中的Product Behavior对所适用的版本有说明.

[MS-ACCDT] Microsoft Corporation, "Access Template File Format Specification", July 2009.

[MS-ADMINS] Microsoft Corporation, "Administration Web Service Protocol Specification", June 2008.

[MS-ADS] Microsoft Corporation, "Access Services Data Server Protocol Specification", July 2009.

[MS-ADTS] Microsoft Corporation, "Active Directory Technical Specification", March 2008.

[MS-ALERTSS] Microsoft Corporation, "Alerts Service Protocol Specification", June 2008.

[MS-ASWS] Microsoft Corporation, "Access Services Protocol Specification", July 2009.

[MS-AUTHWS] Microsoft Corporation, "Authentication Web Service Protocol Specification", June 2008.

[MS-AXL] Microsoft Corporation, "Access Application Transfer Protocol Structure Specification", July 2009.

[MS-BCSDPFFS] Microsoft Corporation, "Business Connectivity Services Deployment Package File Format Specification", July 2009.

[MS-BCSDWPS] Microsoft Corporation, "Business Connectivity Services Deployment Web Service Protocol Specification", July 2009.

[MS-BDCDP] Microsoft Corporation, "Business Data Catalog Data Web Service Protocol Specification", June 2008.

[MS-BDCMFFS] Microsoft Corporation, "Business Data Connectivity Model File Format Specification", July 2009.

[MS-BDCRAWPS] Microsoft Corporation, "Business Data Connectivity Remote Administration Web Service Protocol Specification", July 2009.

[MS-CDEPLOY] Microsoft Corporation, "Content Deployment Remote Import Web Service Protocol Specification", June 2008.

[MS-CONATB] Microsoft Corporation, "Content Area Toolbox Web Service Protocol Specification", June 2008.

[MS-COPYS] Microsoft Corporation, "Copy Web Service Protocol Specification", June 2008.

[MS-CPSWS] Microsoft Corporation, "SharePoint Claim Provider Web Service Protocol Specification", July 2009.

[MS-CSOM] Microsoft Corporation, "SharePoint Client Query Protocol Specification", July 2009.

[MS-CSOMSPT] Microsoft Corporation, "SharePoint Client-Side Object Model Protocol Specification", July 2009.

[MSDN-ASPWP] Microsoft Corporation, "ASP.NET Web Parts Overview", http://msdn.microsoft.com/en-us/library/hhy9ewf1.aspx.

[MSDN-EXCELS] Microsoft Corporation, "Introducing Excel Services", http://msdn.microsoft.com/en-us/library/ms519581.aspx.

[MSDN-IIS] Microsoft Corporation, "Internet Information Services", http://msdn.microsoft.com/en-us/library/aa286507.aspx.

[MSDN-MOSS2007-SDK] Microsoft Corporation, "Microsoft Office SharePoint Server 2007 SDK", http://msdn.microsoft.com/en-us/library/bb931736.aspx.

[MSDN-ODBC] Microsoft Corporation, "Microsoft Open Database Connectivity (ODBC)", http://msdn.microsoft.com/en-us/library/ms710252.aspx.

[MSDN-OLEDB] Microsoft Corporation, "Microsoft OLE DB", http://msdn.microsoft.com/en-us/library/ms722784.aspx.

[MSDN-WSSWP] Microsoft Corporation, "Web Part in Windows SharePoint Services", http://msdn.microsoft.com/en-us/library/ms476318.aspx.

[MS-DOCTRANS] Microsoft Corporation, "Document Transforms Service Protocol Specification", June 2008.

[MS-DSPSTSS] Microsoft Corporation, "Data-Source Adapter SharePoint Team Services Web Service Protocol Specification", June 2008.

[MS-DWSS] Microsoft Corporation, "Document Workspace Web Service Protocol Specification", June 2008.

[MS-EAWF] Microsoft Corporation, "Group Approval Web Service Protocol Specification", June 2008.

[MS-ECTPWPS] Microsoft Corporation, "External Content Type Picker Web Service Protocol Specification", July 2009.

[MS-EMMWCF] Microsoft Corporation, "Metadata Shared Service WCF Service Protocol Specification", July 2009.

[MS-EMMWS] Microsoft Corporation, "Microsoft Enterprise Managed Metadata Web Service Protocol Specification", July 2009.

[MS-ESP] Microsoft Corporation, "Excel Web Services Protocol Specification", June 2008.

[MS-ESURL] Microsoft Corporation, "Excel Services Publishing Protocol Specification", June 2008.

[MS-FORMS] Microsoft Corporation, "Forms Service Protocol Specification", June 2008.

[MS-FPSE] Microsoft Corporation, "FrontPage Server Extensions Remote Protocol Specification", June 2008.

[MS-FSDAP] Microsoft Corporation, "Forms Services Design and Activation Web Service Protocol Specification", June 2008.

[MS-FSFDP] Microsoft Corporation, "Forms Services Feature Detection Protocol Specification", June 2008.

[MS-FSSHTTP] Microsoft Corporation, "File Synchronization via SOAP over HTTP Protocol Specification", July 2009.

[MS-FSSHTTPB] Microsoft Corporation, "Binary Requests for File Synchronization via SOAP Protocol Specification", July 2009.

[MS-GLOS] Microsoft Corporation, "Windows Protocols Master Glossary", March 2007.

[MS-IPFF] Microsoft Corporation, "InfoPath Form Template Format Structure Specification", June 2008.

[MS-IPFF2] Microsoft Corporation, "InfoPath Form Template Format Version 2 Structure Specification", July 2009.

[MS-IPFFX] Microsoft Corporation, "InfoPath Form File Format Specification", June 2008.

[MS-LISTSWS] Microsoft Corporation, "Lists Web Service Protocol Specification", June 2008.

[MS-MAR] Microsoft Corporation, "MOSS Analytics Reporting Protocol Specification", July 2009.

[MS-MEETS] Microsoft Corporation, "Meetings Web Services Protocol Specification", June 2008.

[MS-METAWEB] Microsoft Corporation, "MetaWeblog Extensions Protocol Specification", June 2008.

[MS-OCPROTO] Microsoft Corporation, "Office Client Protocols Overview", June 2008.

[MS-OFFICIALFILE] Microsoft Corporation, "Official File Web Service Protocol Specification", June 2008.

[MS-OFSGLOS] Microsoft Corporation, "Microsoft Office Server Master Glossary", June 2008.

[MS-OSALER] Microsoft Corporation, "Alerts Interop Protocol Specification", June 2008.

[MS-OSCO] Microsoft Corporation, "Office Server ClickOnce Manifest Structure Specification", July 2009.

[MS-OUTSPS] Microsoft Corporation, "Lists Client Sync Protocol Specification", June 2008.

[MS-PEOPS] Microsoft Corporation, "People Web Service Protocol Specification", June 2008.

[MS-PERMS] Microsoft Corporation, "Permissions Web Service Protocol Specification", June 2008.

[MS-PLSP] Microsoft Corporation, "Published Links Web Service Protocol Specification", June 2008.

[MS-PPSAS] Microsoft Corporation, "PerformancePoint Services AuthoringService Protocol Specification", July 2009.

[MS-PPSDECO] Microsoft Corporation, "PerformancePoint Services Decomposition Tree Protocol Specification", July 2009.

[MS-PPSRS] Microsoft Corporation, "PerformancePoint Services RenderingService Protocol Specification", July 2009.

[MS-PRIMEPF] Microsoft Corporation, "Deployment Package Format Specification", June 2008.

[MS-PUBWS] Microsoft Corporation, "Publishing Web Service Protocol Specification", June 2008.

[MS-SEARCH] Microsoft Corporation, "Search Protocol Specification", June 2008.

[MS-SITED3S] Microsoft Corporation, "Site Data 2003 Web Service Protocol Specification", June 2008.

[MS-SITEDATS] Microsoft Corporation, "Site Data Web Service Protocol Specification", June 2008.

[MS-SITESS] Microsoft Corporation, "Sites Web Service Protocol Specification", June 2008.

[MS-SLIDELI] Microsoft Corporation, "Slide Library Web Service Protocol Specification", June 2008.

[MS-SLXV] Microsoft Corporation, "Silverlight XAML Vocabulary Specification 2008", Silverlight XAML Vocabulary Specification 2008.

[MS-SPAFWI] Microsoft Corporation, "SharePoint Activity Feed Web Interfaces Protocol Specification", November 2009.

[MS-SPBEPO] Microsoft Corporation, "SharePoint Back-End Protocols Overview", June 2008.

[MS-SPDIAG] Microsoft Corporation, "SharePoint Diagnostics Web Service Protocol Specification", July 2009.

[MS-SPEMAWS] Microsoft Corporation, "SharePoint E-Mail Web Service Protocol Specification", June 2008.

[MS-SPLCHK] Microsoft Corporation, "SpellCheck Web Service Protocol Specification", June 2008.

[MS-SPRSS] Microsoft Corporation, "RSS 2.0 Format Extensions Specification", June 2008.

[MS-SPSCRWL] Microsoft Corporation, "SPSCrawl Web Service Protocol Specification", June 2008.

[MS-SPSTWS] Microsoft Corporation, "SharePoint Security Token Service Web Service Protocol Specification", July 2009.

[MS-SSAS9] Microsoft Corporation, "SQL Server Analysis Services Protocol Specification", June 2008.

[MS-STSSYN] Microsoft Corporation, "StsSync Structure Specification", June 2008.

[MS-SYS] Microsoft Corporation, "Windows System Overview", March 2008.

[MS-TDS] Microsoft Corporation, "Tabular Data Stream Protocol Specification", February 2008.

[MS-TMPLDISC] Microsoft Corporation, "Template Discovery Web Service Protocol Specification", July 2009.

[MS-UGS] Microsoft Corporation, "UserGroup Web Service Protocol Specification", June 2008.

[MS-UPIEWS] Microsoft Corporation, "User Profile Import and Export Web Service Protocol Specification", July 2009.

[MS-UPSDWS] Microsoft Corporation, "User Profile Social Data Web Service Protocol Specification", July 2009.

[MS-USPSWS] Microsoft Corporation, "User Profile Service Web Service Protocol Specification", June 2008.

[MS-USRPCH] Microsoft Corporation, "User Profile Change Log Web Service Protocol Specification", June 2008.

[MS-UTSP] Microsoft Corporation, "SharePoint Usage Tracking Stored Procedures Protocol Specification", July 2009.

[MS-VERSS] Microsoft Corporation, "Versions Web Service Protocol Specification", June 2008.

[MS-VIEWSS] Microsoft Corporation, "Views Web Service Protocol Specification", June 2008.

[MS-WDV] Microsoft Corporation, "Web Distributed Authoring and Versioning (WebDAV) Protocol: Client Extensions", March 2008.

[MS-WDVME] Microsoft Corporation, "Web Distributed Authoring and Versioning (WebDAV) Protocol: Microsoft Extensions", March 2008.

[MS-WDVMODUU] Microsoft Corporation, "Office Document Update Utility Extensions Protocol Specification", June 2008.

[MS-WEBDAVE] Microsoft Corporation, "Web Distributed Authoring and Versioning Error Extensions Protocol Specification", June 2008.

[MS-WEBSS] Microsoft Corporation, "Webs Web Service Protocol Specification", June 2008.

[MS-WPPS] Microsoft Corporation, "Web Part Pages Web Service Protocol Specification", June 2008.

[MS-WSSCAML] Microsoft Corporation, "Collaborative Application Markup Language (CAML) Structure Specification", June 2008.

[MS-WSSCAP] Microsoft Corporation, "Windows SharePoint Services Collaborative Application Protocol Specification", June 2008.

[MS-WSSHP] Microsoft Corporation, "HTTP Windows SharePoint Services Headers Protocol Specification", June 2008.

[MS-WSSO] Microsoft Corporation, "Windows SharePoint Services Overview", June 2008.

[MS-WSSREST] Microsoft Corporation, "ListData Data Service Protocol Specification", July 2009.

[MS-WSSTS] Microsoft Corporation, "Windows SharePoint Services: Technical Specification", June 2008.

[MS-WWSP] Microsoft Corporation, "Workflow Web Service Protocol Specification", June 2008.

可能会遇到的错误信息如下:

Error converting data type varchar to uniqueidentifier

或

conversion failed when converting from a character string to uniqueidentifier

你先需要将字符串转换为uniqueidentifier类型.

举例如下:

declare @guid uniqueidentifier 
select @guid = CAST('16d85cfe-360f-44af-bc79-33bc1e89b698' as uniqueidentifier)
exec proc_GetSiteUsage @guid

如果需要新创建一个GUID, 可以这样做:

declare @guid uniqueidentifier
set @guid= NEWID()
print 'Value of @guidis: '+ CONVERT(varchar(255), @guid)

参考:

Generate GUID (Unique Identifier) in SQL Server

http://www.dotnetspider.com/resources/4866-Generate-GUID-Unique-Identifier-SQL-Server.aspx

failed to convert parameter value from string to guid

http://social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/b3690c51-32fd-42cf-8c40-78407b9c4cc0

关于如何使用存储过程获得数据, 可以参考

http://www.informit.com/articles/article.aspx?p=31283&seqNum=4

关于CAST和Convert的区别, 可以参考

http://www.informit.com/articles/article.aspx?p=31283&seqNum=4

SharePoint提供了一种确定站点的使用(usage)的内建的方法. 因为站点的内容并不存在于文件系统中, IIS的logging对于确定Server的负载意义并不太大.

SharePoint内建的usage analysis可以用来确定站点的usage.

默认情况下, Usage Processing 和Loging是被关闭的. 当你开启了logging, 那么默认情况下log files的存储位置会在

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Logs

默认情况下SharePoint会为每一个web application创建一个log文件.

注意, logging和processing是两个独立的配置, 因为你可以仅开启logging而不开启processing. 这在你想要通过某些自定义的应用程序来处理这些信息的时候会比较有用.

log文件被创建并存储在以web application的GUID名字命名的文件夹下.  在这个文件夹之下, 还有按日期命名的子文件夹.

注意, 这些logging的信息被存储在内存中, 然后会在各种不同的情况下冲刷到磁盘文件上(比如说IIS重启).

典型的一条记录看起来像这样:

1404BB44-B1DB-44D3-9708-30AFB049393A 00:00:21 http://testsharepointserver/sites/test lists/tasks/active.aspx sharepoint\system   Mozilla/4.0 (compatible; MSIE 4.01; Windows NT; MS Search 5.0 Robot) 82C7B622-CDF7-4EF8-A21A-FE591A8D6F6A

第一个GUID是站点的ID, 之后是时间戳, URL, 请求的页面, 用户名, 浏览器, 最后是访问的web id.

为什么要使用SharePoint Usage Report呢? IIS的log不是也可以统计这一类的信息么?

因为当你每次从SharePoint站点下载一个文档的时候, 在IIS log中你不会看到这个文档的访问信息的记录. 取而代之的是把文档的字节流返回给客户的DLL文件-- owrsrv.dll

SharePoint Site Usage log文档的格式不适于直接阅读, 具体格式被记录在文章Usage Event Logging in Windows SharePoint Services 3.0中. 其中还包含有可以编译出解析该文档的工具程序的C++源代码.

Configure usage reporting

http://technet.microsoft.com/en-us/library/cc262541.aspx

Your Top 10 List...Or How To Gather Usage Statistics with SharePoint

http://www.bluedoglimited.com/SharePointThoughts/ViewPost.aspx?ID=129

Usage Event Logging in Windows SharePoint Services 3.0

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

当然了, 确定这些ID的方法, 可以去数据库里捞, 也可以用Object Model来输出, 但是最简单的方法还是在界面上点点就能看到.

1. 打开管理中心站点, 打开Application Management选项卡.

2. 点击Site Collection Administrators

3. 选择你想要查看的Site Collection. 在IE地址栏中, 你可以看到站点集的GUID.

资料来源:

http://hristopavlov.wordpress.com/2008/10/20/a-very-fast-method-to-get-the-site-collections-web-structure/ 

链接:

如何确定一个SharePoint列表的ID?

http://www.cnblogs.com/awpatp/archive/2010/01/28/1658714.html

http://www.cnblogs.com/awpatp/archive/2010/02/19/1669368.html

1. 打开管理中心站点.

2. 点击Application Management选项卡.

3. 点击Create or extend Web application.

4. 点击Extend an existing Web application

5. 选择一个Web Application.

6. 在浏览器的地址栏中, 可以发现你选择的Web application的GUID

7. 点击Cancel.

链接:

如何确定一个SharePoint列表的ID?

http://www.cnblogs.com/awpatp/archive/2010/01/28/1658714.html

AllMembershipCondition

======================

代表着一个匹配所有代码的membership condition. 这个类不能被继承.

这个membership condition通常被用做一个policy level的root code group, 以便于这个policy能够应用到所有的代码上.

http://msdn.microsoft.com/en-us/library/system.security.policy.allmembershipcondition.aspx

UrlMembershipCondition

======================

通过测试URL来确定一个assembly是否属于一个code group. 这个类不能被继承.

这里会考量完整的URL, 包括协议(HTTP, HTTPS, FTP) 和 文件. 比如说, http://www.fourthcoffee.com/process/grind.htm 就是一个完整的URL.

URLs可以被精确地匹配, 也可以在末尾指定一个通配符(wildcard)来匹配. 比如说, http://www.fourthcoffee.com/process/* 就是一个wildcard URL.

http://msdn.microsoft.com/en-us/library/system.security.policy.urlmembershipcondition.aspx

ZoneMembershipCondition

======================

通过测试起源的zone来确定一个assembly是否属于一个code group. 这个类不能被继承.

这里所指的zone可以用一个枚举变量来指定, 该枚举变量叫做SecurityZone, 它的成员有:

• MyComputer
• Intranet
• Trusted
• Internet
• Untrusted
• NoZone

具体是哪个zone, 可以使用Microsoft Internet Explorer的选项面板来配置.

http://msdn.microsoft.com/en-us/library/system.security.policy.zonemembershipcondition.aspx

StrongNameMembershipCondition

======================

通过验证程序集的强命名来确定一个程序集是否属于一个code group. 这个类不能被继承.

Strong names are well suited to specifying code assemblies to which you give a rich set of powerful permissions. Since strong names are cryptographically verified, attackers cannot impersonate rightful assemblies and use their permissions.

强明镜是非常适合确定那些你给了很多强大权限的code assemblies的. 因为强命名是通过加密来鉴定的, 攻击者不能模仿有权限的assemblies, 也不能使用它们的权限.

http://msdn.microsoft.com/en-us/library/system.security.policy.strongnamemembershipcondition.aspx

Code groups是构建code access security policy的砖块. 每一个policy level都包括一个可以拥有child code group的root code group. 每一个child code group都能有它们自己的child code groups. 这个行为可以扩展延伸到任意的层次上, 形成一棵树. 每一个code group都有一个membership condition可以确定是否一个给定的assembly属于它, 这个判断要基于assembly所给的证据. 只有那些membership condition与一个给定的assembly能够匹配的code groups, 它们自身和它们的child code groups能应用policy.

FirstMatchCodeGroup

=====================

允许security policy由一个code group的和第一个匹配的child code group的policy statement的联合来定义. 这个类不能被继承.

跟其他任何的code group一样, FirstMatchCodeGroup 仅在他的membership condition与一个assembly提供的evidence匹配的时候才应用policy. 如果有一个匹配, 他就按顺序测试每一个child的membership condition, 直到发现第一个匹配时停止. FirstMatchCodeGroup 的结果是root code group和第一个匹配的child code group的policy statement的联合

FirstMatchCodeGroup 的目的就是帮助application domain的宿主的编程应用来设定domain policy.

UnionCodeGroup

====================

代表着一个它的policy statement是当前codegroup的policy statement和所有它的匹配的child code groups的policy statement的组合的这么一种code group. 这个类不能被继承.

UnionCodeGroup是最常见的code group的类型. 所有匹配的child code group的policy statement(还有孩子的孩子的code groups)都与匹配的parent code group的permission set组合了起来. 从而, 如果它的membership condition匹配了, 这个code group形成了它的policy statement 与 它的所有的也与evidence匹配的child code group的policy statement 的联合.

UnionCodeGroup code groups are the code groups created by the CASPOL utility (see Code Access Security Policy Tool (Caspol.exe)) and the .NET Framework Configuration tool (see .NET Framework Configuration Tool (Mscorcfg.msc)).

UnionCodeGroup code groups是由CASPOL utility 创建的code groups. 更多信息参考下两个链接Code Access Security Policy Tool (Caspol.exe) NET Framework Configuration Tool (Mscorcfg.msc)

来源:

UnionCodeGroup

http://msdn.microsoft.com/en-us/library/system.security.policy.unioncodegroup.aspx

FirstMatchCodeGroup

http://msdn.microsoft.com/en-us/library/system.security.policy.firstmatchcodegroup.aspx