/// /// Method to handle starting the appropriate Workflow as specified by the Site Collection Workflow Name property /// private void StartWorkflow() { SPWorkflowAssociation wfa = SPContext.Current.Web.WorkflowAssociations.GetAssociationByName(this.SiteCollectionWorkflowName, CultureInfo.InvariantCulture); wfa.AssociationData = this.GetWorkflowInitiationData(); SPContext.Current.Site.WorkflowManager.StartWorkflow(null, wfa, this.GetWorkflowInitiationData(), SPWorkflowRunOptions.Asynchronous); } /// /// Method to construct the Workflow Initiation/Association Data /// /// private String GetWorkflowInitiationData() { String schema = " "xmlns:dms=\"http://schemas.microsoft.com/office/2009/documentManagement/types\" " + "xmlns:dfs=\"http://schemas.microsoft.com/office/infopath/2003/dataFormSolution\" " + "xmlns:q=\"http://schemas.microsoft.com/office/infopath/2009/WSSList/queryFields\" " + "xmlns:d=\"http://schemas.microsoft.com/office/infopath/2009/WSSList/dataFields\" " + "xmlns:ma=\"http://schemas.microsoft.com/office/2009/metadata/properties/metaAttributes\" " + "xmlns:pc=\"http://schemas.microsoft.com/office/infopath/2007/PartnerControls\" " + "xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\">" + " " StringBuilder sb = new StringBuilder(); sb.AppendFormat(" sb.AppendFormat(" sb.AppendFormat(" sb.AppendFormat(" sb.AppendFormat(" sb.AppendFormat(" return String.Format(schema, sb.ToString()); } |
Out of the box SharePoint ships with the User Tasks Web Part which allows you to display tasks assigned to the current user in the current Site.
If you want to display all Tasks in SiteCollection you can use CQWP or DataView. But there is an easy way to do that for the same user experience. The best approach is to change the value of a hidden property of the User Tasks Web Part QuerySiteCollection. This property is hidden and cannot be modified through the UI.
First export User Tasks WebPart and add property:
<QuerySiteCollection xmlns="http://schemas.microsoft.com/WebPart/v2/Aggregation">true</QuerySiteCollection>
before the </WebPart> tag
And import again. Check the result.
This will work with SharePoint 2007/SharePoint 2010.
In Solution file WSP in SharePoint 2010, you can see the contents of the WSP by changing the file extension to CAB. You can then open the file like a ZIP file within Windows Explorer, or via WinRAR.
But you cannot modify it using one of these items:
I found tool (IZArc) solve this problem. Steps involved to update the WSP are as follows :
When you use sandbox Visual Web Part and TemplateControl.LoadControl method is not working in a sandbox solution?
The reason is quite simple – your code in a sandbox solution actually executes in a console application – the SPUCWorkerProcess.exe. It is a console application has created an HttpContext and a Page instance, in which your web part class is also instantiated on that page. You don’t have some crucial asp.net pieces as the HostingEnvironment and the VirtualPathProvider – without these two the LoadControl method simply won’t work. And it is not that you don’t have access to the file system, even if you had, the LoadControl method still wouldn’t work because there wouldn’t be a VirtualPathProvider to provide the file to the asp.net compiler. The bad news is that the same holds for the TemplateControl.ParseControl method too.
Microsoft create template supports Visual Web Parts in the sandbox from Visual Studio 2010 you can use when download Visual Studio 2010 Sharepoint Power Tools
When try to use form created in sandbox solution. I found error when post data more than 128 KB. It is one limitation of more limitations in sandbox solutions.
We need to increase size to increase this limit requestlengthdiskthreshold.
Sandbox processes use SPUCHostService.exe/SPUCHostService.exe. which has extra web.config (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\UserCode\web.config), When you updated requestlengthdiskthreshold value in this web.config problem will be solved. But this solution would not work on a hosting provider. There would be little chance they would change their UserCode settings for me.
