Merge pull request #3701 from MicrosoftDocs/master-jdaly-2020-11-2

updates to plug-in topics

Author: JimDaly

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

@@ -2,7 +2,7 @@
 title: "Tutorial: Write and register a plug-in (Common Data Service) | Microsoft Docs" # Intent and product brand in a unique string of 43-59 chars including spaces
 description: "This tutorial is the first in a series that will show you how to work with plug-ins." # 115-145 characters including spaces. This abstract displays in the search result.
 ms.custom: ""
-ms.date: 02/23/2019
+ms.date: 11/03/2020
 ms.reviewer: "pehecke"
 ms.service: powerapps
 ms.topic: "article"
@@ -70,6 +70,12 @@ You need to use Visual Studio to write a plug-in. Use these steps to write a bas
     ![Install Microsoft.CrmSdk.CoreAssemblies NuGet Package](media/tutorial-write-plug-in-install-microsoft.crmsdk.coreassemblies.png)
 
 1. You must select **I Accept** in the **License Acceptance** dialog.
+
+    > [!NOTE]
+    > Adding the `Microsoft.CrmSdk.CoreAssemblies` NuGet package will include these assemblies in the build folder for your assembly, but you will not upload these assemblies with the assembly that includes your logic. These assemblies are already present in the sandbox runtime.
+    >  
+    > Do not include any other NuGet packages or assemblies to the build folder of your project. You cannot include these assemblies when you register the assembly with your logic. You cannot assume that the assemblies other than those included in the  `Microsoft.CrmSdk.CoreAssemblies` NuGet package will be present and compatible with your code.
+
 1. In **Solution Explorer**, right-click the `Class1.cs` file and choose **Rename** in the context menu.
 
     ![Rename class](media/tutorial-write-plug-in-rename-class.png)

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: 07/03/2019
+ms.date: 11/03/2020
 ms.reviewer: "pehecke"
 ms.service: powerapps
 ms.topic: "article"
@@ -61,6 +61,13 @@ All assemblies must be signed before they can be registered. This can be done us
 
 Plug-in assemblies must contain all the necessary logic within the respective dll.  Plugins may reference some core .Net assemblies. However, we do not support dependencies on .Net assemblies that interact with low-level Windows APIs, such as the graphics design interface.
 
+### Do not depend on any other assemblies
+
+Adding the `Microsoft.CrmSdk.CoreAssemblies` NuGet package will include these assemblies in the build folder for your assembly, but you will not upload these assemblies with the assembly that includes your logic. These assemblies are already present in the sandbox runtime.
+ 
+Do not include any other NuGet packages or assemblies to the build folder of your project. You cannot include these assemblies when you register the assembly with your logic. You cannot assume that the assemblies other than those included in the  `Microsoft.CrmSdk.CoreAssemblies` NuGet package will be present and compatible with your code.
+
+
 ## IPlugin interface
 
 A plug-in is a class within an assembly created using a .NET Framework Class library project using .NET Framework 4.6.2 in Visual Studio. Each class in the project that will be registered as a step must implement the <xref:Microsoft.Xrm.Sdk.IPlugin> interface which requires the <xref:Microsoft.Xrm.Sdk.IPlugin.Execute*> method.