-
I have to build an integration solution that talks to BIG_NAME_FINANCIAL_SYSTEM via their API, which takes the form of a .NET framework 4.5.2 DLL. The vendor is not interested in building or providing a web API, nor are they interested in updating their code to .NET Core. My intention is to build a .NET Core background service that will pull data from/push data to this system, using their API. However I have essentially fallen at the first hurdle because The end result is that when I run my Core app that references BIG_NAME_FINANCIAL_SYSTEM's API DLL, their DLL throws a Yes, I know I can build a Framework app that references their API DLL, then exposes its own API which my Core app can then talk to - but that's another layer of indirection, and latency, and project to maintain, and hence I'd prefer to avoid that if at all possible. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
You can probably use this compat assembly that basically noops https://github.com/dotnet/corefxlab/tree/master/src/System.Web.Compatibility cc @ericstj |
Beta Was this translation helpful? Give feedback.
You can probably use this compat assembly that basically noops https://github.com/dotnet/corefxlab/tree/master/src/System.Web.Compatibility
cc @ericstj