JAR Binding Project Settings: Target Framework: Nougat Android Class Parser: class-parse Android CodegenTarget: XamarinAndroid JAR Build Action: “InputJar” or “EmbeddedJar” (which is what I had read on Xamarin website).

When the “Build Action” is changed to one of these two the following compiler error is received... Error- CS0111 Type 'JniDbMgr' already defines a member called 'Release' with the same parameter types

Changed the JAR Build Action

New Binding Project Settings: Target Framework: Nougat
Android Class Parser: jar2xml Android CodegenTarget: XamarinAndroid JAR Build Action: “Embedded Reference Jar” or “Embedded Reference”

Gets a compile error saying that the “Build Action” must be “InputJar” or “EmbeddedJar”

Changed the Android Class Parser

New Binding Project Settings: Target Framework: Nougat Android Class Parser: class-parse Android CodegenTarget: XamarinAndroid JAR Build Action: “Embedded Reference Jar” or “Embedded Reference”

The Binding project now Compiles with this warning: “BINDINGSGENERATOR : warning BG8601: No packages found”

The Android Project (same Target Framework as Binding Project) fails to compile with multiple errors of CS0246 – The type or namespace name ‘Com’ could not be found. You can replace ‘Com’ in the error statement with others I am using like ISyncObserver. Yes, the Binding Project has been added to the Android Project’s “References”

Even though the Build fails with these errors, I can go into the code and type one of these “could not be found” types and intellisense finds them and shows me their available methods and members. As if they are found. Must be an issue with VS 2017.

The main issue here is the compile Error- CS0111 described at the beginning which I think is a JAR file issue.

asked 29 Jun, 09:10

BESpring's gravatar image

BESpring
141219
accept rate: 20%

I do not see anything inherently wrong with UltraLiteJ. You may need to tweak the bindings as described in this StackOverflow thread.

https://stackoverflow.com/questions/10579234/binding-project-for-ultralitejni12-jar-already-defines-a-member-error

(29 Jun, 14:02) Chris Keating

This link was a start. Of course ianywhere gets replaced with sap. The big issue with this example is the damn spaces between "class [@name='".

For the SAP people monitoring this thread, do you not have any documentation on setting up a 2017 UltraLite Univeral/Android app? This is something that should definitely be there as it is not an aberration but is SOP. I could find nothing on your websites about setting up the dev environment.

permanent link

answered 30 Jun, 12:02

BESpring's gravatar image

BESpring
141219
accept rate: 20%

FYI to anyone who lands here: You will need to add System.XML to the Binding Project's References List. This will get rid of several warnings in the BINDINGSGENERATOR File that appear to be important.

(05 Jul, 11:00) BESpring
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×68
×21

question asked: 29 Jun, 09:10

question was seen: 162 times

last updated: 05 Jul, 11:00