locked
Super slow AXML editing RRS feed

  • Question

  • User165993 posted

    I got one big problem with Xamarin development on VS15 - .axml editing is so slow/freezing, even when i go to source and not designer it's still randomly freezes for few seconds, then executes key strokes i made and freezes again for few seconds. Is it even Xamarin causing this? Could i possibly use .xml extension instead for layouts and use default VS Xml editor, it works properly on regular xml's like strings.xml, etc.

    Edit: When it's frozen VS starts using ~27% of my CPU which is even higher than what android emulator uses.

    Monday, July 18, 2016 11:36 AM

Answers

All replies

  • User242158 posted

    Same problem!

    Friday, August 12, 2016 8:23 AM
  • User150892 posted

    +1

    Friday, September 16, 2016 6:34 AM
  • User213428 posted

    It seems to freeze for a while every time you save (I think it regenerates Resource.Designer.cs). So try to not save that often. Although, be careful not to go the designer view without having saved first, I lost my changes I did in the source tab when I did so.

    Sunday, September 18, 2016 5:44 PM
  • User221673 posted

    Had the same problem, turned out that Resharper was the sinner.. I suspended it and everything worked much faster..

    https://resharper-support.jetbrains.com/hc/en-us/articles/206546999-How-can-I-temporary-disable-turn-off-ReSharper-

    Thursday, September 22, 2016 2:30 PM
  • User296086 posted

    In Cycle 4 you could download a version without this problem.

    https://forums.xamarin.com/discussion/77992/axml-layout-designer-inside-visual-studio-keeps-loading-forever

    We already go through cycle 8 and the problem continues and it is no longer possible to download the version that was indicated in this post.

    It is impossible to work with software under these conditions.

    Is there any solution ?

    • Marked as answer by Anonymous Thursday, June 3, 2021 12:00 AM
    Wednesday, February 1, 2017 9:33 AM
  • User387088 posted

    This is still happening in VS2019, v16.3.0. Awfull experience

    Tuesday, September 24, 2019 3:36 PM