You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/general-development/prepare-to-set-up-and-configure-a-sharepoint-workflow-development-environment.md
+1-3Lines changed: 1 addition & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Prepare to set up and configure a SharePoint workflow development environment
3
3
description: Learn how to set up a workflow development environment to develop SharePoint workflows as free-standing apps.
4
-
ms.date: 12/14/2020
4
+
ms.date: 06/10/2022
5
5
ms.prod: sharepoint
6
6
ms.assetid: b6a3321f-4131-4a8e-9cb7-7a1b4ab9e26b
7
7
ms.localizationpriority: medium
@@ -64,8 +64,6 @@ If you have pre-release (that is, "Preview") versions of SharePoint Server, Work
64
64
65
65
The release version of the Visual Studio workflow components and their related updates introduce important changes that enhance performance, scalability, and reliability. Unfortunately, these upgrades require you to update workflow projects that you created using the Preview tools.
66
66
67
-
To make this process easier, we provide a conversion tool that you can get through CodePlex. The tool is called the [SharePoint Workflow Converter for Visual Studio 2012](http://wfconverter.codeplex.com/).
68
-
69
67
Here is a summary of changes that require you to update your workflow projects:
70
68
71
69
- Activity references to **Item Guid** are replaced by **Item Id**. This change has important consequences:
Copy file name to clipboardExpand all lines: docs/general-development/sharepoint-server-application-lifecycle-management.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -354,7 +354,7 @@ To achieve continuous integration, the build definition can be triggered when de
354
354
355
355
356
356
357
-
ForSharePoint applications, developers should use the [Office/SharePoint Continuous Integration with TFS 2012](http://officesharepointci.codeplex.com/) build definitions project to achieve scheduled builds or continuous integration. This project provides build definitions, Windows PowerShell scripts, and process instructions on how to configure [Visual Studio Team Services](https://www.visualstudio.com/vso/) or an on-premises version of TFS to build and deploy SharePoint applications in a continuous integration model. Developers should download the components in this project and configure their instance of TFS accordingly. For instructions on how to configure TFS with the provided build definition for SharePoint applications and configure the build definition to use the Windows PowerShell scripts to deploy the SharePoint application to a target environment, see the [Office/SharePoint Continuous Integration with TFS 2012 documentation](http://officesharepointci.codeplex.com/documentation).
357
+
For SharePoint applications, developers should use the [Office/SharePoint Continuous Integration with TFS 2012](https://social.technet.microsoft.com/wiki/contents/articles/25850.sharepoint-2013-continues-integration-with-tfs-2013-release-and-build-management-part-3.aspx) build definitions project to achieve scheduled builds or continuous integration. This project provides build definitions, Windows PowerShell scripts, and process instructions on how to configure [Visual Studio Team Services](https://www.visualstudio.com/vso/) or an on-premises version of TFS to build and deploy SharePoint applications in a continuous integration model. Developers should download the components in this project and configure their instance of TFS accordingly. For instructions on how to configure TFS with the provided build definition for SharePoint applications and configure the build definition to use the Windows PowerShell scripts to deploy the SharePoint application to a target environment, see the [Office/SharePoint Continuous Integration with TFS 2012 documentation](https://social.technet.microsoft.com/wiki/contents/articles/25850.sharepoint-2013-continues-integration-with-tfs-2013-release-and-build-management-part-3.aspx).
Copy file name to clipboardExpand all lines: docs/general-development/working-with-tasks-in-sharepoint-workflows-using-visual-studio-2012.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Working with Tasks in SharePoint Workflows using Visual Studio 2012
3
3
description: Learn about the new and revised workflow task framework that was introduced in SharePoint, which is built on the new Workflow Manager.
4
-
ms.date: 06/07/2022
4
+
ms.date: 06/10/2022
5
5
ms.prod: sharepoint
6
6
ms.assetid: f5869fe2-1bef-4e6f-bfdc-3e109501d260
7
7
ms.localizationpriority: medium
@@ -16,7 +16,7 @@ Learn about the new and revised workflow task framework that was introduced in S
16
16
> SharePoint 2010 workflows have been retired since August 1, 2020 for new tenants and removed from existing tenants on November 1, 2020. If you’re using SharePoint 2010 workflows, we recommend migrating to Power Automate or other supported solutions. For more info, see [SharePoint 2010 workflow retirement](https://support.microsoft.com/office/sharepoint-2010-workflow-retirement-1ca3fff8-9985-410a-85aa-8120f626965f).
17
17
18
18
19
-
This article is accompanied by an end-to-end code sample that you can use to follow the article, or as a starter for your own SharePoint workflow projects. You can find the downloadable code [here](http://assets.andrewconnell.com/media/Default/Downloads/SP2013Wf-CustomTasks.zip).
19
+
This article is accompanied by an end-to-end code sample that you can use to follow the article, or as a starter for your own SharePoint workflow projects. You can find the downloadable code [here](https://www.andrewconnell.com/blog/sharepoint-2013-workflow-custom-tasks).
20
20
21
21
One of the greatest benefits that the SharePoint brings to Windows Workflow Foundation is the implementation of a new and improved task management framework that incorporates the new Workflow Manager as its hosting environment.
22
22
## Reviewing workflow tasks in SharePoint 2007 and SharePoint 2010
> SharePoint 2010 workflows have been retired since August 1, 2020 for new tenants and removed from existing tenants on November 1, 2020. If you’re using SharePoint 2010 workflows, we recommend migrating to Power Automate or other supported solutions. For more info, see [SharePoint 2010 workflow retirement](https://support.microsoft.com/office/sharepoint-2010-workflow-retirement-1ca3fff8-9985-410a-85aa-8120f626965f).
-[Transformation guidance from farm solutions to add-in model - Replacement of files deployed via Modules (lab)](https://github.com/OfficeDev/TrainingContent/tree/master/Archive/O3658/10%20Transformation%20guidance%20from%20farm%20solutions%20to%20add-in%20model)
152
+
-[Transformation guidance from farm solutions to add-in model - Replacement of files deployed via Modules (lab)](https://github.com/OfficeDev/TrainingContent/blob/master/SharePoint/AddIns/14%20Transformation%20guidance%20from%20farm%20solutions%20to%20add-in%20model/Readme.md)
153
153
-[Branding SharePoint sites in the SharePoint Add-in model](../solution-guidance/branding-sharepoint-sites-sharepoint-add-in.md)
154
154
155
155
### Videos
156
156
157
157
-[PnP Webcast - Customizations options with SharePoint Online “modern” experiences](https://www.youtube.com/watch?v=724Spxu3hF4)
158
158
-[Learn best practices for customizing and branding SharePoint Team Sites](https://www.youtube.com/watch?v=2AxN-G56-d4)
159
-
-[Office Dev PnP Web Cast – Branding SharePoint using add-in model techniques](/office/blogs/branding-sharepoint-using-add-in-model-techniques)
159
+
-[Office Dev PnP Web Cast – Branding SharePoint using add-in model techniques](/sharepoint/dev/solution-guidance/branding-sharepoint-sites-sharepoint-add-in)
160
160
161
161
### Solutions
162
162
@@ -199,9 +199,9 @@ Cascading style sheet (CSS) plays a large role in SharePoint branding. To succes
-[Core.EmbedJavaScriptJSOM - Shows how to do JavaScript embedding from SP hosted add-in](https://github.com/OfficeDev/PnP/tree/master/Samples/Core.EmbedJavaScriptJSOM)
233
233
-[Core.EmbedJavaScript.HeaderFooter - Shows how to add custom header and footer with JavaScript embed pattern](https://github.com/OfficeDev/PnP/tree/master/Samples/Core.EmbedJavaScript.HeaderFooter)
Copy file name to clipboardExpand all lines: docs/scenario-guidance/Long-running-scheduled-operations.md
+9-10Lines changed: 9 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Long-running and scheduled operations
3
3
description: Use timer jobs in SharePoint to perform background tasks to manage or govern your environment, such as displaying a message on the site when certain criteria are not met, or enforcing retention policies or running scheduled processes that are processor-intensive.
4
-
ms.date: 06/22/2021
4
+
ms.date: 06/10/2022
5
5
ms.localizationpriority: medium
6
6
---
7
7
# Long-running and scheduled operations
@@ -74,11 +74,10 @@ In this pattern, the Azure WebJob handles the scheduling aspects associated with
-[Using Remote Event Receivers and Remote Timer Jobs (training)](https://github.com/OfficeDev/TrainingContent/tree/master/Archive/O3658/05%20Using%20Remote%20Event%20Receivers%20and%20Remote%20Timer%20Jobs)
-[Asynchronous operations with Azure storage queues and WebJobs](https://dev.office.com/patterns-and-practices-detail/2254)
81
-
-[Content Type Enforce Retention](https://dev.office.com/patterns-and-practices-detail/2266)
77
+
-[Using Remote Event Receivers and Remote Timer Jobs (training)](https://github.com/OfficeDev/TrainingContent/tree/master/SharePoint/AddIns/08%20Using%20Remote%20Event%20Receivers%20and%20Remote%20Timer%20Jobs)
-[Using Remote Event Receivers and Remote Timer Jobs (training)](https://github.com/OfficeDev/TrainingContent/tree/master/Archive/O3658/05%20Using%20Remote%20Event%20Receivers%20and%20Remote%20Timer%20Jobs)
109
+
-[Using Remote Event Receivers and Remote Timer Jobs (training)](https://github.com/OfficeDev/TrainingContent/tree/master/SharePoint/AddIns/08%20Using%20Remote%20Event%20Receivers%20and%20Remote%20Timer%20Jobs)
111
110
112
111
### Windows scheduled tasks
113
112
@@ -133,8 +132,8 @@ In this pattern, the Windows Scheduler handles the scheduling aspects associated
133
132
##### Samples
134
133
135
134
-[Core.SimpleTimerJob (O365 PnP Sample)](https://github.com/SharePoint/PnP/tree/master/Samples/Core.SimpleTimerJob) - End-to-end article about this pattern with accompanying video.
136
-
-[Using Remote Event Receivers and Remote Timer Jobs (training)](https://github.com/OfficeDev/TrainingContent/tree/master/Archive/O3658/05%20Using%20Remote%20Event%20Receivers%20and%20Remote%20Timer%20Jobs)
137
-
-[Moving Full Trust Code to the Cloud](https://github.com/OfficeDev/TrainingContent/tree/master/Archive/O3651/O3651-4%20Moving%20Full%20Trust%20Code%20to%20the%20cloud%20using%20repeatable%20patterns%20and%20best%20practices)
135
+
-[Using Remote Event Receivers and Remote Timer Jobs (training)](https://github.com/OfficeDev/TrainingContent/tree/master/SharePoint/AddIns/08%20Using%20Remote%20Event%20Receivers%20and%20Remote%20Timer%20Jobs)
136
+
-[Moving Full Trust Code to the Cloud](https://github.com/OfficeDev/TrainingContent/blob/master/SharePoint/AddIns/04%20Moving%20Full%20Trust%20Code%20to%20the%20cloud%20using%20repeatable%20patterns%20and%20best%20practices/Lab.md)
138
137
139
138
### SharePoint TimerJobs
140
139
@@ -152,4 +151,4 @@ A timer job is a trigger to start to run a specific Windows service for one of t
-[Moving Full Trust Code to the Cloud](https://github.com/OfficeDev/TrainingContent/tree/master/Archive/O3651/O3651-4%20Moving%20Full%20Trust%20Code%20to%20the%20cloud%20using%20repeatable%20patterns%20and%20best%20practices)
154
+
-[Moving Full Trust Code to the Cloud](https://github.com/OfficeDev/TrainingContent/blob/master/SharePoint/AddIns/04%20Moving%20Full%20Trust%20Code%20to%20the%20cloud%20using%20repeatable%20patterns%20and%20best%20practices/Lab.md)
-[Azure Active Directory implicit flow authentication samples](https://github.com/SharePoint/sp-dev-fx-webparts/tree/master/samples/react-aad-implicitflow)
50
-
-[An ASP.NET Core implementation of the TokenHelper and SharePointContext classes for use in SharePoint Apps (AspNetCore.Authentication)](https://dev.office.com/patterns-and-practices-detail/10979)
-[Access SharePoint data with the Cross Domain JavaScript Library](https://dev.office.com/code-samples-detail/5814)
53
-
-[Access SharePoint data with the Cross Domain JavaScript Library and the REST\OData endpoints](https://dev.office.com/code-samples-detail/5815)
50
+
-[An ASP.NET Core implementation of the TokenHelper and SharePointContext classes for use in SharePoint Apps (AspNetCore.Authentication)](https://github.com/pnp/PnP/tree/master/Solutions/AspNetCore.Authentication)
-[Access SharePoint data with the Cross Domain JavaScript Library](https://github.com/OfficeDev/SharePoint-Add-in-JSOM-CrossDomain)
53
+
-[Access SharePoint data with the Cross Domain JavaScript Library and the REST\OData endpoints](https://github.com/OfficeDev/SharePoint-Add-in-REST-OData-CrossDomain)
*[SharePoint 2010 and web templates](https://blogs.msdn.microsoft.com/vesku/2010/10/14/sharepoint-2010-and-web-templates)
93
92
*[Save, download, and upload a SharePoint site as a template](/sharepoint/dev/general-development/save-download-and-upload-a-sharepoint-site-as-a-template)
94
93
*[Site definitions vs. Web templates](https://blogs.msdn.microsoft.com/vesku/2011/07/22/site-definitions-vs-web-templates/)
0 commit comments