Merge pull request #4864 from MicrosoftDocs/main638338969487778750sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

powerapps-docs/developer/data-platform/dependent-assembly-plugins.md

@@ -1,7 +1,7 @@
 ---
 title: Dependent Assembly plug-ins (preview)
 description: Learn how to include more assemblies that your plug-in assembly can depend on.
-ms.date: 10/12/2023
+ms.date: 10/25/2023
 ms.reviewer: jdaly
 ms.topic: article
 author: divkamath
@@ -286,6 +286,10 @@ This command opens a dialog so you can select a NuGet package to update the plug
 
 ## Design notes
 
+Here a a few things to consider when creating plug-in packages.
+
+### Generating the NuGet package
+
 The Visual Studio project created using [pac plugin init](/power-platform/developer/cli/reference/plugin#pac-plugin-init) uses Visual Studio capabilities that enable generating NuGet Packages. This method uses the [SDK-style](/nuget/resources/check-project-format) project format. Power Platform Tools for Visual Studio uses the [Non-SDK-style](/nuget/resources/check-project-format) project format.
 
 You aren't required to use these tools to generate a NuGet package with your plug-ins. You can use whatever capabilities you choose to generate a NuGet package, but you must use the tooling available to upload the package to Dataverse.
@@ -295,6 +299,24 @@ More information:
 - [Create a NuGet package using MSBuild](/nuget/create-packages/creating-a-package-msbuild)
 - [NuGet pack and restore as MSBuild targets](/nuget/reference/msbuild-targets)
 
+### What not to include in your package
+
+You may experience an issue when creating and registering plug-in packages where standard Dataverse assemblies are included in your package resulting in an error at package registration time.
+
+> [!IMPORTANT]
+> Do not include the following Dataverse assemblies in your package. Doing so will result in an error when registering the package.
+>
+>  Microsoft.Crm.Sdk.Proxy.dll  
+>  Microsoft.Xrm.Sdk.dll  
+>  Microsoft.Xrm.Sdk.Workflow.dll  
+>  Microsoft.Xrm.Sdk.Data.dll  
+>  Microsoft.Crm.Sdk.dll
+
+Including any of these assemblies in the plug-in package results in the following error message when registering the plug-in package with Dataverse:
+
+   "PluginPackage can not contain assemblies included in the Microsoft.CrmSdk.CoreAssemblies or Microsoft.CrmSdk.Workflow nuget packages."
+
+You can correct this situation by following the information in this article, [Controlling dependency assets](/nuget/consume-packages/package-references-in-project-files#controlling-dependency-assets), so that these dependency assets are not included in your package. You'll need to mark the assembly reference using the \<PrivateAssets> tag in the project configuration file (.csprog).
 
 ## Using System.Text.Json