All geek questions in one place

An unrelated XAML file is very slow when switching to another file

if I modify XAML and leave it unsaved to switch to another file. Visual Studio freezes for about 10 seconds before becoming responsive again. Therefore, I am spending too much time on development and demographics for development.

Is there any solution?

+4
source share
3 answers

Visual studio is not a XAML editor, and especially if you turn on the xaml interface view, it will be slower ... Therefore, it’s better to turn off the xaml user interface view and edit it manually. Use the blend expression if you want to edit XAML by looking at its interface.

Joy

+1
source

The only workaround I found was to press F5 to debug, and then immediately press Ctrl + Break to cancel the build. F5 automatically saves all unsaved files and for some reason does not cause a 10-20 second lock, which I get when I save or go over unsaved files normally.

This is an annoying habit to penetrate, but it saves a little time and frustration.

+2
source

I have the same problem and we are not alone:

http://connect.microsoft.com/VisualStudio/feedback/details/376583/ctrl-tab-between-forms-slow-with-unsaved-xaml-files

http://connect.microsoft.com/VisualStudio/feedback/details/585430/vsip-visual-studio-builds-xaml-files-on-saving

The problem is that, despite the fact that this problem was reported back in 2008, there is no workaround, and MS does not seem to care. :-(

0
source

Source: https://habr.com/ru/post/1384681/

More articles:


All Articles