Merge pull request #1760 from MicrosoftDocs/master-jdaly-7-3-19

Added note about .NET framework versions

Author: JimDaly

powerapps-docs/developer/common-data-service/org-service/visual-studio-dot-net-framework.md

@@ -2,7 +2,7 @@
 title: "Visual Studio and the .NET Framework (Common Data Service) | Microsoft Docs" 
 description: "Learn about managed code development tools and requirements."
 ms.custom: ""
-ms.date: 01/25/2019
+ms.date: 07/03/2019
 ms.reviewer: ""
 ms.service: powerapps
 ms.topic: "article"
@@ -21,6 +21,8 @@ The .NET SDK assemblies for Common Data Service are built on .NET Framework 4.6.
 
 You can use Visual Studio to build your managed code applications using .NET Framework 4.6.2 or later. 
 
+Plug-ins and custom workflow assemblies should use .NET Framework 4.6.2. While assemblies built using later versions should generally work, if they use any features introduced after 4.6.2 an error will occur.
+
 > [!IMPORTANT]
 > You should build any custom client applications using Microsoft .NET Framework 4.6.2 or later.
 > Only applications using Transport Level Security (TLS) 1.2 or better security are allowed to connect with Common Data Service. TLS 1.2 is not the default protocol used by .NET Framework 4.5.2, but it is in .NET Framework 4.6.2. 

powerapps-docs/developer/common-data-service/workflow/workflow-extensions.md

@@ -105,7 +105,9 @@ More information: [Install Visual Studio 2017](/visualstudio/install/install-vis
 
 These are general steps used to create a custom workflow activity using Visual Studio. For a complete step-by-step example see [Tutorial: Create workflow extension](tutorial-create-workflow-extension.md).
 
-1. Create a Workflow Activity Library project using .NET Framework 4.6.2 as the target framework
+1. Create a Workflow Activity Library project using .NET Framework 4.6.2 as the target framework.
+    > [!IMPORTANT]
+    > While assemblies built using later versions should generally work, if they use any features introduced after 4.6.2 an error will occur.
 1. Delete the Activity1.xaml file generated with the project
 1. Install the [Microsoft.CrmSdk.Workflow](https://www.nuget.org/packages/Microsoft.CrmSdk.Workflow/) NuGet package.
 

powerapps-docs/developer/common-data-service/write-plug-in.md

@@ -2,7 +2,7 @@
 title: "Write a plug-in (Common Data Service) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "Learn about the concepts and technical details necessary when writing plug-ins" # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
-ms.date: 06/20/2019
+ms.date: 07/03/2019
 ms.reviewer: ""
 ms.service: powerapps
 ms.topic: "article"
@@ -43,6 +43,10 @@ Content in this topic discusses the steps **in bold** above and supports the fol
 
 When creating assemblies keep the following constraints in mind.
 
+### Use .NET Framework 4.6.2
+
+Plug-ins and custom workflow assemblies should use .NET Framework 4.6.2. While assemblies built using later versions should generally work, if they use any features introduced after 4.6.2 an error will occur.
+
 ### Optimize assembly development
 
 The assembly should include multiple plug-in classes (or types), but can be no larger than 16 MB. It is recommended to consolidate plug-ins and workflow assemblies into a single assembly as long as the size remains below 16 MB. More information: [Optimize assembly development](/dynamics365/customer-engagement/guidance/server/optimize-assembly-development)