• Workflow Property

            <p>
            Parameters can be defined for a workflow (or custom activity) in two ways. You can implement a normal .NET class property, or you can use a dependency property. The property value for a dependency property is stored in a central repository, rather than being implemented as a normal instance variable in your class.
            </p>
    
  • SharePoint Form Authentication

    Here is an article about SharePoint Form Configuration. Basically, you need to modify the web.config of the content site and central admin site. But you should keep the central admin's role provider . Then you need go to central admin to change the web application's Authentication. One web application may be accessed in different zone, for example intranet and internet zone. You can config intranet access site to use windows authentication, and config the internet access site to use form authentication. But The web.config files of all access site need be modified to know the information of form authentication.</p>

    One thing to note is that you need to enable the PeoplePickerWildcards like the following.

  • Page Layouts

    What is page layouts. Let's see how page is used. First page layout is used to create page just like the Web Page template. But it has one more benefit "Field Control". Page Layout is inherit from Page directly or indirectly. To create a Page Layout you need to create a content type first, the parent content type of this content type is Page. Then you can add more column to this content type. Then you create Page layout based on the content type you just created, and the columns of that content type becomes field controls. You can add field controls to the page layout, you can add webpart zone the page layout. When creating page, you create page out of page layout instead of WebPart Page.

    age layouts have a special relationship with contetn types within a publishing site. Each page layout must be associated with exactly one content type. This content type must inherit from the Page content found in the Publishing Content Types group. This content types may have fields(columns) , it may also have a special workflow associated with in defining a special approval process for the press release.

    Keep in mind that content type only defines the schema and rules for the type of content; it does not address the presentation in any way. This is where page layouts come into play. Page layouts, when combined with a master page, define the rendering/look and feel of a requested page. In addition, developers can associate multiple page layouts iwth a single content type to give content owners the utmost control in selecting different rendering options for a particular page type.

    Moreover, content owners are not restricted to the page layout that is selected at the time of page creation. At any point in the future, even after the page has been published, a content owner can edit the page and chage the selected page layout. The only limitation is that the only page layouts availabe are those associated with the content type selected when the page was created.

  • Deploy web part

    1. Deploy the assembly containing the web part class to the site's hosting web application's bin folder or server's GAC

  • Master Page Content Placeholders

    The SharePoint default master page containes 32 different content placeholders used by the content pages throughout SharePoint sites. Not all of the 32 place holders are required in all custom master pages. In fact, the 8 provided master pages for publishing sites only contains 21 of 32 and one additional content place holder. They are