Background: After I updated Xamarin Studio to version 6, my studio suddenly ceased to understand the code: almost everything was underlined in red, all using was written

"Using directive is unnecessary."

I did not understand the studio any code, even new projects Android App. Finding the same problem only here and seeing that there was no intelligible solution, I followed the example of the questioner and made a downgrade by installing Xamarin Studio 5.10.3. But this did not help, Xamarin still does not understand the code.

The problem itself: Xamarin red highlights almost all methods related to android. Hovering on any "using Android." He speaks

"error CS0103: The name 'Android' does not exist in the current context".

He says the same things about Activity, Bundle, SetContentView. I tried to install almost all versions of Xamarin 5.10. Also completely deleted and reinstalled the Android SDK. Nothing helps. Thanks in advance for your help. Problem

    1 answer 1

    In general, I did not understand how I managed to fix everything, but I’ll tell you what I did, what worked. After suffering enough time with this, I spat on Xamarin Studio and installed Visual Studio 2015 with the Xamarin SDK. There, too, problems began. Although the visual studio understood what an Android is, but when trying to build an application, it consistently produced the following errors:

    aapt.exe ended with code 1073741819

    java.lang.UnsupportedClassVersionError: com / android / dx / command / Main: Unsupported major.minor version 52.0

    I tried to update the JDK to the latest version, as advised on the network, but there were no changes. After that, I checked with hope Xamarin Studio and was surprised that he stopped issuing the old errors that I described in the question. Now he gave the same errors as VS2015. As a result, with third-party help and a tyke method, it was almost by chance that it all happened because of the availability of the Android SDK Build-tools version 24 (see image) . After its removal, such bugs ceased to occur and the application began to be assembled again in Visual Studio and in Xamarin Studio. Only here android emulators for some reason stopped running ... but that's another story.

    All because of her