Quantcast
Channel: Recent Threads — Xamarin Community Forums
Viewing all articles
Browse latest Browse all 204402

Can't build any bindings project after upgrade

$
0
0

A couple of weeks ago I upgraded Xamarin from 4.6 to 4.10. Since then I have been unable to compile a couple of bindings projects used to incorporate JARs in my solution. In fact no bindings project I create give useful output. The result is always the same: the build is "successful" and some interfaces and eventargs objects are created, but all others classes fail with a warning that it has "unknown base type java.lang.Object". I think the actual problem is occurring earlier in the build. With verbose output there is this: resolving assembly C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoAndroid\v1.0\mscorlib.dll System.ArgumentException: Value does not fall within the expected range. at System.Runtime.CompilerServices.RuntimeHelpers.InitializeArray(Array array, RuntimeFieldHandle fldHandle) at Mono.Cecil.Mixin.GetSize(CodedIndex self, Func`2 counter) at Mono.Cecil.PE.ImageReader.GetCodedIndexSize(CodedIndex index) at Mono.Cecil.PE.ImageReader.ComputeTableInformations() at Mono.Cecil.PE.ImageReader.ReadImage() at Mono.Cecil.PE.ImageReader.ReadImageFrom(Stream stream) at Mono.Cecil.ModuleDefinition.ReadModule(Stream stream, ReaderParameters parameters) at Mono.Cecil.ModuleDefinition.ReadModule(String fileName, ReaderParameters parameters) at Mono.Cecil.AssemblyDefinition.ReadAssembly(String fileName) at Xamarin.Android.Binder.CodeGenerator.Run(CodeGeneratorOptions options) C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoAndroid\v1.0\mscorlib.dll warning BG8200 : warning : failed to parse assembly {0}: {1}. For details, see verbose output

repeated for several assemblies, including Mono.Android.dll. VS2010 and Xamarin Studio give identical output. The result is identical if I create a brand new bindings project. I've tried installing Xamarin 4.8 instead with no change. I've tried re-installing 4.6 but it won't let me since it is incompatible (and I probably need to use the later version anyway). Updating the Android SDK and changing API target levels made no difference. I emailed support a week ago, but apart from a template reply (twice) asking for details and logs (which I replied to - twice) I've heard nothing.

Does anyone have any idea of anything else I can try to resolve this? I'm supposed to have this project finished by the end of the year, and at the moment with Xamarin non-functional I'm stuck!

Stuart


Viewing all articles
Browse latest Browse all 204402

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>