From 8bcf7086d7e8661b20ccc9b83c5a3880515fb82b Mon Sep 17 00:00:00 2001 From: Connie Yau Date: Wed, 25 Oct 2017 15:38:16 -0700 Subject: [PATCH] Making relative link use home operation (#544) --- Documentation/compatibility/workflow-3_0-types-are-obsolete.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/compatibility/workflow-3_0-types-are-obsolete.md b/Documentation/compatibility/workflow-3_0-types-are-obsolete.md index c6914f2..cc73fd6 100644 --- a/Documentation/compatibility/workflow-3_0-types-are-obsolete.md +++ b/Documentation/compatibility/workflow-3_0-types-are-obsolete.md @@ -16,7 +16,7 @@ Windows Workflow Foundation (WWF) 3.0 APIs (those from the System.Workflow names - [x] Build-time break ### Recommended Action -New WWF 4.0 APIs (in System.Activities) should be used instead. An example of using the new APIs can be found [here](../../../../framework/windows-workflow-foundation/how-to-update-the-definition-of-a-running-workflow-instance.md) and further guidance is available [here](http://blogs.msdn.com/b/workflowteam/archive/2012/02/08/deprecatingwf3.aspx). Alternatively, since the WWF 3.0 APIs are still supported, they may be used and the build-time warning avoided either by suppressing it or by using an older compiler. +New WWF 4.0 APIs (in System.Activities) should be used instead. An example of using the new APIs can be found [here](~/docs/framework/windows-workflow-foundation/how-to-update-the-definition-of-a-running-workflow-instance.md) and further guidance is available [here](http://blogs.msdn.com/b/workflowteam/archive/2012/02/08/deprecatingwf3.aspx). Alternatively, since the WWF 3.0 APIs are still supported, they may be used and the build-time warning avoided either by suppressing it or by using an older compiler. ### Affected APIs * Not detectable via API analysis