I'm facing performance issues when editing xaml files (views, styles, app.xaml, ...) in Visual Studio 2015.
If a xaml file is open I got a really nasty delay when typing or scrolling, even in other files. Also my CPU goes up and IntelliSense is not loaded. When I close all xaml files then everything just go back to normal performance, also in other files like .cs or .resw.
After a while I got an error that say "An exception has been encounterd. This may be caused by an extenstion". And yes, I've looked in the ActivityLog.xml file, but I couldn't figure it out. There where 2 errors, 1 with a source of "ClientRights (Client rights determined)" and 1 with "Editor or Editor Extension (System.NullReferenceException)"
I'm running Windows Version 1607 (OS Build 14393.222) and Visual Studio 2015 Update 3.
I have the feeling that it all started when I installed update 3, not quite sure if that has something to do with it, it's been a while when I've been in a xaml project (in this case UWP).
It must be something to do with the XAML designer, although I disabled it.
These are the steps I've already tried:
Disable extenstions (some couldn't be disabled)
Uninstalled Resharper
New install of vs2015 Update 3
Found on stackoverflow (Visual Studio 2015 is extremely slow):
Disable XMAL designer (Options > XAML Designer - uncheck "Enable XAML Designer")
Disable solution analysis (Options > C# > Advanced - uncheck "Enable full solution analysis")
Disable CodeLens (Options > Text Editor > All languages - uncheck "Enable CodeLens")
Clear asp.net caches
Anyone facing the same problem? Any help would be very appreciated
New install of vs2015 didn't help.
Fresh install of win10 + vs2015 did the job :-(
Lost many hours but back running!
Related
EDIT: Good information provided below to diagnose, but the issue was I was running Visual Studio 2022 17.3. Version 17.4 is required for .NET 7, and I had just installed that. Once I installed the latest version of VS, all my problems went away. Install with Visual Studio
Suddenly today, debugging my ASP.NET Core 6 and 7 apps suddenly has stopped working. I hit F5 to debug, it stops on my breakpoint, but as soon as I continue or step into, I'm shown this dialog:
I haven't made any changes to code, I'm simply trying to continue after I've stopped at a breakpoint. This just started happening today and I can't figure out what I did.
I haven't made any changes to code, I'm simply trying to continue
after I've stopped at a breakpoint. This just started happening today
and I can't figure out what I did.
Well, if your visual studio stop working for debugging all type of application, please check following configuration:
1. Tools > Options > Debugging > .NET/C++ Hot Reload
2. Tools > Options > Projects and Solutions > ASP.NET Core >
Furthermore, If you select the Always rebuild option in the dialog box, you won't see the dialog box again in the current Visual Studio session, and Visual Studio will automatically rebuild and reload instead of showing the dialog box.
Note:
In addition, as you can see above in the first release of Visual Studio (version 17.0) the standard Edit and Continue dialog is still shown when using Hot Reload with the debugger. This was a bug and has been resolved starting with 17.1 Preview 2 release.
If you still need more details about the issue you are having with, I would higly recommend you to check our official document here.
If issue still perist:
After checking above configuration, if your issue still persists and if you are not using Visual Studio (version 17.0) then you still reset your unknown setting in visual studio as following:
Go to Tools > Import and Export Settings.
Then No, just reset settings
Finally, restart Visual studio.
You can get more details here.
with VS 2015 Enterprise i get always following message on a solution while debugging: XAML Visual Diagnostic is either disabled or is not supported by the current application
Tools - Options - Debugging - General:
Enable UI Debugging Tools for XAML is enabled
Preview selected elements in Live Visual Tree is enabled
I have tried:
VS Restart
Clean Solution / Rebuild
Fresh Checkout
Curious: If i start the solution without debugging and i attach the debugger to the process, it works ...
Update:
If i select "Enable native code debugging" in project settings - debug, it works !
I needed an additional debugging option to be disabled in order for the tools to work with my projects:
Tools - Options - Debugging - General:
Use Managed Compatibility Mode --> disabled
I also faced this problem for some WPF projects that came to my pc from various sources. In my case the problem was in the project target framework - it was set to .NET Framework 3.5. The Live Visual Tree and the Live Property Explorer in VS 2015 do not work with .NET 3.5:
Inspect XAML properties while debugging
https://msdn.microsoft.com/en-us/library/mt270227.aspx
So I just changed the target framework to .NET Framework 4.0 in the project properties dialog (the Application tab) to make these 'live' tools work.
I faced the save issue on VS 2019. It happened all of a sudden on a project which it used to work on. Restarting VS did not help. But it got resolved after PC restart.
If you're having that problem in VS 2017 while debugging on a remote machine, installing the Visual C++ 2017 Redistributable (x64 in my case) made UI debugging work.
I always had this VM where UI debugging worked but my colleagues couldn't get it to work on their machines until I was experimenting with something where I had to uninstall all redistributables. After finishing my experiments I realized I couldn't debug the UI anymore. I reinstalled the 2017 redistributable and the functionality got enabled again.
Having been quite spoilt by this excellent add on for VS 2013, it has come of something of a shock to find that there is absolutely no Xaml intellisense when using vs 2015 RC.
in the options I have made sure that it is selected:
and that the designer is used as the default when editing my views;
I have started and restarted Visual Studio several times and yet intellisense remains stubbornly inactive when creating Xaml ( NB it is fine when writing either VB or C# code).
Has anyone else experienced this and found a solution?. Visual Studio 2013 is still on my machine, but the two should work happily side by side, indeed my experience is that they do bar this little matter of no intellisense for xaml.
Thanks
Uncheck Enable XAML designer, restart VS; then check Enable XAML designer again and restart VS again, the Intellisense comes out. This works for me. :)
I also experienced this and my solution was to reset the environment settings using the Import and Export Wizard. Tools->Import and Export Settings. And then clicking on "Reset all settings".
Deleting the .suo file and restarting Visual Studio (20015 rc) solved this for me.
When I open my project that uses a MahApps.Metro window in "Blend for Visual Studio" I get tons of errors. One of them is (this one probably causes all the other errors):
The name "MetroWindow" does not exist in the namespace "clr-namespace:MahApps.Metro.Controls;assembly=MahApps.Metro"
This same project works fine in Visual Studio 2012. Additionally, all resources in Blend have a warning icon. How could I fix this?
Any help would be appreciated.
I fixed it. I changed the debug platform on all the projects in my solution to Any CPU like this:
Opened the project in both Visual Studio and Blend
Opened the Configuration Manager (drop down menu beside debug/release "Start" button)
One of the projects' debug platform was set to x86 so I clicked on <new...>
Set New Platform to Any CPU
Set Copy Settings From to <Empty>
Clicked Ok
Blend then asked me to reload the project and I clicked on Yes To All
"Unable to start debugging 'C:\Windows\System32\WWAHost.exe'. The Microsoft Visual Studio Remote Debugging Monitor (MSVSMON.EXE) does not appear to be running on the remote computer. This may be because a firewall is preventing communication to the remote computer. Please see Help for assistance on configuring remote debugging."
Searched for similar posts, but didn't found one. If duplicate just inform.
I am not trying to connect to any remote machine. Just testing on my local machine.
Is there any way to solve this issue. (I'm using Windows 8 Enterprise 64-bit, just a javascript project)
Problem solved. Installed Remote tools update from here and working fine. Thanks for responding. Closing the topic.
I had the same problem. I fixed it by changing properties/compile/target platform to x86 instead of Any CPU. It solved the problem in my case. Hope it helps.
This happened to me just now when I had a website set up in IIS for mydomain.com, and set my project's start up url (Local IIS) to mydomain.com, and then launched the project before remembering to add a record in the host files for the domain:
127.0.0.1 mydomain.com
This got me for a good hour before I remembered I never set the record. Adding the record fixed it right away.
Windows 7 x64, VS 2012
In my case, the Remote Debugging Monitor component was installed and the app was clearly configured to debug locally in settings. This was a WinForms app upgraded from VS 2008, .NET 3.5.
Turns out it was the Windows Firewall. By directly running:
C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\Remote Debugger\x64\msvsmon.exe
A firewall dialog appeared where I could allow msvsmon.exe to run. After a VS 2012 re-start, debugging (locally) was fine!
Ensure you have Local Machine selected in this drop-down menu:
Windows 7 x64, VS 2012, VB.NET
I fixed it like this:-
Create a shortcut on your desktop to "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\Remote Debugger\x64\msvsmon.exe".
Right-click shortcut and select "Properties" from the dropdown menu. Select the "Compatibity" tab, tick "Run this program as administrator" and click OK
Create a shortcut on your desktop to "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\devenv.exe".
Right-click shortcut and select "Properties" from the dropdown menu. Select the "Compatibity" tab, tick "Run this program as administrator" and click OK.
To start VS2012:-
Double-click the msvsmon shortcut icon (that you created above, to launch msvsmon). Wait for the "Visual Studio Remote Debugging Monitor (Administrator)" window to display before continuing ...
Double-click the "Visual Studio 2012 Professional" shortcut icon (that you created above, to launch VS2012)
In VS2012, ensure standard toolbar is visible.
In VS2012, ensure "Solution Platforms" dropdown (on standard toolbar) is visible and set to "x86".
and debug now works (for me anyway) ...
However after 15 minutes or so, debug may stop working and you may get the msvsmon error again. If that happens, simply close VS2012 and msvsmon and then start again (from "To start VS2012:-" above) ...
Myself and several other developers have been trying to look for a solution for this problem for about 3/4 hours as Visual Studio crashed then this error would occur (twice in 2 days). I then suddenly (after a lot of debugging and trying other suggestions and headbanging) I somehow realised that the file which was highlighted had changed and when I was trying to debug was not the MVC app project, once I changed it to my project's one it then worked.
Hope this helps and saves people from hours of pain!
I also got this error, I usually run sites under a named user (which is also a database user) and forgot to set the Application Pool. (parliament's answer also helped me)
For me this worked in VS2013:
Save your work, close Visual Studio then reopen your project
I encountered this error as well.
The cause of mine was that I had accidentally emptied out the following property
Properties->Debugging->WorkingDirectory
Changing it to:
inherit from parent or project defaults
Solved the issue.
If you are using Microsoft's Azure, try attaching manually the debugger:
I have outlined the steps in the following answer:
https://stackoverflow.com/a/35738995/1057052