jpobst
commented
1 year ago Thanks for trying out the prototype and providing feedback!
I've definitely received feedback that having to add a line for all transitive dependencies is a pain. I'd like to do something to ease that pain, but I haven't figured out what can safely be done for it.
Let's take your Square.OkIO example and automatically add okio-3.5.0.jar to your project. But perhaps another NuGet package you are using does use Square.OkIO C# bindings and has a transitive reference to the Square.OkIO version 2.10.0 NuGet package.
Now we are adding both okio-3.5.0.jar and okio-2.10.0.jar to the application, which won't compile. Theoretically we could arbitrarily pick one, like the newest 3.5.0, but that .jar may have breaking changes and it won't work with the Square.OkIO 2.10.0 C# bindings.
These are the kind of issues that prevent going down the fully automatic path. So, as a first step, we've started with forcing the user to create projects with "proper" dependency chains.
One future idea I was thinking about that may help alleviate the pain without causing other issues would be a dotnet global tool that would generate the initial full project(s) with all the transitive dependencies specified for you.
Example:
maven-bind com.walletconnect:android-core:1.20.0 WalletConnect.csprojThis would generate a csproj that has all the appropriate <AndroidMavenLibrary> or <PackageReference> lines for all transitive dependencies. This would get it done the first time (which is likely to be the most painful), but you would have to make any updates as needed when you move to a different version. Or I guess you could regenerate the whole thing from scratch for a new version.
vyacheslav-volkov
First of all thanks for this project, I really like the idea of slim bindings, I've been using my own slim bindings for years and it's much better than full C# binding for all Java types. Now, I'm using https://github.com/kezong/fat-aar-android to include all .aar files to a native library.
I tried to use this library to add
com.walletconnect:sign:2.18.0,com.walletconnect:android-core:1.20.0and in my opinion it is completely unusable in its current state. I have a native project written in Kotlin which uses these libs and I want to include all .aar dependencies in a .NET project to get my native project working. I get a lot of messages on dependencies and it is almost impossible to solve them all, moreover, if they update their library, I will have to repeat all the steps again to find all the dependencies and update them. Try including these libraries and you will understand me.My suggestions: It would be nice to automatically resolve all dependencies and add all .aar.jar files without manually describing them in .csproj, something like this (the same way like fat aar includes them):
and only show nuget package errors for critical packages like
Xamarin.AndroidX.., Xamarin.Kotlin.., etc. For example, I don't useSquare.OkIOat all from C# code, but it will show me an error that I need to install the nuget package instead of just including the raw .aar file. Perhaps you should add some kind of mode that will simply download and include all .aar files in the project, without matching them against all nuget packages, only the critical ones.Here is the list of libs that I added and gave up because the number of errors is growing exponentially:
here is the list of errors: