Referencing .NET Framework DLL from .Net Core 3

Question

I have a .NET Framework library provided by a vendor (CyberSource payment processor - https://github.com/CyberSource/cybersource-sdk-dotnet).

This API is being referenced by an ASP.NET Core 3.0 application.

Everything compiles fine but when I attempt to call a method in the .NET Framework library, I get the following exception:

{"Method not found: 'Void System.ServiceModel.EndpointAddress..ctor(System.Uri, System.ServiceModel.EndpointIdentity, System.ServiceModel.Channels.AddressHeaderCollection)'."}

Things I've determined:

Vendor doesn't provide a .NET Core or .NET Standard -compliant library
Library source is not portable as-is to .NET Standard or .NET Core

Is there any reasonable way to make this work?

Ian Kemp - SO dead by AI greed · Accepted Answer · 2020-07-17 14:39:03Z

2

You can analyze the DLL with The .NET Portability Analyzer. If all classes and methods that the DLL uses are available in .NET Standard/.NET Core then CLR will be able to call those methods. But some apis are not yet ported and that can be what you are facing. If that's the case, you may be able to fork and rewrite the code to use APIs available in .NET Core 3.

edited Jul 17, 2020 at 14:39

Ian Kemp - SO dead by AI greed

1

answered Jan 9, 2020 at 22:24

Andrii Litvinov

13.4k4 gold badges56 silver badges62 bronze badges

Sign up to request clarification or add additional context in comments.

8 Comments

user1142433 Over a year ago

Portability Analyzer is giving a 75% portability report. It's not an option for us to rewrite their library at this point.

Andrii Litvinov Over a year ago

I have installed System.ServiceModel.Primitives package and EndpointAddress indeed does not have default ctor. Can you target net48 instead of netcoreapp3.1 if fork/modify is not an option? That can work.

user1142433 Over a year ago

Asp.Net 3 requires Core 3.0 - it's not compatible with net48.

user1142433 Over a year ago

Yes, I meant an api service proxy. WIll probably build it in .NET framework 4.x. :-/

Ian Kemp - SO dead by AI greed Over a year ago

@user1142433 Interested to hear how you got on with this, as I'm currently facing a similar problem. If you did get something working, it would also make a great self-answer to this question.

|

Collectives™ on Stack Overflow

Referencing .NET Framework DLL from .Net Core 3

1 Answer 1

8 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

8 Comments

Your Answer

Sign up or log in

Post as a guest

Related