updating links from fwlink to real link if exists

docs/framework/windows-workflow-foundation/consuming-odata-feeds-from-a-workflow.md

@@ -9,7 +9,7 @@ WCF Data Services is a component of the .NET Framework that enables you to creat
 
 ## Using the sample Northwind OData service
 
-The examples in this topic use the sample Northwind data service located at <https://services.odata.org/Northwind/Northwind.svc/>. This service is provided as part of the [OData SDK](https://go.microsoft.com/fwlink/?LinkID=185248) and provides read-only access to the sample Northwind database. If write access is desired, or if a local WCF Data Service is desired, you can follow the steps of the [WCF Data Services Quickstart](https://go.microsoft.com/fwlink/?LinkID=131076) to create a local OData service that provides access to the Northwind database. If you follow the quickstart, substitute the local URI for the one provided in the example code in this topic.
+The examples in this topic use the sample Northwind data service located at <https://services.odata.org/Northwind/Northwind.svc/>. This service is provided as part of the [OData SDK](https://www.odata.org/wp-content/uploads/sites/21/odatasdkcodesamples.zip) and provides read-only access to the sample Northwind database. If write access is desired, or if a local WCF Data Service is desired, you can follow the steps of the [WCF Data Services Quickstart](../data/wcf/quickstart-wcf-data-services.md) to create a local OData service that provides access to the Northwind database. If you follow the quickstart, substitute the local URI for the one provided in the example code in this topic.
 
 ## Consuming an OData feed using the client libraries
 
@@ -148,4 +148,4 @@ xmlns="http://www.w3.org/2005/Atom">
 ...
 ```
 
-This example provides one method that workflow application authors can use to consume the raw data returned from an OData service. For more information about accessing WCF Data Services using URIs, see [Accessing Data Service Resources (WCF Data Services)](../data/wcf/accessing-data-service-resources-wcf-data-services.md) and [OData: URI Conventions](https://go.microsoft.com/fwlink/?LinkId=185564).
+This example provides one method that workflow application authors can use to consume the raw data returned from an OData service. For more information about accessing WCF Data Services using URIs, see [Accessing Data Service Resources (WCF Data Services)](../data/wcf/accessing-data-service-resources-wcf-data-services.md) and [OData: URI Conventions](https://www.odata.org/documentation/odata-version-2-0/uri-conventions/).

docs/framework/windows-workflow-foundation/custom-tracking-records.md

@@ -26,5 +26,5 @@ A <xref:System.Activities.Tracking.CustomTrackingRecord> is emitted in a code ac
 
 ## See also
 
-- [Windows Server App Fabric Monitoring](https://go.microsoft.com/fwlink/?LinkId=201273)
-- [Monitoring Applications with App Fabric](https://go.microsoft.com/fwlink/?LinkId=201275)
+- [Windows Server App Fabric Monitoring](https://docs.microsoft.com/previous-versions/appfabric/ee677251(v=azure.10))
+- [Monitoring Applications with App Fabric](https://docs.microsoft.com/previous-versions/appfabric/ee677276(v=azure.10))

docs/framework/windows-workflow-foundation/debugging-workflows.md

@@ -25,7 +25,7 @@ Workflow debugging also supports using Visual Studio’s infrastructure to attac
 
 ## Remote Debugging
 
-Windows Workflow Foundation (WF) remote debugging functions the same as remote debugging for other Visual Studio components. For information on using remote debugging, see [How to: Enable Remote Debugging](https://go.microsoft.com/fwlink/?LinkId=196257).
+Windows Workflow Foundation (WF) remote debugging functions the same as remote debugging for other Visual Studio components. For information on using remote debugging, see [How to: Enable Remote Debugging](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/febz73k0(v=vs.100)).
 
 > [!NOTE]
 > If the workflow application targets the x86 architecture and is hosted on a computer running a 64 bit operating system, then remote debugging will not work unless Visual Studio is installed on the remote computer or the target for the workflow application is changed to **Any CPU**.

docs/framework/windows-workflow-foundation/feature-specifics.md

@@ -90,15 +90,15 @@ The WCF configuration schema is complex and provides users with many hard to fin
 
 ### Getting Started
 
-- [A Developer's Guide to WCF 4.0](https://go.microsoft.com/fwlink/?LinkId=204940)
+- [A Developer's Guide to WCF 4.0](https://docs.microsoft.com/previous-versions/dotnet/articles/ee354381(v=msdn.10))
 
-- [Configuration Channel Factory](https://go.microsoft.com/fwlink/?LinkId=204941)
+- [Configuration Channel Factory](xref:System.ServiceModel.Configuration.ConfigurationChannelFactory%601)
 
-- [Standard Endpoint Element](https://go.microsoft.com/fwlink/?LinkId=204942)
+- [Standard Endpoint Element](xref:System.ServiceModel.Configuration.StandardEndpointElement)
 
-- [Service configuration improvements in .NET Framework 4](https://go.microsoft.com/fwlink/?LinkId=204943)
+- [Service configuration improvements in .NET Framework 4](https://blogs.msdn.microsoft.com/endpoint/2009/06/30/service-configuration-improvements-in-net-4/)
 
-- [Common User Mistake in .NET 4: Mistyping the WF/WCF Service Configuration Name](https://go.microsoft.com/fwlink/?LinkId=204944)
+- [Common User Mistake in .NET 4: Mistyping the WF/WCF Service Configuration Name](https://blogs.msdn.microsoft.com/endpoint/2009/11/09/common-user-mistake-in-net-4-mistyping-the-wfwcf-service-configuration-name/)
 
 ### Simplified Configuration Scenarios
 
@@ -120,9 +120,9 @@ The [DataContractResolver](../wcf/samples/datacontractresolver.md) solves these
 
 ### Getting Started
 
-- [Data Contract Resolver API documentation](https://go.microsoft.com/fwlink/?LinkId=204946)
+- [Data Contract Resolver API documentation](xref:System.Runtime.Serialization.DataContractResolver)
 
-- [Introducing the Data Contract Resolver](https://go.microsoft.com/fwlink/?LinkId=204947)
+- [Introducing the Data Contract Resolver](https://blogs.msdn.microsoft.com/youssefm/2009/06/05/configuring-known-types-dynamically-introducing-the-datacontractresolver/)
 
 - Samples:
 
@@ -282,7 +282,7 @@ The routing service in .NET 4 is designed to make these problems easier to solve
 
 2. Samples: [Routing Services [WCF Samples]](../wcf/samples/routing-services.md)
 
-3. Blog: [Routing Rules!](https://go.microsoft.com/fwlink/?LinkId=204956)
+3. Blog: [Routing Rules!](https://blogs.msdn.microsoft.com/RoutingRules/)
 
 ### Routing Scenarios
 

docs/framework/windows-workflow-foundation/how-to-create-a-custom-persistence-participant.md

@@ -4,7 +4,7 @@ ms.date: "03/30/2017"
 ms.assetid: 1d9cc47a-8966-4286-94d5-4221403d9c06
 ---
 # How to: Create a Custom Persistence Participant
-The following procedure has steps to create a persistence participant. See the [Participating in Persistence](https://go.microsoft.com/fwlink/?LinkID=177735) sample and [Store Extensibility](store-extensibility.md) topic for sample implementations of persistence participants.  
+The following procedure has steps to create a persistence participant. See the [Participating in Persistence](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/dd699769(v=vs.100)) sample and [Store Extensibility](store-extensibility.md) topic for sample implementations of persistence participants.  
 
 1. Create a class deriving from the <xref:System.Activities.Persistence.PersistenceParticipant> or the <xref:System.Activities.Persistence.PersistenceIOParticipant> class. The PersistenceIOParticipant class offers the same extensibility points as the PersistenceParticipant class in addition to being able to participate in I/O operations. Follow one or more of the following steps.  
 

docs/framework/windows-workflow-foundation/how-to-enable-sql-persistence-for-workflows-and-workflow-services.md

@@ -8,7 +8,7 @@ ms.assetid: ca7bf77f-3e5d-4b23-b17a-d0b60f46411d
 
 This topic describes how to configure the SQL Workflow Instance Store feature to enable persistence for your workflows and workflow services both programmatically and by using a configuration file.
 
-Windows Server App Fabric simplifies the process of configuring persistence. For more information, see [App Fabric Persistence Configuration](https://go.microsoft.com/fwlink/?LinkId=201204).
+Windows Server App Fabric simplifies the process of configuring persistence. For more information, see [App Fabric Persistence Configuration](https://docs.microsoft.com/previous-versions/appfabric/ee790848(v=azure.10)).
 
 Before using the SQL Workflow Instance Store feature, create a database that the feature uses to persist workflow instances. The [!INCLUDE[netfx_current_short](../../../includes/netfx-current-short-md.md)] set-up program copies SQL script files associated with the SQL Workflow Instance Store feature to the %WINDIR%\Microsoft.NET\Framework\v4.xxx\SQL\EN folder. Run these script files against a SQL Server 2005 or SQL Server 2008 database that you want the SQL Workflow Instance Store to use to persist workflow instances. Run the SqlWorkflowInstanceStoreSchema.sql file first and then run the SqlWorkflowInstanceStoreLogic.sql file.
 
@@ -147,7 +147,7 @@ workflowServiceHost.DurableInstancingOptions.InstanceStore = sqlInstanceStoreObj
 ```
 
 > [!IMPORTANT]
-> It is recommended that you do not store sensitive information such as user names and passwords in the Web.config file. If you do store sensitive information in the Web.config file, you should secure access to the Web.config file by using file system Access Control Lists (ACLs). In addition, you can also secure the configuration values within a configuration file as mentioned in [Encrypting Configuration Information Using Protected Configuration](https://go.microsoft.com/fwlink/?LinkId=178419).
+> It is recommended that you do not store sensitive information such as user names and passwords in the Web.config file. If you do store sensitive information in the Web.config file, you should secure access to the Web.config file by using file system Access Control Lists (ACLs). In addition, you can also secure the configuration values within a configuration file as mentioned in [Encrypting Configuration Information Using Protected Configuration](https://docs.microsoft.com/en-us/previous-versions/aspnet/53tyfkaw(v=vs.100)).
 
 ### Machine.config Elements Related to the SQL Workflow Instance Store Feature
 

docs/framework/windows-workflow-foundation/instance-stores.md

@@ -4,7 +4,7 @@ ms.date: "03/30/2017"
 ms.assetid: f2629668-0923-4987-b943-67477131c1e0
 ---
 # Instance Stores
-An instance store is a logical container of instances. It is the place where the instance data and metadata is stored. An instance store does not imply dedicated physical storage. An instance store could contain durable information in a SQL Server database or non-durable state information in a memory. The [!INCLUDE[netfx_current_long](../../../includes/netfx-current-long-md.md)] ships with the SQL Workflow Instance Store, which is a concrete implementation of an instance store that allows workflows to persist instance data and metadata into a SQL Server 2005 or SQL Server 2008 database. In addition Windows Server App Fabric also provides a concrete implementation of an instance store. For more information, see [Windows Server App Fabric Instance Store, Query, and Control Providers](https://go.microsoft.com/fwlink/?LinkID=201201&clcid=0x409).  
+An instance store is a logical container of instances. It is the place where the instance data and metadata is stored. An instance store does not imply dedicated physical storage. An instance store could contain durable information in a SQL Server database or non-durable state information in a memory. The [!INCLUDE[netfx_current_long](../../../includes/netfx-current-long-md.md)] ships with the SQL Workflow Instance Store, which is a concrete implementation of an instance store that allows workflows to persist instance data and metadata into a SQL Server 2005 or SQL Server 2008 database. In addition Windows Server App Fabric also provides a concrete implementation of an instance store. For more information, see [Windows Server App Fabric Instance Store, Query, and Control Providers](https://docs.microsoft.com/previous-versions/appfabric/ff383417(v=azure.10)).  
 
  The persistence API is the interface between a host and an instance store that allows the host to send command requests (for example, <xref:System.Activities.DurableInstancing.LoadWorkflowCommand> and <xref:System.Activities.DurableInstancing.SaveWorkflowCommand>) to the instance store. The concrete implementation of this API is called a persistence provider. The persistence provider receives requests from a host and modifies the instance store.  
 

docs/framework/windows-workflow-foundation/migration-guidance.md

@@ -16,38 +16,38 @@ In the .NET Framework 4, Microsoft is releasing the second major version of Wind
  Thus, the decision to adopt the .NET Framework 4 is decoupled from your decision to move to WF4 (System.Activities.\*) from WF3 (System.Workflow.\*). This topic provides links to WF migration guidance that provides information about working with WF3 and WF4.  
 
 ## WF Migration Whitepapers and Cookbooks  
- The [WF Migration Overview](https://go.microsoft.com/fwlink/?LinkId=153873) topic provides a broad overview of the relationship between WF3 and WF4 and migration strategies. Companion topics drill into specific topics.  
+ The [WF Migration Overview](https://docs.microsoft.com/previous-versions/appfabric/ff383417(v=azure.10)) topic provides a broad overview of the relationship between WF3 and WF4 and migration strategies. Companion topics drill into specific topics.  
 
- [WF Migration Overview](https://go.microsoft.com/fwlink/?LinkId=153873)  
+ [WF Migration Overview](https://docs.microsoft.com/previous-versions/appfabric/ff383417(v=azure.10))  
  Describes the relationship between WF3 and WF4, and the choices you have as a user or a potential user of workflow technology in .NET 4.  
 
- [WF Migration: Best Practices for WF3 Development](https://go.microsoft.com/fwlink/?LinkId=153852)  
+ [WF Migration: Best Practices for WF3 Development](https://docs.microsoft.com/previous-versions/appfabric/ff383417(v=azure.10))  
  Discusses how to design WF3 artifacts so they can be more easily migrated to WF4.  
 
- [WF Guidance: Rules](https://go.microsoft.com/fwlink/?LinkId=153854)  
+ [WF Guidance: Rules](https://docs.microsoft.com/previous-versions/appfabric/ff383417(v=azure.10))  
  Discusses how to bring rules-related investments forward into .NET Framework 4 solutions.  
 
- [WF Guidance: State Machine](https://go.microsoft.com/fwlink/?LinkId=153855)  
+ [WF Guidance: State Machine](https://docs.microsoft.com/previous-versions/appfabric/ff383417(v=azure.10))  
  Discusses WF4 control flow modeling in the absence of a State-Machine activity.  
 
  Note that this guidance only applies to workflow projects that target .NET Framework 4. State Machine workflows were added in .NET 4.0.1 with the release of Platform Update 1, and were included as part of .NET Framework 4.5. For more information about state machine workflows in .NET 4.0.1 - 4.0.3 and .NET Framework 4.5, see [Update 4.0.1 for Microsoft .NET Framework 4 Features](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/hh290669(v=vs.100)) and [State Machine Workflows](state-machine-workflows.md).  
 
- [WF Migration Cookbook: Custom Activities](https://go.microsoft.com/fwlink/?LinkId=153856)  
+ [WF Migration Cookbook: Custom Activities](https://docs.microsoft.com/previous-versions/appfabric/ff383417(v=azure.10))  
  Provides examples and instructions for redesigning WF3 custom activities on WF4.  
 
- [WF Migration Cookbook: Advanced Custom Activities](https://go.microsoft.com/fwlink/?LinkId=275560)  
+ [WF Migration Cookbook: Advanced Custom Activities](https://docs.microsoft.com/previous-versions/appfabric/ff383417(v=azure.10))  
  Provides guidance for redesigning advanced WF3 custom activities that use WF3 queues and schedule child activities as WF4 custom activities.  
 
- [WF Migration Cookbook: Workflows](https://go.microsoft.com/fwlink/?LinkId=153858)  
+ [WF Migration Cookbook: Workflows](https://docs.microsoft.com/previous-versions/appfabric/ff383417(v=azure.10))  
  Provides examples and instructions for redesigning WF3 workflows on WF4.  
 
- [WF Migration Cookbook: Workflow Hosting](https://go.microsoft.com/fwlink/?LinkId=275561)  
+ [WF Migration Cookbook: Workflow Hosting](https://docs.microsoft.com/previous-versions/appfabric/ff383417(v=azure.10))  
  Provides guidance for redesigning WF3 hosting code as WF4 hosting code. The goal is to cover the key differences in workflow hosting between WF3 and WF4.  
 
- [WF Migration Cookbook: Workflow Tracking](https://go.microsoft.com/fwlink/?LinkId=275562)  
+ [WF Migration Cookbook: Workflow Tracking](https://docs.microsoft.com/previous-versions/appfabric/ff383417(v=azure.10))  
  Provides guidance for redesigning WF3 tracking code and configuration using equivalent WF4 tracking code and configuration.  
 
- [WF Guidance: Workflow Services](https://go.microsoft.com/fwlink/?LinkId=275564)  
+ [WF Guidance: Workflow Services](https://docs.microsoft.com/previous-versions/appfabric/ff383417(v=azure.10))  
  Provides example-oriented step-by-step instructions for redesigning workflows that implement Windows Communication Foundation (WCF) web services (commonly referred to as workflow services) created in WF3 to use WF4, for common scenarios for out-of-box activities.  
 
 ## See also

docs/framework/windows-workflow-foundation/net-framework-3-0-wf-in-net-framework-4-interop.md

@@ -18,7 +18,7 @@ The <xref:System.Activities.Statements.Interop> activity is a [!INCLUDE[netfx_cu
 
 - The WF 3 activity must have a public parameterless constructor.  
 
-- Due to limitations in the interface types that the <xref:System.Activities.Statements.Interop> activity can support, <xref:System.Workflow.Activities.HandleExternalEventActivity> and <xref:System.Workflow.Activities.CallExternalMethodActivity> cannot be used directly, but derivative activities created using the Workflow Communication Activity tool (WCA.exe) can be used. See [Windows Workflow Foundation Tools](https://go.microsoft.com/fwlink/?LinkId=178889) for details.  
+- Due to limitations in the interface types that the <xref:System.Activities.Statements.Interop> activity can support, <xref:System.Workflow.Activities.HandleExternalEventActivity> and <xref:System.Workflow.Activities.CallExternalMethodActivity> cannot be used directly, but derivative activities created using the Workflow Communication Activity tool (WCA.exe) can be used. See [Windows Workflow Foundation Tools](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms734408(v=vs.90)) for details.  
 
 ## Configuring a WF 3 Activity Within an Interop Activity  
  To configure and pass data into and out of a WF 3 activity, across the interoperation boundary, the WF 3 activity’s properties and metadata properties are exposed by the <xref:System.Activities.Statements.Interop> activity. The WF 3 activity’s metadata properties (such as <xref:System.Workflow.ComponentModel.Activity.Name%2A>) are exposed through the <xref:System.Activities.Statements.Interop.ActivityMetaProperties%2A> collection. This is a collection of name-value pairs used to define the values for the WF 3 activity’s metadata properties. A metadata property is a property backed by dependency property for which the <xref:System.Workflow.ComponentModel.DependencyPropertyOptions.Metadata> flag is set.  

docs/framework/windows-workflow-foundation/overview.md

@@ -37,4 +37,4 @@ Workflow components in the host process
 
 ## See also
 
-- [BizTalk Server 2006 or WF? Choosing the Right Workflow Tool for Your Project](https://go.microsoft.com/fwlink/?LinkId=154901)
+- [BizTalk Server 2006 or WF? Choosing the Right Workflow Tool for Your Project](https://docs.microsoft.com/previous-versions/dotnet/articles/cc303238(v=msdn.10))