How to cancel inprogress workflow?

How to cancel inprogress workflow?

SPWorkflowCollection itemWorkflowCollection= listItem.Workflows;
foreach (SPWorkflow itemWorkflow in itemWorkflowCollection)
{
//cycle workflows associated to the item (listItem)
if (!itemWorkflow.IsCompleted && itemWorkflow.InternalState == SPWorkflowState.Running)
{
foreach (SPWorkflowTask taskWorkflow in itemWorkflow.Tasks)
{
//cycle throught all tasks associated to the workflow
//if task is not completed
if (taskWorkflow["PercentComplete"].ToString() != "1")
{
//you can cancel or change the running tasks before canceling the workflow
taskWorkflow["Status"] = "Canceled";
taskWorkflow["PercentComplete"] = 1;
web.AllowUnsafeUpdates = true;
taskWorkflow.Update();
}
}
SPWorkflowManager.CancelWorkflow(itemWorkflow);
}
}
Enjoi...

Query to get Lock Site Collection in SHarepoint 2007.

Query to get Lock Site Collection in SHarepoint 2007.

BitFlags-131072 For Read Only Site COllection
BitFlags-1 Adding Content Prevented
BitFlags-0 for None
BitFlags-3 for No Access





SELECT dbo.Webs.SiteID as SiteID,dbo.Webs.Id AS WebGuid,


dbo.Webs.Title AS WebTitle,

dbo.Webs.FullUrl AS WebUrl

FROM dbo.Webs INNER JOIN

dbo.Sites ON dbo.Webs.SiteId = dbo.Sites.Id AND dbo.Sites.BitFlags = 131072

AND dbo.Webs.ParentWebId is null

Create Custom Action in Ribbon in Sharepoint 2010

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

http://wcftutorial.net/Difference-between-WCF-and-Webservice.aspx

End Point


Bindings and Behavior

Contracts and Service host

Message and Channel

WCF client and Metadata

http://www.dotnetcurry.com/ShowArticle.aspx?ID=766

http://learn2expert.net/DotNetInterview/COM/COM.aspx

New Folders in Sharepoint 2010 14 Hive:

New folders available in SharePoint Hive folder are,


Policy

UserCode

WebClients

WebServices

Sharepoint 2010 Alerts

By default alerts can be send only through e-mail. But we can change that default setting by using the new DeliveryChannels Property of SPAlert class. This DeliveryChannels property, specifies the delivery method of the alert.


The following snippet used to set the SMS delivery method to the Alert.

oAlert.DeliveryChannels = SPAlertDeliveryChannels.Sms;


SPAlertDeliveryChannels is the enumerated member, which specifies the method of delivering alerts.

Email-Delivery as E-mail
Sms-Delivery as SMS Message

The following example code used to update the sms delivery method to all the alerts for every user available in Current website.

SPWeb oWebsite = SPContext.Current.Web;
SPUserCollection collUsers = oWebsite.Users;
foreach (SPUser oUser in collUsers)
{
SPAlertCollection collAlerts = oUser.Alerts;
foreach (SPAlert oAlert in collAlerts)
{
oAlert.DeliveryChannels = SPAlertDeliveryChannels.Sms;
oAlert.Update();
}
}

Enjoi...

including additional assemblies in the WSP with Visual Studio SharePoint development tools

http://blog.mastykarz.nl/including-additional-assemblies-wsp-visual-studio-sharepoint-development-tools/
Thanks to above blog....on including a very good article on including additional assemblies in the WSP with Visual Studio SharePoint development tools


The new Visual Studio SharePoint development tools simplify work for SharePoint developers. Out-of-the-box the tools have some great functionality and knowing about these gems allows you to fully benefit of the power of the new tools. One of such gems can be used to make the process of provisioning multiple assemblies with a simple SharePoint Solution (WSP) easier.




How many times did you have to manually write the contents of the Manifest.xml file? Whenever you wanted to deploy an assembly with a WSP package, you had to figure out its fully qualified (4-part) name and include it in the Manifest.xml file. At some point the process got simplified thanks to tools like WSPBuilder but before that, you had to do everything manually.



The whole development story of SharePoint solutions has changed with the new Visual Studio SharePoint development tools. Using the new tools you can deploy additional assemblies with just a few mouse clicks.



Taking you there…

Let’s assume that you have the following projects: MySharePointProject which contains some SharePoint artifacts and MySharePointProject.Controls which is an ordinary Class Library that contains only the code of some controls.







Using the MySharePointProject you would like to package the Controls project including the SafeControls entries.



What you need to do is to double click on the Package project item: the Package Designer will open.







In the Package Designer you click the Advanced button. In the Advanced view you click the Add button and choose the Add Assembly from Project Output… menu option.







From the Source Project dropdown list you choose MySharePointProject.Controls project.







Then in the Safe Controls section, you click the Click here to add a new item button to add a new Safe Controls entry. And here’s where the magic happens.



…almost all the way.

In the Namespace column you enter MySharePointProject.Control – the namespace where your controls are located. The Assembly Name column can be used to provide the name of your assembly (fully qualified if the assembly will be deployed to GAC).







If it’s not the first time that you’re reading about the Visual Studio SharePoint development tools, the odds are high that you have heard about the Replaceable Parameters: tokens that are being replaced with something else during the build process. The list of out-of-the-box available tokens is really impressive, but in this scenario, one of them takes the attention in particular. Using the $SharePoint.Project.AssemblyFullName$ token you can specify that you want to include the fully qualified name of your assembly. During the build process, the Visual Studio SharePoint development tools will find this token and replace it with the actual fully qualified name of the assembly. There is however one challenge when dealing with additional assemblies.







The way the Visual Studio SharePoint development tools work at the moment is, that they use the context information from the project being built and use it to provide the replace value for the Replaceable Parameters. While it works in the most scenarios it gives you not the desired results here. If you use the $SharePoint.Project.AssemblyFullName$ token as the value for the Assembly Name column in a Safe Control entry, the generated Manifest.xml will contain the fully qualified name of the MySharePointProject assembly instead of the MySharePointProject.Controls assembly that we used in the reference. Does this mean that we cannot make use of the tokens and go back in time to the 2007 era when we had to do things manually? Not quite…



In my previous article I wrote about extending the packaging process of the Visual Studio SharePoint development tools. This is one of the scenarios when being able to extend the packaging process saves you a lot of time and keeps you productive! By using a custom Replaceable Parameter you can use a token in the Safe Control Assembly Name column and replace it with the actual fully qualified name of the referenced assembly just before the Manifest.xml file will be packaged.



Extensibility to the rescue: Introducing Imtech.VisualStudio.SharePoint.Tasks

To get the job done we need a couple of things. First of all we need a custom MSBuild task that will translate our custom Replaceable Parameter with the name of the referenced assembly. This is being done by the Imtech.VisualStudio.SharePoint.Tasks assembly. The assembly contains a custom MSBuild task that reads the contents of Manifest.xml, retrieves all Assembly elements, and replaces the $Imtech.SharePoint.AssemblyFullName$ tokens with the full name of the assembly referenced in the Assembly tag.



The next thing that we need to do, is to create a custom targets file. This does two things. It registers our custom task responsible for replacing the tokens and hooks it up with the packaging process of the Visual Studio SharePoint development tools. The targets file should contain the following contents:



?123456



We override the AfterLayout target what allows us to easily open the assemblies referenced in Manifest.xml. Additionally we are sure that our tokens are being translated before the Manifest.xml gets packaged in the WSP.



The next step is to hook up the custom targets file with the project file so that it will be used by the build process. You can do this by adding an Import element right under the one that contains a reference to Microsoft.VisualStudio.SharePoint.targets.







The last thing to do is to go to the Safe Controls dialog, add a new Safe Controls entry and use the $Imtech.SharePoint.AssemblyFullName$ token in the Assembly Name column.







If you’ve done everything right and choose Package, you should see the $Imtech.SharePoint.AssemblyFullName$ token properly replaced with the fully qualified name of the MySharePointProject.Controls assembly. You can see the Manifest.xml file used in the WSP package in the pkg\Debug\MySharePointProject directory under the MySharePointProject project.







Summary

Visual Studio SharePoint development tools provide you out-of-the-box not only with a great set of tools, that help you do your job as a SharePoint developer easier and faster, but also a very powerful extensibility framework that allows you to tailor the tools to fit your specific needs.

Programmatically remove fields from content type

You should delete fields from content type using the FieldLinks collection.




When applying site content types to lists, the content type is copied to the list. If you change the content type on the list (for example, add or remove columns), the "parent" and all the same content types on other lists won't be changed.



You have two option. If you want to change only the list content type, but not the related site content type:

using (SPWeb web = site.OpenWeb())

{

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

SPContentTypeCollection cts = list.ContentTypes;

SPContentType ct = cts["YourContentType"];

ct.FieldLinks.Delete("YourField");

ct.Update();

}



If you want to change the site content type, you should go with the code below:

using (SPWeb web = site.OpenWeb())

{

SPContentTypeCollection cts = web.ContentTypes;

SPContentType ct = cts["YourContentType"];

ct.FieldLinks.Delete("YourField");

// calling the update with true will copy the changes from

// site content types to all list content type instance

ct.Update(true);

}

Remove column from content type using powershell script

http://get-spscripts.com/2010/10/cant-remove-site-column-from-content.html


The example below will remove the “Aliases” site column from the “Sales Document” site content type in http://portal:




#Attach to the web and content type

$web = Get-SPWeb http://portal

$ct = $web.ContentTypes["Sales Document"]



#Get link to the columnn from the web

$spFieldLink = New-Object Microsoft.SharePoint.SPFieldLink ($web.Fields["Aliases"])



#Remove the column from the content type and update

$ct.FieldLinks.Delete($spFieldLink.Id)

$ct.Update()



#Dispose of the web object

$web.Dispose()

Note that any columns of this type deleted from a parent content type will not automatically disappear in the child content types below it. The easiest way to get around this is to use the same script above to remove the site column from child content types, too.




Unfortunately, you may also find that if the content types containing this site column were attached to lists, then the lists themselves will also have the column added to them – even after removing the column from all associated content types. If this is the case, you will not be able to remove the column in the list using the browser UI as the Remove button will be missing on the column administration page here also.



To resolve this, you can either decide to remove the column using PowerShell one list at a time, or if there is a way of defining a batch of lists, use a script to modify multiple lists in one go. The script below provides you with an example of how to walk through each document library of a specified name on each site of the site collection and delete the offending column. If you do decide to run a script like this, please ensure you have fully tested it in a development environment beforehand due to the potential damage that it could inflict:



#Delete column on a specified list in all sites of a site collection

$site = Get-SPSite http://portal

$site
Get-SPWeb -Limit all
ForEach-Object {

#Specify list which contains the column

$list = $_.Lists["Pages"]

#Specify column to be deleted

$field = $list.Fields["Aliases"]

#Allow column to be deleted

$field.AllowDeletion = $true

#Delete the column

$field.Delete()

#Update the list

$list.Update()

}

$site.Dispose()

Content Types Event Receivers

http://pietersveenstra.wordpress.com/2011/12/12/removing-multiple-event-handlers-from-content-type-or-list/

http://charliedigital.com/2010/10/06/programmatically-adding-an-event-receiver-to-a-content-type/


http://social.technet.microsoft.com/Forums/en-US/sharepoint2010programming/thread/ffc35fd4-2b26-4e56-a924-a3b9d9e25e6b

Search Center Links

http://www.businessintelligencetoday.com/1/post/2011/4/setting-up-a-search-center-in-sharepoint-2010.html




http://www.sharepoint911.com/blogs/john/archive/2011/06/10/using-tabs-in-the-enterprise-search-center-in-sharepoint-server-2010.aspx



http://social.msdn.microsoft.com/Forums/en-US/sharepoint2010general/thread/897c6a75-3a8f-4a86-9621-195b9d6fafbe

Workflow Codes

Workflow status codes (used for view filter)



Here is the list of the status codes used to maintain the workflow statuses. This list might be useful when anyone creates a view based on workflow status. If you are creating a view for a list filtered by the workflow status, you would need use the number rather than the words (e.g. 2 instead of In Progress, 4 instead of Cancelled etc)



Status Value

Not Started 0

Failed on Start 1

In Progress 2

Error Occurred 3

Canceled 4

Completed 5

Failed on Start (retrying) 6

Error Occurred (retrying) 7

Canceled 15

Approved 16

Rejected 17

Infopath Code Signing Certificate

Blog with step by step instructions: http://www.cnblogs.com/chenchaospr/archive/2008/04/10/1146686.html




The below link for setting up Enterprise Root Certificate:

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

Installing Visual Studio Tools for Applications for Infopath 2010

Installing Visual Studio Tools for Applications


Visual Studio Tools for Applications (VSTA) is an optional installation component available in Microsoft Office 2010 setup. To install VSTA:



1.Launch Office 2010 setup from your Office 2010 installation media or from the Control Panel Programs and Features application.

2.If you’re installing a new copy of Office 2010, click the Customize button in the installer. If you’ve already installed Office 2010, choose the Add or Remove Features radio button in the installer.

3.Set the Visual Studio Tools for Applications option to Run from My Computer and continue through the setup wizard.

Most annoying thing - Prompts for credentials a bunch of times...

The below was found by my friend Chris Weinert... Here is the solution in his own words....
On Windows 7 (Sysmex domain), when you open a Visio document from SharePoint, do you get prompted for credentials a bunch of times? Does the document open even if you cancel out of the dialogs?


Yes, and Yes, right?



I’ve been looking for this issue since late 2008 when still using Vista. Regular files open up fine, but some Office documents prompt for credentials.

Vista/Win7 behave differently than XP with the way they (and Office) interact with SharePoint.



I finally found a solution on a TechNet forum.

Add this registry setting:







And then restart the WebClient service on your local machine:









Open up a Visio diagram, or one of the HR New Hire/Term forms (InfoPath)….no more prompts!!

Enjoy.

-C

Creating WSDl files for Sharepoint deployment

Create Directory -
Copy SPDev.exe
Copy asmx file there.
Run the SPDev.exe using below command
SPDev.exe -o GenWS -url Sitecollectionurl -asmx My.asmx
Copy the Disco and WSDl files in ISAPI folder along with asmx...
 and you are good to go.

t is not a bug, it is by design that state machine workflow does not support the replicator activity.

http://www.sharepointdev.net/sharepoint--workflow/state-machine-replicator-activity-41998.shtml

Dynamic Task using CAG and Replicator Sample

http://www.mannsoftware.com/workflow/Wiki%20Pages/Dynamic%20Tasks%20Using%20a%20Replicator.aspx

Failed to load the custom Activity from toolbox in workflow

Ok, found the culprit - this happens if the library is in GAC. Once you remove the error doesn't happen anymore. On top of that the same error also happens in VS 2008 SP1.


This is not a good workaround though, as when deploying to Sharepoint the library gets installed into GAC and we're back to the same problem.

Deploy-an-ASP-NET-Form-to-a-workflow

http://dotnetslackers.com/articles/aspnet/Deploy-an-ASP-NET-Form-to-a-workflow.aspx