When you develop a custom field type that inherits from SPFieldLookUp/SPFieldUser(not sure about any other controls) .
The derived field type has its own rendering controls. The issue arises when multiple values are to be stored in a field of the custom fieldtype.
In order to save multiple values to an SPFieldLookUp the property "AllowMultipleValues" should be set to true . When "AllowMultipleValues" property is
set to true, the field rendering control is overridden by MultipleLookupField. So the custom field rendering control is never instantiated/render if the field is
set to store multiple values(AllowMultipleValues=true). As a workaround what I did is overridden the ‘OnAdded’ function and edit the schema to append the ‘Mult’ attribute.

   1: using System;

   2: using System.Collections.Generic;

   3: using System.Text;

   4: using Microsoft.SharePoint;

   5: using Microsoft.SharePoint.WebControls;

   6: using System.Web.UI;

   7: using System.Xml;

   8:  

   9: namespace CustLookuColumn

  10: { 

  11:     public class MultiLookUp : SPFieldLookup  

  12:     {        

  13:        

  14:        public MultiLookUp(SPFieldCollection fields, string fieldName)

  15:             : base(fields, fieldName)

  16:         {          

  17:                    

  18:         }

  19:  

  20:        public override void OnAdded(SPAddFieldOptions op)

  21:        {

  22:            base.OnAdded(op);        

  23:            XmlDocument doc = new XmlDocument();

  24:            doc.LoadXml(this.SchemaXml);

  25:            XmlNode element = doc.FirstChild;

  26:            XmlAttribute attr = doc.CreateAttribute("Mult");

  27:            attr.Value = "TRUE";

  28:            element.Attributes.Append(attr);

  29:            this.SchemaXml = doc.OuterXml;

  30:            base.Update();

  31:  

  32:        }

  33:        public MultiLookUp(SPFieldCollection fields, string typeName, string displayName)

  34:             : base(fields, typeName, displayName)

  35:         {

  36:            

  37:         }        

  38:        

  39:         public override BaseFieldControl FieldRenderingControl

  40:         {

  41:             get

  42:             {

  43:                 BaseFieldControl fieldControl = null;

  44:                 fieldControl = new RenderFieldControl(); //See the below code snippet                               

  45:                 fieldControl.FieldName = InternalName;

  46:                 return fieldControl;

  47:             }

  48:         }

  49:     }   

  50: }

   1: using System;

   2: using System.Runtime.InteropServices;

   3: using Microsoft.SharePoint;

   4: using Microsoft.SharePoint.WebControls;

   5: using System.Web.UI;

   6: using System.Web.UI.WebControls;

   7: using System.Web.UI.HtmlControls;

   8:  

   9: //This is just a skeleton, I haven't included the entire functionality. 

  10:  

  11: namespace CustLookuColumn

  12: {

  13: public class RenderFieldControl : BaseFieldControl

  14:    {      

  15:        protected override void CreateChildControls()

  16:        {

  17:            base.CreateChildControls();

  18:         }

  19:  

  20:     }

  21:  

  22: }

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

   2: <FieldTypes>

   3:   <FieldType>

   4:     <Field Name="TypeName">MultiLookUp</Field>

   5:     <Field Name="TypeDisplayName">MultiLookUpField</Field>

   6:     <Field Name="TypeShortDescription">Custom Multi LookUp Field</Field>

   7:     <Field Name="ParentType">LookupMulti</Field>

   8:     <Field Name="UserCreatable">TRUE</Field>

   9:     <Field Name="FieldTypeClass">CustLookuColumn.MultiLookUp,CustLookuColumn , Version=1.1.1.1, Culture=neutral, PublicKeyToken=6332f1922196b6de</Field>

  10:     <Field Name="FieldEditorUserControl">/_controltemplates/YOUR_LookupFieldEditor.ascx</Field>

  11:     <!-- 

  12:         YOUR_LookupFieldEditor.ascx is not included it would be identical to the ascx control under ..\12\TEMPLATE\CONTROLTEMPLATES\LookupFieldEditor.ascx

  13:     -->

  14:   </FieldType>

  15: </FieldTypes>

Note: The samples provided within this blog may not work, my intention was to provide you a workaround when you hit with this issue.

Happy customization!!!

The max number of characters that can be passed through FullTextSqlQuery is 4096 characters, beyond this length throws an exception ArgumentOutOfRangeException. You will get the same behavior when using the webservice QueryEx(XmlNode) as well.

   1: private void ExecQuery()

   2: {

   3: ResultTableCollection resultCollection = null;

   4: SPSite site = new SPSite("http://server/");

   5: FullTextSqlQuery fullText = new FullTextSqlQuery(site);

   6: fullText.ResultTypes = ResultType.RelevantResults;

   7: fullText.QueryText = "SELECT Title, Path, Description, Write, Rank, Size FROM Scope()"; //max 4096

   8: fullText.KeywordInclusion =KeywordInclusion.AnyKeyword;

   9: resultCollection = fullText.Execute();

  10: ResultTable results = resultCollection[ResultType.RelevantResults];

  11: dataGridView1.DataSource = null;

  12: if (results.RowCount > 0)

  13: {

  14: DataTable dtresults = new DataTable();

  15: dtresults.TableName = "Result"

  16: dtresults.Load(results, LoadOption.OverwriteChanges);

  17: DataSet ds = new DataSet("All_Results");

  18: ds.Tables.Add(dtresults);

  19: dataGridView1.DataSource = ds;

  20: dataGridView1.DataMember = "Result";

  21: }

  22: }

Hope this helps.

Removing Association

 

   1: SPSite site = new SPSite("http://localhost");

   2: SPWeb web = site.OpenWeb();

   3: SPList list = web.Lists["Shared Documents"];

   4: SPWorkflowAssociation _association = null;

   5: foreach (SPWorkflowAssociation association in list.WorkflowAssociations)

   6: {

   7: if (association.Name == "Approval")

   8: {

   9: _association = association;

  10: break; 

  11: }

  12: }

  13: if(_association !=null)

  14: list.RemoveWorkflowAssociation(_association);

Adding workflow to the library

   1: SPSite site = new SPSite("http://localhost");

   2: SPWeb web = site.OpenWeb();

   3: SPList list = web.Lists["Shared Documents"];

   4: SPList taskList = web.Lists["Tasks"];

   5: SPList historyList = web.Lists["Workflow History"]; 

   6: SPWorkflowTemplate _template = null;

   7: foreach (SPWorkflowTemplate template in web.WorkflowTemplates)

   8: {

   9: if (template.Name == "Approval")

  10: {

  11: _template = template;

  12: break; 

  13: } 

  14: }

  15: SPWorkflowAssociation asso = SPWorkflowAssociation.CreateListAssociation(_template, _template.Name, taskList, historyList); 

  16: list.AddWorkflowAssociation(asso);

Starting workflow

   1: SPSite site = new SPSite("http://localhost");

   2: SPWeb web = site.OpenWeb();

   3: SPList list = web.Lists["Shared Documents"];

   4: SPWorkflowAssociation association = AddWorkflow(); // Above function to get the SPWorlflowAssociation object

   5: SPWorkflowManager manager = site.WorkflowManager; 

   6: for (int idx = 0; idx < 10 ; idx++) // I'm assuming there would be atleast 10 items within the library

   7: {

   8: SPListItem item = list.Items[idx];

   9: manager.StartWorkflow(item,association, "you can pass any data here",true);

  10: }

You might have experienced a road block when trying to the update the ‘ModerationStatus’ field with other fields. Any attempt to do so will result in an exception “You cannot change moderation status and set other item properties at that same time”. This is an expected behavior since the document deals with stream, promotion and demotion and for non document libraries we are not touching the streams, so it allows updating other fields with “ModerationStatus”.

Here is the code: In this sample code, we are trying to update the 'Editor' field along with the 'ModerationStatus’.

      

   1: SPSite oSite = new SPSite("http://localhost:100/sites/Internetsite/");

   2:         SPWeb oWeb = oSite.OpenWeb(); 

   3:         SPList oList = oWeb.Lists["Shared Documents"]; 

   4:         SPListItem oListItem = oList.Items[0]; 

   5:         SPUser oUser = oWeb.AllUsers[@"domain\user123"]; 

   6:         SPFieldUserValue oUserValue = new SPFieldUserValue(oWeb, oUser.ID, oUser.LoginName); 

   7:         oListItem["Editor"] = oUserValue;                

   8:         oListItem.ModerationInformation.Status = SPModerationStatusType.Approved; 

   9:         oListItem.Update();

 

Note: This behaviour is only with libraries of type document libraries(SPBaseType.DocumentLibrary).

Good Luck!!!

   1: SPSite spSite = new SPSite("http://nishand:100/sites/InternetSite/");

   2: SPRecycleBinItemCollection collection = spSite.RecycleBin; 

   3:  

   4: for (int x = 0; x < collection.Count ; x++) 

   5: {           

   6:               collection[x].Delete(); x = x-1;                               

   7: }

   8:  

The above code works only for the items deleted by the user who runs the application/current user.
Any attempt to delete a file deleted by other user from the recycle bin file will result in an exception "Operation is not valid due to the current state of the object."

We do have an overridden Delete() function, that helps to delete all RecycleBin items.

SPRecycleBinItemCollection.Delete(Guid [] guids)

Hope this works for you!

By default the SPWorkflowAssociation.AutoCleanupDays property value is set to ‘60’ days, to set this property we need to call the SPList.UpdateWorkflowAssociation(SPWorkflowAssociation) function, SPWeb.Update() won’t work here.

   1: SPSite site = new SPSite("<http://nishandv3:100/sites/DevSite/>");

   2: SPWeb web = site.OpenWeb();

   3: SPWorkflowTemplateCollection collection = web.WorkflowTemplates;

   4: SPList list = web.Lists["Shared Documents"];

   5: SPWorkflowAssociation _asso = null;

   6: foreach (SPWorkflowAssociation asso in list.WorkflowAssociations)

   7: {

   8: if (asso.Name == "Approval")

   9: {

  10: asso.AutoCleanupDays = 100;

  11: _asso = asso;

  12: }

  13: }

  14: list.UpdateWorkflowAssociation(_asso); 

Hope this works for you!

Note: Make sure that you have enabled search based alerts SSP-> Search Settings -> Search Based Alerts

   1: SPSite spSite = new SPSite("http://nishand:300/sites/PubSite/Search/");

   2: SPWeb web = spSite.OpenWeb();

   3: Query alertQuery = new KeywordQuery(spSite);

   4: alertQuery.QueryText = "Hello" // Keyword

   5: SearchAlert searchAlert = new SearchAlert(spSite, alertQuery); 

   6: searchAlert.InnerAlert.AlertFrequency = SPAlertFrequency.Daily; 

   7: searchAlert.InnerAlert.Title = "Alert#2"

   8: searchAlert.InnerAlert.User = web.Users["domain\\user"]; 

   9: searchAlert.Update();

How to check whether an alert named 'Alert#2' has been created?

  Go to Site Actions ->  Site Settings - User Alerts -> Select 'user name' and click on 'update' button.