博客园_teamleader

CAML join

2012-02-05T14:24:00Z

参考： http://msdn.microsoft.com/zh-cn/library/ee539975.aspx

SPList list = web.Lists["Orders"];

SPQuery query = new SPQuery();

query.Joins = @"

<Join Type=’LEFT’ ListAlias=’customers’>
    <Eq>
      <FieldRef Name=’CustomerName’ RefType=’Id’ />
      <FieldRef List=’customers’ Name=’ID’ />
    </Eq>
</Join>

<Join Type=’LEFT’ ListAlias=’customerCities’>
    <Eq>
      <FieldRef List=’customers’ Name=’CityName’ RefType=’Id’ />
      <FieldRef List=’customerCities’ Name=’ID’ />
    </Eq>
</Join>
";

query.ProjectedFields = @"

<Field

Name=’CustomerCity’

Type=’Lookup’

List=’customerCities’

ShowField=’Title’ />

query.ViewFields = @"

query.Query = @"

<Where>

<Eq>

<Value Type='Text'>London</Value>

</Eq>

</Where>

SPListItemCollection items = list.GetItems(query);

通过 Wiz 发布

本文链接

ActivateOnDefault & AutoActivateInCentralAdmin feature 属性

2012-01-13T02:05:00Z

<?xml version="1.0" encoding="utf-8" ?>
<Feature Id="21003D96-D88E-42ed-AF97-2C4C22BFA3CF"
      Title="Test Web Application Feature"
      Description="I should be activated by default."
      Version="1.0.0.0"
      Scope="WebApplication"
      Hidden="false"
      xmlns="http://schemas.microsoft.com/sharepoint/"
      ActivateOnDefault="true"
      AutoActivateInCentralAdmin="true"
      AlwaysForceInstall="true">
</Feature>

ActivateOnDefault

Optional Boolean. TRUE if the Feature is activated by default during installation or when a Web application is created; FALSE if the Feature is not activated. This attribute equals TRUE by default. The ActivateOnDefault attribute does not apply to site collection (Site) or Web site (Web) scoped Features.

In general, Farm-scoped Features become activated during installation, and when a new Web application is created, all installed Web application-scoped Features in it become activated.

AutoActivateInCentralAdmin
Optional Boolean. TRUE if the Feature is activated by default in the Administrative Web site, site collection, or Web application. This attribute equals FALSE by default. The AutoActivateInCentralAdmin attribute does not apply to Farm-scoped Features.

通过 Wiz 发布

本文链接

Powershell点滴

2012-01-11T01:07:00Z

1. 如何表达枚举类型？

[StringSplitOptions] $option = "None"

[StringSplitOptions] $option = "RemoveEmptyEntries"

2. 在bat中调用执行Powershell文件（相对路径）

powershell.exe -Command "& {.\Script1.ps1}"

3. 加入-NoExit参数执行ps1文件

PowerShell.exe -NoExit " & ' C:\Program Files\...\sharepoint.ps1 ' "

4. 通用参数-confirm -ErrorAction

-Confirm $false

-ErrorAction "SilentlyContinue"

5. 创建对象并传递参数

$date = New-Object -TypeName System.DateTime -ArgumentList @(1882,7,4,0,0,0)

6. 创建COM对象

$ie = New-Object -ComObject "InternetExplorer.Application"

参考资料

http://www.cnblogs.com/fuhj02/archive/2010/12/03/PowerShell_Serials.html

通过 Wiz 发布

本文链接

判断某程序是64位还是32位

2012-01-10T09:04:00Z

1. 用代码判断本身

if (IntPtr.Size == 4)

{

// 32-bit

}

else if (IntPtr.Size == 8)

{

// 64-bit

}

2. 用代码判断正在运行的其他进程

http://stackoverflow.com/questions/1953377/how-to-know-a-process-is-32-bit-or-64-bit-programmatically

3. 不用代码判断任意exe，看第二个回复 http://blogs.technet.com/b/windowshpc/archive/2009/03/27/how-to-tell-if-a-exe-file-is-a-32-bit-or-64-bit-application-using-dumpbin.aspx

If you have a hex editor program, just open your file with it and shortly after the standard header intro stuff (like "This program cannot be run in DOS mode...") you will see either

"PE..L" (hex code: 504500004C) = 32 bit

"PE..d†" (hex code: 504500006486) = 64 bit

其实普通文本编辑器就行（比如notepad），打开之后搜索PE就会得到类似下面的结果

（64位）

（32位）

通过 Wiz 发布

本文链接

如何确定当前程序是否运行在Administrator模式下

2012-01-09T05:04:00Z

        WindowsIdentity identity = WindowsIdentity.GetCurrent();
        WindowsPrincipal principal = new WindowsPrincipal(identity);
        if (!principal.IsInRole(WindowsBuiltInRole.Administrator))
        {
            MessageBox.Show("You must run this application as administrator. Terminating.");
            Application.Exit();
        }

通过 Wiz 发布

本文链接

Sharepoint - 如何修改Web.Config文件

2012-01-06T03:45:00Z

http://msdn.microsoft.com/en-us/library/ms460914(v=office.14).aspx

http://claytonj.wordpress.com/2008/03/19/custom-webconfig-settings-in-sharepoint/

I have come across two ways to modify the web.config with custom nodes when using SharePoint. Yes, I know SharePoint solutions (.wsp) allow you to update web.config for safe control entries and other areas but this model doesn’t allow for any modification you want…lets say a WCF service <system.serviceModel>.

Option 1
You can use the SPWebConfigModification class that is inside the Microsoft.SharePoint.Administration.dll. Its purpose is to write nodes and attributes into the web.config file. This is a great approach when you want to deploy your custom settings via a features/solutions deployment.

SPWebService service = SPWebService.ContentService; SPWebConfigModification myModification = new SPWebConfigModification(); myModification.Path = “configuration/SharePoint/SafeControls”; myModification.Name = “SafeControl[@Assembly='MyCustomAssembly'][@Namespace='MyCustomNamespace'][@TypeName='*'][@Safe='True']“; myModification.Sequence = 0; myModification.Owner = “User Name“; myModification.Type = SPWebConfigModification.SPWebConfigModificationType.EnsureChildNode; myModification.Value = “<SafeControl Assembly=’MyCustomAssembly’ Namespace=’MyCustomNamespace’ TypeName=’*’ Safe=’True’ />”; service.WebConfigModifications.Add(myModification); /*Call Update and ApplyWebConfigModifications to save changes*/ service.Update(); service.ApplyWebConfigModifications();

http://msdn2.microsoft.com/en-us/library/microsoft.sharepoint.administration.spwebconfigmodification.aspx

So the above code would go in a FeatureReceiver event when activated and removed when deactivated.

Option 2
If you want to write custom nodes into a web.config when the web application is first created you could also do the following.

When a Web Application is first created WSS copies the web.config file from C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\CONFIG to the root folder of the Web Application. But before this file is copied it checks the CONFIG directory for any xml file that has a name in the format webconfig.*.xml and merges the contents with the web.config.

So you would create a file called webconfig.myname.xml and save it to C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\CONFIG

However, this approach will not modify existing web applications.

webconfig.myname.xml contents:
<?xml version=”1.0″ encoding=”utf-8″ ?>
<actions>
<add path=”configuration/appSettings”>
<add key=”MyFilePath” value=”C:\temp\path\” />
</add>
<add path=”configuration”>
<connectionStrings />
</add>
<add path=”configuration/connectionStrings”>
<remove name=”MySqlServerConnection” />
<add name=”MySqlServerConnection” connectionString=”server=[server];database=
db];Integrated Security=SSIP;” providerName=”System.Data.SqlClient” />
</add>
</actions>

So this needs to be completed on each web front end server. So to eliminate the manual approach again you can and package this up into a solution so WSS manages the deployment across the farm.

When creating a supplemental config file, the web.config modifications are NOT automatically mergeduntil you make a call to stsadm -o copyappbincontent.

You can also force this command to be run through a FeatureReceiver.

After exploring the stsadm tool in reflector I found that the copyappbincontent operation makes a call to SPWebApplication.WebService.ApplyApplicationContentToLocalServer()'

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

通过 Wiz 发布

本文链接

Sharepoint 2010 解决DFWP - Unable to display this Web Part 的问题

2012-01-06T03:16:00Z

参考这个：

http://support.microsoft.com/kb/2639184

简言之，微软为了防止dos攻击，在2011年5~8月份不知道哪个patch中将WebPart的xsl转换时间限制为1秒之内，如果超时就不显示该WebPart而给出如下错误消息：

"Unable to display this Web Part. To troubleshoot the problem, open this Web page in a Microsoft SharePoint Foundation-compatible HTML editor such as Microsoft SharePoint Designer. If the problem persists, contact your Web server administrator."

通常这种情况发生在字段很多（比如超过30个子段）的定制Form之上。

通常是第一次访问时出现这个错误，刷新页面后就正常显示了，估计是因为有缓存的缘故，如果不持续访问，过一段时间又会出现这个错误，估计是缓存失效了。

微软在这个KB中给出了解决方案：

1. 简化xls的代码，从而加快解析速度，于是不超时正常显示（xsl不是很好写啊）

2. 使用infopath form替代默认的Web Form （好像需要sharepoint企业版）

3. 继承系统自带的DataFormWebPart，创建并应用自己的WebPart（看似复杂实则最可行）

1) Sub class the DataForm Web Part. Override the following methods. Then Deploy the assembly.
Example:
public class customDFWP : DataFormWebPart
    {
        public override bool IsGhosted
        {
            get
            {
                return true;
            }
        }
        public override bool CanHaveServerControls
        {
            get
            {
                return true;
            }
        }
    }

2) Add a safe control entry to the web.config
Example: <SafeControl Assembly="customDFWP, Version=1.0.0.0, Culture=neutral, PublicKeyToken=963f869a440db619" Namespace="customDFWP" TypeName="*" Safe="True" AllowRemoteDesigner="True" SafeAgainstScript="False"/>

3) Add the following to the <tagMapping> element of the web.config
Example: <add tagType="Microsoft.SharePoint.WebPartPages.DataFormWebPart, Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" mappedTagType="customDFWP.customDFWP, customDFWP, Version=1.0.0.0, Culture=neutral, PublicKeyToken=963f869a440db619" />

4) Register the assembly on the form page.
Example: <%@ Register tagprefix="customDFWP" namespace="customDFWP" assembly="customDFWP, Version=1.0.0.0, Culture=neutral, PublicKeyToken=963f869a440db619" %>

5) On the form page find <WebPartPages:DataFormWebPart > and replace it with the new custom tag.
Example:<customDFWP:customDFWP>

http://social.msdn.microsoft.com/Forums/en-AU/sharepoint2010general/thread/44cfd798-be7a-4436-8786-bd44049e7def

通过 Wiz 发布

本文链接

OpenQuery

2011-11-29T13:16:00Z

@part = 'select top 1 * from ntp.dbo.penhold
where convert(varchar, request_date, 111) = ntp.dbo.fn_getpreweekday(''' + @ldate + ''')'

sp_execute_sql('select @var = count(1) from openquery(linkserver, ''' + @part + ''')')

通过 Wiz 发布

本文链接

Sharepoint Workflow Errors: Descriptions, resolutions and Workarounds

2011-11-17T07:47:00Z

转自blogspot地址（天朝不让访问）：

http://blog-sharepoint.blogspot.com/2010/02/sharepoint-workflow-errors-descriptions.html

The following table lists some of the common errors that can occur in a Workflow developed using SharePoint Designer. A short description of some of the likely causes for each error are also provided.

More detailed examples of the following scenarios where an error may occur in a SharePoint Designer workflow are also provided later in this post:

Exiting / Breaking a Looping Workflow using Workflow Errors
Workflow Permissions
Changing the name of a Document in a Document Library

If you come across a workflow error which is not explained below, please post details in a comment to this post. I will ammend the table and information below to include any additional errors, descriptions and possible causes to build a comprehensive list of workflow errors and resolutions when developing using SharePoint Designer.

Workflow Error Summary Table

Status / Event Type	Description	Outcome	Possible Cause(s)
Error	Error updating a list item	List Item Not Found	No item in the list matching the critera used to find a list item being updated.
Error	Error updating a list item	Access Denied	Permissions of the user who initiated the workflow don't allow them to modify data in the list item.
- Stopped Event Type: Error	Error Deleting a list item	Access Denied	Permissions of the user who initiated the workflow don't allow the user to delete items from the list.
Error	Error updating a list item	Unknown Error	Attempting to update Approval Status of a list item from a Workflow initiated by a user without approve permissions on the list/library.
- Failed on Start (retrying) - Stopped (Event Type: Error)	Error updating a list item	Unknown Error	Incorrect data types. Eg. attempting to include illegal characters in the filename of a document by appending the date to the filename. Permissions: Attempting to update a list item using the permissions of the user who initiated the workflow, who doesn't have access to update items in the list.
Error	An error has occured in ...Workflow Name		A previous workflow error has caused the workflow to halt.
Error	Error updating a list item	Document must be checked out	The document or list item being updated is in a list or library with force checkout enabled. First check out the document before making changes from a workflow, or disable force checkout. Note: Setting the Approval Status via a Workflow created using SharePoint Designer is not possible when Force Checkout is enabled.

Below are a series of scenarios where Workflows developed using SharePoint Designer will halt or stop due to a Workflow Error. An explanation of the cause of the error, as well as a resolution or workaround for the issue are also provided for each scenario. There are also instances where a workflow error can be caused intentionally to break a looping or repeating set of workflows once the looping sequence has completed (eg. processing all list items - see below).

Error Scenarios

Exiting / Breaking a Looping Workflow using Workflow Errors:

Looping Workflows developed using SharePoint Designer are often configured to stop due to a list item not being found. For example, when processing all items in a list using looping workflows, each instance may be initiated by updating a field from each item in the list being processed to initiate a separate iteration of the loop for each item. When all items have been processed, the workflow will not be able to find the next list item adn as a result will halt with an error ("Error updating a list item" : "List Item Not Found"). In cases similar to this, the workflow may not have stopped, as the workflow will sometimes retry the operation which caused an error depending on the type and severity of the error. Also, some errors will prevent new instances of the workflow initiating on the same list item with a workflow error. In scenarios where the workflow process should loop, this can be a problem as the workflow may not be able to move past the first iteration, or will cause the loop to stop if a workflow halts midway through the looping process.

Resolution / Workaround:

To ensure that a workflow loop continues until it has completed all required iterations, configuring the workflow initiate when an item is added to the list will result in each workflow initiated for each iteration of the loop being associated with a different list item. If one of the workflows halts due to an error (intentionally or unintentioanlly), the remaining iterations and components of the workflow can still continue as they will always be initiated on new list items added to the list. To help keep lists tidy, it may be a good idea to include an action late in the workflow to remove the current (temporary) list item once it has completed operations required for the current iteration and initiated the next iteration of the loop. After all items in the separate list have been processed. The workflow for the final list item created will stop due to a "List Item Not Found" error. As there will be not remaining items in the list which match the criteria required to find and initiate the next iteration, the loop will stop, breaking out of the looping sequence.

Workflow Permissions:

It is very common for developers of workflows in SharePoint to have elevated permissions on the SharePoint Site Collection in comparison to the general end-users of the SharePoint environment. This can lead to workflows not functioning as expected, or not working at all once in use, as testing may have been completed using the permissions of the workflow developer. To help prevent access / permission issues with workflows in SharePoint, you should always thoroughly test workflows using accounts with identical permissions to end-users of the SharePoint environment and workflow. In some cases this may require you to test using multiple accounts with varying permissions matching that of the end-users, or to change the permission level of one or two test accounts in order to test all possible scenarios.

As a workflow runs using the permissions of the user who initiated / triggered the workflow, in many cases during development it will be running using the credentials / permissions of the developer. If the developer has elevated access to components on the SharePoint site including lists associated with the workflow, the workflow will often function as expected during development, but not work once deployed into a production environment.

Resolution / Workaround:

When a workflow is initiated by a user with standard permissions, and the workflow needs to complete actions that would require the user to have a greater permission level on the site and lists, you can split the worklfow into components which are then initiated by users with the required permissions.

For example, a general user may make a change to a document stored in a document library with content approval enabled. A custom approval workflow is initiated to create and assign tasks to have the changes approved. As the Approval Task is created by the workflow running as the user who submitted the changes for approval, the user requires permissions that allow them to add items to the Approval Task list.

If using the "Collect data from user" action to get the approval status of the changes from an Approver, the workflow will continue to run as the user who initiated the worklfow (not the approver) once the approval status has been collected. This will result in a Workflow error if you try to update the approval status of the list item or document, as the user who made and submitted the changes for approval doesn't have approve permissions on the list/library. A solution for this problem is to split the workflow into two separate workflows. One to initiate the approval process and create the approval task item, and a second workflow on the Workflow task list which will be initiated by the approver when the approval status for the changes is set. You will not be able to use the "collect data from user" action, as this will result in the workflow continuing using the credentials of the user who initiated the workflow and a workflow error when attempting to set the Approval Status. Instead, you should create a new content type with only the fields required to collect the Approval Status for a modified list item and use the "Create List Item" action to create the Approval Task. Once created, associate the content type with a task or other list type, making it the default and only content type available on the "New" menu for the list. In the workflow associated with the content approval enabled list, you should use the "Create List Item" action to add an Approval Task item to the task list, then complete the workflow (Stop).

The Second workflow associated with the task list should be configured to initiate when an item in the Approval Task list is modified. The first step in the workflow should be to check to see if the Content approval status has been set by the approver. If not, then the workflow can stop as it will be reinitiated when the approval status is updated by an approver. If the approval Status has been set, then the workflow can continue to update the Approval Status of the list item or document that was changed and submitted for approval. The approval status can now be set by the workflow as it will be running using the permissions of the approver, not the user who initiated the approval process.

Column Data Types & Limitations

Attempting to set the value of a column in SharePoint that requires a specific data type such as a List Item ID, date or filename (Name) will result in a Workflow error when the incorrect data is assigned to a field/column in the list item or document. When developing workflows using SharePoint Designer, restrictions have been implemented to help ensure that the correct data type is used when setting workflow variables or fields in a list item. For example, when setting the value of a date/Time field, only a date variable or field can be set as the new date value. Similarly, when working with list items in SharePoint from a workflow, SharePoint Designer uses the List Item ID data type when retrieving or storing the ID of the current or another list item to ensure that only one (unique) item is returned.

Changing the name of Documents in a Document Library from a Workflow

- Difference between the "Name" and "Name (for use in forms)" fields

- Illegal / Special Characters in Document Filenames causing workflow errors.

- How to use calculated columns to remove illegal / special characters from a date or other field to be set or included in the document filename.

The "Name" and "Name (for use in forms)" columns in a SharePoint document library both refer to the same data, being the filename of the document of file, but function differently when updated by a Workflow Developed using SharePoint Designer. The main difference when using the Name columns in a Workflow is that the file extension for the document is included when using the "name (for use in forms)" column, but not the "Name" column.

Name - Doesn't include file extension
Name (for use in forms) - Includes file extension

When setting the value for the "Name" or "Name (for use in forms)" fields, special / illegal characters need to be considered, as the workflow will stop with an "Error updating a list item" error, with the outcome "Unknown Error". This is due to the fact the SharePoint doesn't allow specific characters to be included in the Name (filename) of a document stored in a Document Library. See Illegal Characters in SharePoint Document Libraries for more information about non-supported special characters for filenames in SharePoint.

Use calculated columns to format the created date to be appended to the filename (Name) of a document or form:

1. Configure a calculated column on the Sharepoint document library that formats the created date as a string with no illegal / special characters, that can then be included in the filename of the document.

Calculated Column: Generate a text string containing the created date in a specific format (dd-mm-yyyy : 03-02-2010)

=TEXT([Created],"dd-mm-yyyy")

2. Configure a workflow to append the value from the calculated column to the "Name (for use in forms)" fields of the document.

To append the date to an existing filename, you will need to use the value from the "Name" column, as it will not include the file extension. You would do this using the "Build dynamic string" workflow action, which would first take the original filename (without the file extension), then append the value from the calculated column containing the formatted date. The file extension can be included in the new filename string, but is not required. Once the new filename have been generated, you can set the "Name (for use in forms)" field for the current item using the "Update list Item" action, or the "Set field in current item" action.

Related:
Troubleshoot workflow errors

Access Denied when trying to upload multiple files to a SharePoint Library when one of the files contains an illegal character.

Published by Wiz

本文链接

Master Pages in SharePoint 2010

2011-10-26T00:54:00Z

v4.master (default for 2010)

minimal.master (for Office 2010 Web Applications and SharePoint Server 2010 Search Center)

default.master (for 2007 upgrade)

nightandday.master (Available in SharePoint Server 2010)

直接将Search Center的master page切换到v4.master会有问题，Sharepoint Designer 2010 Unleashed书中有解决方案的链接

Published by Wiz

本文链接