I am trying to add a custom .dll to a client-side customization. When I add the .dll as a custom assembly, it works fine. However, when I try to go back into the assembly reference manager, it gives me an error saying that my .dll already exists. The customization appears to be functioning correctly with the exception of this error when I open the customization in developer mode and access the assembly reference manager. I also noticed that epicor moved my .dll from the custom assemblies to the native assemblies. Has this ever happened to anyone else?
Related Topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| More Native Assemblies/References in one environment | 2 | 430 | September 10, 2019 | |
| How to Add "System.ServiceModel" Assembly Reference to Customization | 3 | 11105 | February 24, 2020 | |
| Referencing custom assembly / dll in E10 | 1 | 306 | July 4, 2024 | |
| Adding an assembly for Microsoft.Office.Interop.Outlook | 7 | 2398 | October 30, 2013 | |
| Auto-rebuild customizations on load | 8 | 1119 | August 2, 2019 |