Developed the project and at some point he stopped compiling. Since the studio does not write humanly, what exactly is an error in its opinion, just rolled back - deleted the added pages. But after that, the code nevertheless does not want to compile, displays errors that say that, in the studio’s opinion, the deleted pages are still alive somewhere else. Search ran through the contents of the project - nowhere information on the remote page (activit) is not found. Tell me how to tame this wild horse enter image description here

vOptions was an activation that I deleted. She is not searching anywhere. I rebuilt the project, cleaned the bin folder - it's useless.

  • This is common in Xamarin. I personally encountered this behavior when the versions of some packages did not match. It happened like this: the project is compiled and launched, you put an additional package, it pulls up the update of other packages, you put an update and ... everything arrived, everything that used to work now now does not compile and does not start because of a long list of such mistakes. - Bulson
  • And then I did not put anything new. Added a new activation, tested, stopped working. He deleted everything that is connected with this activation - he does not want to work. And in the mistakes of complete nonsense. Conclusion - go to the android studio and score on xamarin - Antykus
  • @Antykus delete all bin and obj folders. - Dev
  • @Dev try. And you do not know if you can teach the studio to display a description of the error in case of errors? Now he just writes that there is an error - Antykus 8:49 pm
  • @Antykus if the error is in the general project, then it will usually be displayed. If in the platform, then this happens (especially androyd). See the device log. sometimes helps. - Dev

1 answer 1

What helped:

- перенёс папку проекта из дефолтного расположения в другое место - кучу раз удалял папки bin и obj (они были в трёх папках: в главной, в андроидовской и в iOS) - чистил солюшн - перестраивал солюшн 

In short, he dug as hard as he could, sentencing the Old-Sumer spells in a whisper, it seems even accidentally summoned some kind of demon, but not the essence. And in the end, with the next compilation, the program on the device opened.

  • one
    Well, congratulations. And I have a year and a half ago, such adventures fought off any desire for further exploration of Xamarin. Can I try again? - Bulson 4:05 pm
  • @Bulson Honestly, I’ve come across this: I’ve come across three times this kind of behavior of this system, I’ve been tormented a lot and every time I told myself that’s enough, it’s enough to spend time But then some insight came that something else could be tried, and as a result, the project came to life and advanced ... until it came to a dead end again. It seems to me that Xamarin has a prospect, and besides, it is very warm to use the knowledge of C #. But the prospect of spitting and going completely to the android studio is still looming - Antykus
  • It is clear that since then, little has changed. Do you use Xamarin.Forms or Xamarin.Android? - Bulson
  • @Bulson Xamarin.Forms - Antykus
  • Understood thanks. - Bulson