1. The Rendering Template for the Survey List is in the defaulttemplates.ascx control under 12/Template/Control template.

2. The rendering template ID is “ViewToolBar”. This template renders the "Respond to this Survey", Actions menu and Settings menu in the toolbar.

3. This template is a generic template which is used by Other lists as well.

4. The template is given below :

<SharePoint:RenderingTemplate ID="ViewToolBar" runat="server">

<Template>

<wssuc:ToolBar CssClass="ms-menutoolbar" EnableViewState="false" id="toolBarTbl" ButtonSeparator="<img src='/_layouts/images/blank.gif' alt=''>" RightButtonSeparator="&nbsp;&nbsp;" runat="server">

<Template_Buttons>

<SharePoint:NewMenu AccessKey="<%$Resources:wss,tb_NewMenu_AK%>" runat="server" />

<SharePoint:ActionsMenu AccessKey="<%$Resources:wss,tb_ActionsMenu_AK%>" runat="server" />

<SharePoint:SettingsMenu AccessKey="<%$Resources:wss,tb_SettingsMenu_AK%>" runat="server" />

</Template_Buttons>

<Template_RightButtons>

<SharePoint:PagingButton runat="server"/>

<SharePoint:ListViewSelector runat="server"/>

</Template_RightButtons>

</wssuc:ToolBar>

</Template>

</SharePoint:RenderingTemplate>

5. "Respond to this Survey" is rendered by <SharePoint:NewMenu AccessKey="<%$Resources:wss,tb_NewMenu_AK%>" runat="server" />.

6. We cannot modify OOB defaulttemplates.ascx as this would be unsupported.

7. Make a copy of defaulttemplates.ascx under CONTROL TEMPLATES FOLDER of 12 hive and rename it to CustomDefaultTemplates.ascx

8. To hide “Respond to this Survey” if a user has already responded to the survey, Create a class which inherits from the Microsoft.Sharepoint.WebControls.NewMenu.

9. In this override CreateChildControls and have your logic to hide unhide "Respond to this Survey" based on your need.

10. Build the class library and install the dll to the GAC.

11. Modify the “ViewToolBar” in the custom ascx such that to render your custom "Respond to this Survey" menu from the class library you created.

(Note : You need to add your assembly reference and register the tag prefix in the Custom ascx control.)

The following is the snippet from the custom ascx control :

<SharePoint:RenderingTemplate ID="CustomViewToolBar" runat="server">

<Template>

<wssuc:ToolBar CssClass="ms-menutoolbar" EnableViewState="false" id="toolBarTbl" ButtonSeparator="<img src='/_layouts/images/blank.gif' alt=''>" RightButtonSeparator="&nbsp;&nbsp;" runat="server">

<Template_Buttons>

<CustomSurvey:SurveyMenu ID="SurveyID" runat="server"></CustomSurvey:SurveyMenu>

<SharePoint:ActionsMenu AccessKey="<%$Resources:wss,tb_ActionsMenu_AK%>" runat="server" />

<SharePoint:SettingsMenu AccessKey="<%$Resources:wss,tb_SettingsMenu_AK%>" runat="server" />

</Template_Buttons>

<Template_RightButtons>

<SharePoint:PagingButton runat="server"/>

<SharePoint:ListViewSelector runat="server"/>

</Template_RightButtons>

</wssuc:ToolBar>

</Template>

</SharePoint:RenderingTemplate>

12. Next step is to render the custom rendering template to the "Survey List" so that the custom "Respond to this Survey" menu will be rendered in the toolbar.

13. For this the "ToolbarTemplate" property of the View should be changed in the schema.xml file of the Survey List definition.

14. As modifying the OOB files are not supported, Copy the “SurveyList” folder from 12/Template/Features and paste in the same place as “CustomSurveysList”.

Change the feature ID of the “CustomSurveyList”

15. Open the schema.xml file available under survey folder of “CustomSurveysList” and add the “ToolbarTemplate=CustomViewToolBar” attribute to the “View BaseID=0”.

16. Sample attached : <View BaseViewID="0" FreeForm="TRUE" ReadOnly="TRUE" Type="HTML" ToolBarTemplate=" CustomViewToolBar ">

17. Install and activate "CustomSurveysList"

18. Create a Survey List using CustomSurveyList template and we should be able to achieve the functionality as required.

CODE FOR CUSTOM ascx file
---------------------------------
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using Microsoft.SharePoint;
using Microsoft.SharePoint.WebControls;
using System.Web;
using Microsoft.SharePoint.Utilities;
using System.Globalization;

namespace CustomSurveyMenu
{
    public class SurveyMenu : NewMenu
    {

        protected override void CreateChildControls()
        {
            try
            {
                string valueToEncode = SPResource.GetString("ToolBarMenuRespondToSurvey", new object[0]);
                SPLinkButton child = new SPLinkButton();
                child.ID = "diidIONewItem";
                child.Text = SPHttpUtility.HtmlEncode(valueToEncode);
                child.ToolTip = valueToEncode;
                child.ImageUrl = "/_layouts/images/NewItem.gif";
                child.HoverCellActiveCssClass = "ms-buttonactivehover";
                child.HoverCellInActiveCssClass = "ms-buttoninactivehover";
                child.Permissions = SPBasePermissions.EmptyMask | SPBasePermissions.AddListItems;
                child.PermissionContext = PermissionContext.CurrentFolder;
                child.RenderContext = base.RenderContext;
                child.NavigateUrl = SPContext.Current.Web.Url + "/Lists/" + SPContext.Current.List.Title + "/NewForm.aspx?Source=" + SPHttpUtility.HtmlEncode(SPContext.Current.Web.Url + "/" + SPContext.Current.List.Views["Overview"].Url);
                child.AccessKey = (string)HttpContext.GetGlobalResourceObject("wss", "tb_NewMenu_AK", CultureInfo.CurrentUICulture);

                SPList oList = SPContext.Current.List;
                SPListItemCollection oListItemColl = oList.Items;

                SPUser oUserNew = this.Web.CurrentUser;
                string strUserName = oUserNew.Name;

                foreach (SPListItem oItem in oListItemColl)
                {
                    string strCreatedBy = oItem["Created By"].ToString().Trim();
                    string[] SplitCreated = strCreatedBy.Split(new Char[] { '#' });

                    string strModifiedBy = oItem["Modified By"].ToString().Trim();
                    string[] SplitModified = strModifiedBy.Split(new Char[] { '#' });

                    if (Convert.ToString(SplitCreated[1]).ToUpper() == strUserName.ToUpper() && oItem["Completed"].ToString().ToUpper() == "1" && Convert.ToString(SplitModified[1]).ToUpper() == strUserName.ToUpper())
                    {
                        child.Visible = false;
                    }
                }

                this.Controls.Add(child);
            }
            catch (Exception ex)
            {
                // PUT YOUR LOGIC TO CATCH EXCEPTION. Whether you would want to write it into a txt file etc..
            }
        }
    }
}

The OOB page isn’t accessible, even if users put the actual url (layouts/mngsiteadmin.aspx") in the browser and try accessing it.

Is easy to implement and supported.

The following sample approach can be tested :

<Sample-Code>

public class MasterPageModuleHandler : IHttpModule

    {

public void Init(HttpApplication context)

        {

            context.BeginRequest += new EventHandler(context_BeginRequest);

        }

void context_BeginRequest(object sender, EventArgs e)

        {

// throw new Exception("The method or operation is not implemented.");

            HttpApplication oApp = (HttpApplication)sender;

if (oApp.Request.RawUrl.Contains("/_layouts/mngsiteadmin.aspx"))

            {

                oApp.Response.Redirect(oApp.Request.RawUrl.Remove(oApp.Request.RawUrl.LastIndexOf("/")) + "/custom/SfMngSiteAdmin.aspx");

            }

        }

public void Dispose()

        {

        }

    }

</Sample-Code>

1. Build the Custom HTTP Module DLL and place it in the GAC

2. Assuming that a custom folder has been created under Layouts folder, ensure that custom-mngsiteadmin.aspx is present there.

3. Add the web.config entry for the custom HTTPModule in the config file of Web application

Find the HttpModules section in the web.config and add the following entry

<add name="HTTPModuleSPFileCache" type="HTTPModuleSPFileCache.CSetFileCache, HTTPModuleSPFileCache, Version=1.0.0.0, Culture=neutral, PublicKeyToken=<your key here>" />

4. Do an IISRESET.

Note: By putting a custom httpmodule in place, instead of normal 200 HTTP status, we get a HTTP 302 (Moved) and then a 200. No issues of performance hit have been reported , in using this approach, and you might want to test this one.

Option 2: Unlike Document Libraries\Lists, where the ToolBar is rendered through Templates defined in ControlTemplates.ascx, the Settings ToolBar for User.aspx is defined in the .aspx like below :

<SharePoint:FeatureMenuTemplate id="MenuTemplateSettings" LargeIconMode="TRUE" runat="server"

Location="Microsoft.SharePoint.User"

GroupId="SettingsMenu"

>

<SharePoint:MenuItemTemplate id="MenuItemSiteAdmins" runat="server" Text="<%$Resources:wss,people_siteadmins%>"

Description="<%$Resources:wss,people_siteadminsdescription%>"

ClientOnClickNavigateUrl="~site/_layouts/mngsiteadmin.aspx" Visible=false MenuGroupId="300" Sequence="100" />

MenuItemSiteAdmins is the ID of the the template responsible for rendering below menu :

So, to be able to override this behavior, I have to create a custom User.aspx page and override the link url to point to custom- mngsiteadmin.aspx page,Like below :

<SharePoint:FeatureMenuTemplate id="MenuTemplateSettings" LargeIconMode="TRUE" runat="server"

Location="Microsoft.SharePoint.User"

GroupId="SettingsMenu"

>

<SharePoint:MenuItemTemplate id="MyMenuItemSiteAdmins" runat="server" Text="<%$Resources:wss,people_siteadmins%>"

Description="<%$Resources:wss,people_siteadminsdescription%>" ClientOnClickNavigateUrl="~site/_layouts/custommngsiteadmin.aspx" Visible=true MenuGroupId="300" Sequence="100" />

So, modifying ClientOnClickNavigateUrl and Visible both  - does the trick.

Next step would be to correct all places where user.aspx appears, to actually point to custom user.aspx. (As I cannot modify OOB User.aspx, I basically have to create a custom copy of it, and then

Correct all those menu-items\links  which point to User.aspx)

Two of such places ,that I can enumerate are :

1. Site Permissions link in QuickLaunch on People.aspx

2. Site Permissions link in QuickLaunch on  groups.aspx

Just as an e.g, to add custom User.aspx to People.aspx – we again have to create a custom People.aspx, and replace this line :

<asp:MenuItem Text="<%$Resources:wss,people_sitepermissions%>" NavigateUrl="user.aspx"/>

With :

<asp:MenuItem Text="<%$Resources:wss,people_sitepermissions%>" NavigateUrl="cuser.aspx"/>

So, the approach requires wide customization and there is no easy way to achieve this (none- as easy as Option1 above).

SPQuery without RowLimit property set would fire the same the query.

I have not listed all the API calls which would fire the above query.

--------------

SiteData.SiteData srvSiteData = new SiteData.SiteData();
srvSiteData.Credentials = System.Net.CredentialCache.DefaultCredentials;
string items = srvSiteData.GetListItems("{48414507-4436-4D47-BE59-9834D33F2B52}","<Query><OrderBy><FieldRef Name=\"Modified\" Ascending=\"True\"></FieldRef></OrderBy></Query>",
"<FieldRef Name=\"Title\"/><FieldRef Name=\"Modified\"/>", 100);

If the Query looks like

<Query><OrderBy><FieldRef Name=\"Modified\" Ascending=\"True\"></FieldRef></OrderBy></Query> the orderby would not work.

Change the XML Query to
<OrderBy><FieldRef Name=\"Modified\" Ascending=\"True\"></FieldRef></OrderBy>

Build and deploy the project attached to this post.

Create a custom list and create a column of Custom field control added by the project. (SimpleTextFieldField)
3. Open SPD.
4. Go to File -- Open Project -- Select the URL of the site.
5. Expand the Lists tree in the Left pane and expand the List which was created in step 2
6. Double Click on NewForm.aspx of the list.
7. Switch to Split mode of NewForm.aspx in SPD.
8. Select the ListForm Webpart in NewForm.aspx page
9. After </WebPartPages:ListFormWebPart> tag hit enter.

10. Go to Insert Menu -- SharePoint Controls -- Custom List Form. If Custom List Form option is not enabled save the NewForm.aspx and try again.

11. A pop up window appear where you can select the List which we created in step 2 and let the Content Type to use for from be selected to Item, check the radio button "New item form (used to add new items to the list).

12. Right click on List Form webpart -- Webpart properties -- Layout -- Select both checkboxes "Hidden" and "Close the webpart" -- Click OK button
13. Save the NewForm.aspx page in SPD.
14. Open IE, browse to the list created -- Click on New -- Add entry for Title column and a value for the Custom field control which we have added and click OK
14. It will come back to AllItems.aspx where we can find that the value entered to the custom column is blank.

Schema of Title Field
---------------------------
<Field ID="{fa564e0f-0c70-4ab9-b863-0177e6ddd247}" Type="Text" Name="Title" DisplayName="Title" Required="TRUE" SourceID="https://schemas.microsoft.com/sharepoint/v3" StaticName="Title" FromBaseType="TRUE" ColName="nvarchar1"/>

Schema of Custom Field control
-------------------------------------
<Field Type="SimpleTextFieldField" DisplayName="huha" Required="TRUE" ID="{9df3f794-4a49-4019-a41a-3d29ae500903}" SourceID="{e68e397e-fb36-4971-955e-904f56a57d10}" StaticName="huha" Name="huha" ColName="nvarchar3" RowOrdinal="0"/>

Schema of Field added through UI
---------------------------------------------
<Field Type="Text" DisplayName="BoomCol" Required="FALSE" MaxLength="255" ID="{ef0b772f-af19-467a-9afd-2920ba1b10d8}" SourceID="{e68e397e-fb36-4971-955e-904f56a57d10}" StaticName="BoomCol" Name="BoomCol" ColName="nvarchar4" RowOrdinal="0"/>

This behaviour was because, the TextBox we exposed is a child control, the main control is SPTextFieldFieldControl. When you convert to a DataForm webpart, these custom controls will be replaced by the SPForm controls.  This control does not identify what is the original value. If you look inside the SPTextFieldFieldControl, I do have HtmlTable, LiteralControl, TextBox etc. So now we get the inner control value and set the “Text/Value” property of the main control(SPTextFieldFieldControl)

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

Code changes for SimpleTextField attached below.

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

using System;
using System.Runtime.InteropServices;

using Microsoft.SharePoint;
using Microsoft.SharePoint.WebControls;
using System.Web.UI.HtmlControls;
using System.Web.UI;
using System.Web.UI.WebControls;

namespace SimpleTextFieldControl
{
    // TODO: Replace, as needed, "TextField" with some other class derived from Microsoft.SharePoint.WebControls.BaseFieldControl.
    [CLSCompliant(false)]
    [Guid("f6fdae87-e10d-4aa6-bd80-db14d41a19d6")]
    public class SimpleTextFieldFieldControl : TextField
    {
        private HtmlTable table;
        private TextBox txtName;
        private string _textValue;
        private void RefreshValues()
        {
            if (txtName != null && this.Context != null && this.Context.Request != null)
            {
                foreach (string key in this.Context.Request.Form.Keys)
                {

                    if (key.ToLower() == txtName.UniqueID.ToLower())
                    {
                        string[] enteredValue = this.Context.Request.Form.GetValues(key);
                        textBox.Text = enteredValue[0];
                        _textValue = textBox.Text;
                    }
                }
            }
        }

        protected override void CreateChildControls()
        {
            base.CreateChildControls();

            this.table = new HtmlTable();

            HtmlTableRow row = new HtmlTableRow();
            table.Rows.Add(row);

            HtmlTableCell cell = null;

            if (this.ControlMode == SPControlMode.Edit ||
                this.ControlMode == SPControlMode.New)
            {
                cell = new HtmlTableCell();
                cell.ColSpan = 2;
                cell.Attributes["class"] = "ms-formdescription";
                cell.InnerText = "Enter a Text:";

                row.Cells.Add(cell);

                row = new HtmlTableRow();
                cell = new HtmlTableCell();

                // a text field
                this.txtName = new TextBox();
                // Get the current value of the field.
                string currentValue = (string)this.ItemFieldValue;

                if (currentValue != null && currentValue != string.Empty)
                {
                    this.txtName.Text = currentValue;
                }

                cell.Controls.Add(this.txtName);
                row.Cells.Add(cell);
                table.Rows.Add(row);
            }

            cell = new HtmlTableCell();

            LiteralControl literalControl = new LiteralControl();

            string text = null;
            object textObject = this.ItemFieldValue;

            if (textObject != null)
            {
                text = (string)textObject;
            }

            if (text == null || text == string.Empty)
            {
                text = this.txtName.Text;
            }

            literalControl.Text = text;

            cell.Controls.Add(literalControl);
            row.Cells.Add(cell);

            base.Controls.Add(table);
        }

        public override string Text
        {
            get
            {
                RefreshValues();
                return _textValue;
            }
            set
            {
                base.Text = value;
            }
        }

        public override void UpdateFieldValueInItem()
        {
            base.UpdateFieldValueInItem();
            try
            {
                this.Value = this.txtName.Text;
                this.ItemFieldValue = this.Value;
            }
            catch
            {
                throw new Exception("error in text field") ;
            }
        }

        protected override void Render(HtmlTextWriter output)
        {
            this.table.RenderControl(output);
        }

    }   
}

1. All the templates for the NewForm, EditForm and DispForm (Item Form pages) are
defined in the defaulttemplates.ascx

2. This templates are associated with the List through content type

3. The FormTemplates of the NewForm, EditForm and DispForm are definied in the
content type as folows

<ContentType ID="0x01"
Name="$Resources:Item"
Group="$Resources:List_Content_Types"
Description="$Resources:ItemCTDesc"
Version="0">
<FieldRefs>
<FieldRef ID="{fa564e0f-0c70-4ab9-b863-0177e6ddd247}" Name="Title"
Required="TRUE" ShowInNewForm="TRUE" ShowInEditForm="TRUE"/> <!-- Title -->
</FieldRefs>
<XmlDocuments>
<XmlDocument
NamespaceURI="https://schemas.microsoft.com/sharepoint/v3/contenttype/forms">
<FormTemplates
xmlns="https://schemas.microsoft.com/sharepoint/v3/contenttype/forms">
<Display>ListForm</Display>
<Edit>ListForm</Edit>
<New>ListForm</New>
</FormTemplates>
</XmlDocument>
</XmlDocuments>
</ContentType>

4. The "ListForm" template which have been in the above Content Type you can find
it in the DefaultTemplates.ascx control

5. Create a custom Defaulttemplates.ascx and create the custom rendering template
based on the ListForm and make ur changes (Including or Excluding control) Note :
ListFieldIteratorControl is the one which renders the Fields for the List in the
item form pages

6. Following are the steps to create custom defaulttemplates.ascx

1. Create a new custom Template: say name: CustDefaultTemplates.ascx and save it
in the folder: C:\Program Files\Common Files\Microsoft Shared\web server
extensions\12\TEMPLATE\CONTROLTEMPLATES

a. Open DefaultTemplates.ascx file (located at the same path mentioned above). Copy
the following lines from the file and add to the CustDefaultTemplate.ascx

<%@ Control Language="C#" AutoEventWireup="false" %>
<%@Assembly Name="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c" %>
<%@Register TagPrefix="SharePoint" Assembly="Microsoft.SharePoint,
Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"
namespace="Microsoft.SharePoint.WebControls"%>
<%@Register TagPrefix="SPHttpUtility" Assembly="Microsoft.SharePoint,
Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"
namespace="Microsoft.SharePoint.Utilities"%>
<%@ Register TagPrefix="wssuc" TagName="ToolBar"
src="~/_controltemplates/ToolBar.ascx" %>
<%@ Register TagPrefix="wssuc" TagName="ToolBarButton"
src="~/_controltemplates/ToolBarButton.ascx" %>

b. Now, in DefaultTemplates.ascx look for line:
<SharePoint:RenderingTemplate ID="ListForm" runat="server">

c. Copy this complete node and paste in the CustDefaultTemplate.ascx below the
lines added above.

d. Now, change the ID="ListForm" to any other ID; example: ID="CustListForm" in
CustDefaultTemplate.ascx

e. Save the File CustDefaultTemplate.ascx

7. Create a custom content type and render the "CustomListForm" as the template for
the New, Edit and Display form.

8. Attache the custom content type with the List.

9. Now whenever you create new, Edit and Dispform for this List it will render your
custom template instead of OOb template.

The following screenshot shows a page with “Submit for Approval” button enabled when any approval workflow is attached with the pages library :

           <ConsoleNode Action="cms:OneClickPublishAction" DisplayText="cms,console_publish" HideStates="ContentApprovalEnabledFalse" ImageUrl="/_layouts/images/cnspub16.gif" UseResourceFile="true" ID="saApprovePublish"/>

           <ConsoleNode Action="cms:PublishWithCommentAction" UseResourceFile="true" ID="saPublishWithComment"/>          

           <ConsoleNode Action="cms:CancelApprovalRequestAction" DisplayText="cms,console_cancelapprovalrequest" HideStates="IsApprovalWorkflowConfiguredTrue" ImageUrl="/_layouts/images/cnsca16.gif" UseResourceFile="true" ID="saCancelApproval"/>

           <ConsoleNode Action="cms:CancelApprovalWorkflowRequestAction" DisplayText="cms,console_cancelapprovalrequest" HideStates="IsApprovalWorkflowConfiguredFalse" ImageUrl="/_layouts/images/cnsca16.gif" UseResourceFile="true" ID="saCancelApprovalWorkflow"/>

           <ConsoleNode Action="cms:CancelSchedulingAction" DisplayText="cms,console_cancelscheduling" UseResourceFile="true" ID="saCancelScheduling"/>

           <ConsoleNode Action="cms:UnpublishAction" DisplayText="cms,console_unpublish" ImageUrl="/_layouts/images/unpub.gif" UseResourceFile="true" ID="saUnpublish" />

           <ConsoleNode IsSeparatorImage="True" UserRights="EmptyMask" />

           <ConsoleNode Action="cms:ApproveOrDeclineAction" DisplayText="cms,console_approveworkflow" ImageUrl="/_layouts/images/apprj.gif" UseResourceFile="true" ID="saApproveOrDecline"/>

           <ConsoleNode Action="cms:WorkflowTasksAction" UseResourceFile="true" ImageUrl="/_layouts/images/cnsvt16.gif" ID="saWorkflowTasks"/>

           <ConsoleNode IsSeparatorImage="True" UserRights="EmptyMask" />

           <ConsoleNode Action="cms:WorkflowStatusAction" DisplayText="cms,console_workflowstatustracking" UseResourceFile="true" ID="saWorkflowStatus"/>

           <ConsoleNode Action="cms:WorkflowStartAction" DisplayText="cms,console_workflowstart" ImageUrl="/_layouts/images/workflows.gif" UseResourceFile="true" ID="saWorkflowStart"/>

       </ConsoleNode>

In the QuickAccess.xml file you can find the Console Node which renders the “SubmitForApproval” button as follows : This doesn’t work fine with the workflows associated with ASPX pages.

<ConsoleNode Sequence="20" Action="cms:SwitchToAuthoringModeAction" DisplayText="cms,siteactions_editpage_displaytext" UseResourceFile="true" ImageUrl="/_layouts/images/edit.gif" HideStates="PageHasCustomizableZonesFalse|PageHasFieldControlsFalse" RequiredStates="InEditModeFalse|IsFormPageFalse|IsDocLibListItemTrue|InSharedView|IsCheckedOutToOtherUserFalse" ID="qaEditPage" />

       <ConsoleNode Sequence="40" Action="cms:SwitchToPublishedModeAction" DisplayText="cms,console_reviewmode" UseResourceFile="true" ImageUrl="/_layouts/images/saveitem.gif" RequiredStates="InEditModeTrue|IsDocLibListItemTrue|InSharedView|SaveConflictExistsFalse|CheckOutRequiredFalse" ID="qaReviewMode"/>

       <ConsoleNode Sequence="60" Action="cms:CheckInAction" UseResourceFile="true" ImageUrl="/_layouts/images/checkin.gif" ID="qaCheckin"/>

       <ConsoleNode Sequence="80" Action="cms:PublishAction" UseResourceFile="true" HideStates="MinorVersionsEnabledFalse" ID="qaPublish"/>

       <ConsoleNode Sequence="100" Action="cms:ApproveAction" DisplayText="cms,console_approve" UseResourceFile="true" ImageUrl="/_layouts/images/cnsapp16.gif" ID="qaApprove"/>

       <ConsoleNode Sequence="101" Action="cms:WorkflowApproveAction" DisplayText="cms,console_approve" UseResourceFile="true" ImageUrl="/_layouts/images/cnsapp16.gif" ID="qaWorkflowApprove"/>

       <ConsoleNode Sequence="120" Action="cms:OneClickPublishAction" DisplayText="cms,console_publish" UseResourceFile="true" ImageUrl="/_layouts/images/cnspub16.gif" ID="qaApprovePublish"/>

       <ConsoleNode Sequence="140" Action="cms:DeclineAction" DisplayText="cms,console_declineworkflow" UseResourceFile="true" ImageUrl="/_layouts/images/cnsrej16.gif" ID="qaDecline"/>

       <ConsoleNode Sequence="141" Action="cms:WorkflowDeclineAction" DisplayText="cms,console_declineworkflow" UseResourceFile="true" ImageUrl="/_layouts/images/cnsrej16.gif" ID="qaWorkflowDecline"/>

       <ConsoleNode Sequence="160" Action="cms:WorkflowTasksAction" UseResourceFile="true" ImageUrl="/_layouts/images/cnsvt16.gif" ID="qaWorkflowTasks"/>

       <ConsoleNode Sequence="180" Action="cms:SharedViewAction" DisplayText="cms,console_sharedview" ImageUrl="/_layouts/images/allusr.gif" UseResourceFile="true" ID="qaSharedView"/>

In the above highlighted nodes you can find the difference that the Console Action are rendered from different class. The One which works fine is rendered from the cms:PublishWithCommentAction and the one which doesn’t work with the workflows associated with the ASPX pages is rendered from cms:PublishAction.

Note : CMS is the tag prefix used as follows in the EditingMenu.xml and QuickAccess.xml files

<references>

       <reference TagPrefix="cms" assembly="Microsoft.SharePoint.Publishing, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" namespace="Microsoft.SharePoint.Publishing.WebControls.EditingMenuActions" />

   </references>

So now we concluded that the node rendered from the cms:PublishWithCommentAction class works fine. So by using the customquickaccess.xml existing in the Mater Page gallery we can delete the existing node (cms:PublishAction) from the quick access and can “Add” the cms:PublishWithCommentAction in the quick access.

Following is the content of the customquickaccess.xml which will delete the non working node and will add the working node in the quick access area.

<?xml version="1.0" encoding="utf-8" ?>

<Console>

      <references>

            <reference TagPrefix="cms" assembly="Microsoft.SharePoint.Publishing, Version=12.0.0.0, Culture=neutral,

PublicKeyToken=71e9bce111e9429c" namespace="Microsoft.SharePoint.Publishing.WebControls.EditingMenuActions" />

      </references>

      <structure>

            <ConsoleNode Action="cms:PublishWithCommentAction" ID="saPublishWithComment" Sequence="610" ConfigMenu="Add"/>

            <ConsoleNode ConfigMenu="Delete" ChangedNodeID="qaPublish" />

      </structure>

</Console>

In the above CustomQuickaccess.xml you can find that we are adding the cms:PublishWithCommentAction through ConfigMenu=Add option and deleting the “qaPublish” node through ConfigMenu=Delete which is cms:PublishAction console node existing in the quickaccess.xml. This is how we need to override the OOB Quick area nodes. In the same way you can customize the EditingMenu and Site Action nodes.

Once you save and publish the customquickaccess.xml file the problematic console node vanishes and the new console node for “SubmitForApproval” appears in the quickaccess which works fine for all the workflows irrespective of the associations.

SPSite mySite = new SPSite("<SiteURL>");

SPWeb myWeb = mySite.OpenWeb();

SPFolder myList = myWeb.Folders["<DocLibName>"];

SPFile myFile = myList.Files[0];

SPUser myUser = myWeb.Users["<User_Name>"];

CheckInFileByUser(myFile, "Checkin Comments", SPCheckinType.MajorCheckIn, myUser);

public static void CheckInFileByUser(SPFile file, string checkinComment,SPCheckinType checkinType,SPUser modifiedByUser)

MethodInfo mi = typeof(SPFile).GetMethod("CheckIn",BindingFlags.Instance | BindingFlags.NonPublic, null, new Type[] { typeof(string), typeof(SPCheckinType), typeof(bool), typeof(SPUser) }, null);

try

mi.Invoke( file, new object[] { checkinComment, checkinType, false, modifiedByUser });

catch (Exception ex)

MessageBox.Show(ex.StackTrace);

MWSDefault.Master is the master page used by the OOB meeting workspace definition "MPS". This master page has been used with all the configuration of the MPS meeting workspace site definition. You can find this master page under the C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\GLOBAL folder. All the modules in the MPS site definition refers the master page from this set up path to provision it to the master page gallery.

Created a custom master page based on this MWSDefault.master page and has successfully provisioned it to the master page gallery. But applying this master page to the meeting workspace site doesn't replicate the same behavior as the OOB MWSDefault.master.

The following screenshot shows you the multipage meeting workspace site with the OOB MWSDefault.master page applied :

The following screenshot shows you the multipage meeting workspace site with the Custom MWSDefault.master page applied :

From the above screenshots you can find the difference that the multi page meeting workspace with the custom master page appears with a "Meeting Navigator" in the quick launch. This meeting navigator should appear only if more than one meeting event is linked with the meeting workspace. There are no meeting events linked with the meeting workspace but still the meeting workspace shows the "Meeting Navigator" with the message that "There are no more meeting occurrences to select from" but with the OOB MWSDefault.master everything is fine.

If you have a look into the "Default.aspx" page then you can find that the "HideMtgNavigatorPane" JavaScript function has been called to hide the meeting navigator if the meeting count for the meeting workspace is less than or equal to one (<=1). The following is the snippet from the default.aspx page :

<div id="MeetingNavigatorPane" class="ms-quicklaunchouter">

  <div class="ms-quickLaunch" style="width:100%">

      <div>

       <table height=100% cellspacing=0 cellpadding=2 class="ms-navSubMenu2">

            <tr valign=top>

                  <td id="onetidMtgNavigator">

                        <script> if (typeof(g_meetingCount) != "undefined" && (g_meetingCount == 0 || g_meetingCount == 1)) HideMtgNavigatorPane(); </script>

                        <!-- Begin Date Picker Column -->

                        <WebPartPages:WebPartZone runat="server" Title="loc:MeetingNavigator" ID="MeetingNavigator" Orientation="Vertical" FrameType="None" AllowLayoutChange="False" AllowPersonalization="false"/>

                        <!-- End Meeting Date Picker -->

                  </td>

            </tr>

       </table>

      </div>

The custom master page has the JavaScript reference but this JavaScript method (HideMtgNavigatorPane) was not called when we are applying the custom master page. While doing the further source code debugging with the variable "g_meetingCount" found an interesting thing which is the root cause of the behavior.

The variable "g_meetingCount" has been assigned with the value in the fly by registering a Client Script Block. This has been implemented in the HandlePrerender method of Microsoft.SharePoint.Meetings.PropertyBag Class. The following is the snippet of the "HandlePrerender" method in which you can find that the "g_meetingCount" is assigned with the value of meeting count from the current web object.

private void HandlePreRender(object sender, EventArgs e)

        {

            // This item is obfuscated and can not be translated.

            SPWeb contextWeb = SPControl.GetContextWeb(this.Context);

            if (SPMeeting.IsMeetingWorkspaceWeb(contextWeb))

            {

                ScriptBuilder builder = new ScriptBuilder();

                string fullOrRelativeUri = contextWeb.GetWebRelativeUrlFromUrl(SPGlobal.GetVTIRequestUrl(this.Page.Request, contextWeb.Request).ToString(), false, false);

                builder.AddVariable("g_pageUrl", "\"" + SPHttpUtility.UrlPathEncode(MtgUtility.GetServerRelativeUrl(contextWeb) + fullOrRelativeUri, true) + "\"");

                builder.AddVariable("g_webUrl", "\"" + SPHttpUtility.UrlPathEncode(contextWeb.ServerRelativeUrl, true) + "\"");

                builder.AddVariable("g_instanceId", "\"" + contextWeb.MeetingInformation.InstanceId + "\"");

                builder.AddVariable("g_meetingCount", "\"" + contextWeb.MeetingCount + "\"");

                SPList homepageLib = MtgUtility.GetHomepageLib(contextWeb);

                if (homepageLib != null)

                {

                    string str2;

                    string str3;

                    Utility.SplitUrl(fullOrRelativeUri, out str2, out str3);

                    if (SPUtility.StsCompareStrings(str2, contextWeb.MeetingInformation.MakeInstanceFolder(homepageLib.RootFolder.Url)))

                    {

                    }

                    builder.AddVariable("g_fPageGlobal", "0");

                }

                this.Page.ClientScript.RegisterClientScriptBlock(typeof(PropertyBag), "Mtg_MeetingsPropertyBag", builder.ScriptText);

            }

        }

So we need to add this class to the Body of the custom master page so that the "g_meetingCount" variable will be assigned with the value and hide/show of the meeting Navigator panel will work as expected. There is already a Tag prefix has been included in the custom Master page for the "Microsoft.SharePoint.Meetings" namespace in the master page so we just need to add the reference to the "PropertyBag" class in the "Body" of the custom master page. This fixed the issue and now the Branding works as expected :

Note :

This "PropertyBag" class is very important and it's not only important for this "g_meetingCount" because there are some other variables are also used in this PropertyBag. So when you are missing any functionalities while customizing the "MWSDefault.master" please make sure that you adds this "PropertyBag" to the "Body" of the custom master page.

State based workflow that has a DelayActivity. The DelayActivity never fires and errors out eventually. The problem lies in the fact that the workflow calls  out to another DLL in the code activity following the DelayActivity. When the call is made a  "System.IO.FileNotFoundException: Could not load file or assembly" exception is raised.