DFU use in C# (Xamarin.iOS)?

[jtth]

Debug-iphoneos.zip

Is it possible to both include and use the DFU component, inside the nRF-Toolbox, in a C# project?

Please advise or provide links on how-to.

[Mostafa Berg]

As per our email discussion, this is most probably an issue with Xamarin and iOS SDK 11.3, downgrade and use 11.2 or earlier to workaround the issue for now, can you please give some error logs on those warnings/errors you're receiving ? would be nice to know what these are:

jtth said:

The binding works and it generates the files, but both of the generated files do not build. Both are littered with errors. 49326 to put a # on it.

Thanks,

Mostafa

[jtth]

Sent. See attached

[Mostafa Berg]

Can't seem to build due to having the latest Xcode and iOS SDK which has that `bridgeos` bug, have you by the way taken a look at this blog post? might give a bit more insight?

medium.com/.../binding-swift-libraries-xamarin-ios-ff32adbc7c76 

[jtth]

The 'bridgeos' bug comes from not using the latest ver of Objective Sharpie. Please see link in which user 'trinnguyen' points this out and provides the link to manually install ver 3.4.23.

Likewise the link provided above (medium) returns 404.

Hope the long weekend was restful. Any news/and or updates Mostafa Berg ?

[jtth]

News, advances, breakthroughs?

[tesc]

Hi,

We do not have any news on this, unfortunately. As previously stated, Xamarin is a third party solution for which we have no official support and no experience. Despite of this we have tried our best to help you and tried to point you in the right directions for solving the issue. I am afraid at this point there is nothing more we can do.

Edit: I tried to fix the link to medium.com provided by Mostafa Berg in his last reply.

Regards,
Terje

[jtth]

Tesc,

Understandably the effort here to bind the library is considerable. Per previous discussion, Mostafa Berg seemed adamant that this was possible and willing to work towards a solution. But after receiving no response to the solution given for the build problem stated in the last post, and then having no communications in over three months, we figured this was too tall a request. In any case thanks for the reply.