You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The legacy system I'm integrating with currently only supplies 32-bit SDKs. It would significantly simplify things if I could make use of it directly in a Temporal activity vs having to wrap the library in an API that the activity calls out to.
The text was updated successfully, but these errors were encountered:
The issue with the extra targets (like Windows 32-bit, Windows ARM, Linux MUSL, etc) is that it adds bloat to the package because the NuGet package has to embed the full DLL for that distro/arch. The NuGet package is already 50MB compressed and each shared library we add is ~30MB (~10MB compressed). Also, I am not sure we test for 32-bit.
You may be able to build the SDK on 32-bit though and make your own package to depend on. I will leave this open for others to see, because it is possible we may ship a separate NuGet package in the future with 32-bit support. But there are no immediate plans for Windows 32-bit.
Describe the solution you'd like
Support for win-x86
Additional context
The legacy system I'm integrating with currently only supplies 32-bit SDKs. It would significantly simplify things if I could make use of it directly in a Temporal activity vs having to wrap the library in an API that the activity calls out to.
The text was updated successfully, but these errors were encountered: