Creating External DLL for Client Customization

I am creating logic to interface with an external web site to validate addresses. I started by embedding the code into a screen customization, but now I realize it could get quite unwieldly as I plan to use this code in many forms (order entry, customers, employees, vendors, etc).

When I try to reference the class from the screen customization, I receive error messages:

When project type is Class Library (.NET Core)
Error: CS0012 - line 59 (4320) - The type 'System.Object' is defined in an assembly that is not referenced. You must add a reference to assembly System.Runtime, Version=4.2.1.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a

When project type is Class Library (.NET Standard)
Error: CS0012 - line 59 (4320) - The type 'System.Object' is defined in an assembly that is not referenced. You must add a reference to assembly 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'.

I know there has been discussion on this forum about avoiding DLLs but I think in this case it is fairly safe to do this (it will just take address field input and output the fixed addresses and should not have any direct interaction with Epicor BOs).

Any idea on what I am missing? Do I need to locate copies of these files (if yes, any ideas where they exists)?

Thanks for any input!
Tanner

I made a DLL to log my customized forms in order to track who uses them, and how often…(just for statistics purposes ). I created my DLL as a class library (.Net framework)
because I had similiar errors when I chose class library (.Net standard)

I Copied the DLL under the Client folder, Added the Assembly to my customization and was able to call it’s public functions.

Pierre

2 Likes

Thanks! I will try a .NET framework library

@hogardy Thanks that worked!