3 ms·
We're already using it to ship a large shared .NET codebase in a native Mac(SwiftUI) application. It's there and it works!
by meibo 4y ago
We're already using it to ship a large shared .NET codebase in a native Mac(SwiftUI) application. It's there and it works!
- JamesSwift 4y agoReally interesting. Any references to what you are doing / how you are doing it?
- meibo 4y agoNothing to link to yet, sorry, but we really just followed the "standard procedure" - it basically involved writing a C API to our business logic, which wasn't all too bad for us as the actual API surface we need isn't huge. You could of course circumvent that and use another IPC mechanism based on your preferences. In the end, we get a dylib that we can call like any other. A big pain point is debugging the generated native code, which isn't impossible but best to be avoided. I'd recommend having a good logging infrastructure in place and building abstractions that let you debug and test your .NET code without the UI layer.