Skip to content

Commit 5009d73

Browse files
authored
Merge pull request #8860 from MicrosoftDocs/phecke-patch-1
Removed broken link
2 parents 6544141 + 4572363 commit 5009d73

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

powerapps-docs/developer/data-platform/build-and-package.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Build and package plug-in code
33
description: Learn about building plug-in code into assemblies and packages for later registration and upload to the Microsoft Dataverse service.
4-
ms.date: 10/02/2023
4+
ms.date: 11/02/2023
55
ms.reviewer: pehecke
66
ms.topic: article
77
author: divkamath
@@ -30,8 +30,6 @@ Plug-in and custom workflow activity assembly projects must target .NET Framewor
3030

3131
Your assembly may include multiple plug-in classes (or types) and even custom workflow activities, but can be no larger than 16 MB in size. It's recommended to consolidate plug-ins and workflow assemblies into a single assembly as long as the size remains below 16 MB.
3232

33-
Best practice information: [Optimize assembly development](/dynamics365/customer-engagement/guidance/server/optimize-assembly-development)
34-
3533
### Signed assemblies are required
3634

3735
Assemblies must be signed before they can be registered with Dataverse only if you are not using the [dependent assemblies](#dependent-assemblies) capability. You can use the Visual Studio **Signing** tab in your project's properties or the [Sn.exe (Strong Name Tool)](/dotnet/framework/tools/sn-exe-strong-name-tool) command to sign the assembly.

0 commit comments

Comments
 (0)