I have started using VS2022 recently. I'd like to use the diagnostic tool while debugging but the following message appears:
diagnostic tools does not support current debugging configuration
After some research, I found
The Diagnostics Tools window does not support the current debugging configuration
and
Visual Studio 2015 diagnostics tool does not support current debugging configuration
But they both concern VS2015. Note that in
Tool>options>debugging>general
the option
Diagnostic tool while debugging
is enabled (checked)
Does anyone has an idea on a potential solution? I'm using Python so far.
Related
I am using Visual Studio 2022 professional version 17.4.3. During debug, the diagnostic tool is empty and shows nothing. This issue only occurs in VS2022. VS2019 is working fine with diagnostic display running during the debug process. VS2019 window
Do I need to do any configuration for VS2022 to get this diagnostic tool to show progress like VS2019?
Using Visual Studio 2022 v17.1.3 and Microsoft Edge 99.0.1150.55
I was using Chrome to execute my ASP.NET projects and Javascript breakpoints worked. After switching to Edge, Javascript debugging stopped working.
I've followed suggestions in several stack articles, specifically this one with no results:
Visual Studio integrated Javascript debugging with Windows 10 Edge
My settings are all configured properly:
Options->Debugging->General
Project Properties
Does anybody have an updated 2022 fix for this?
I had the same problem until today. The solution for me and i think also for all of mankind is :-) to run your application not under the "Default Website" on IIS (Internet Information System). Your application must be configurated as a own Site with own Port on IIS. Here are some screenshots as example:
Configuration in IIS:
IIS Config
Configuration in Visual Studio for your "Start Project":
VS Config
Configuration in Visual Studio Code:
VS Code Config
I hope i could help all of you to solve the problem ;-)
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.
I'm getting the following error when connecting to visual studio online with tfs plugin:
org.apache.axis2.databinding.AFBException: Unexpected subelement InheritLevel
It seems like it does connect to VSO and this problem occurs when its loading the project information. I'm using the alternate connection method, which is already enabled on VSO. How can I fix this problem or do I have to switch to eclipse?
The IntelliJ plugin for TFS is based on the 2010 api and is not well supported. As TFS and VS 2010 are now no longer supported I would expect breakages. Other than putting pressure on JetBrains to fix it you can:
use Eclipse that has fully supported first part plugin
Use the command line out side of IntelliJ
Nether will be what you want, but it may be the best that you can get without Jet Brains fixing it.
Is it possible to use FxCop for .NET 4.5 applications?
I am looking to use FxCop with the Visual Studio 2013 Professional edition.
Visual Studio 2013 Professional comes with Static Code Analysis (which is FxCop, just a fancy name for it).
In this link some information is provided:
As a developer, you can run code analysis on your project automatically or you can run it manually.
To run code analysis each time that you build a project, you select Enable Code Analysis on Build (defines CODE_ANALYSIS constant) on the project's Property Page. For more information, see How to: Enable and Disable Automatic Code Analysis for Managed Code.
To run code analysis manually on a project, on the Analyze menu, click Run Code Analysis on ProjectName. For more information, see How to: Enable and Disable Automatic Code Analysis for Managed Code.
This version runs perfectly on .NET 4.5.
FxCop 1.36 is a standalone version of Code Analysis. Microsoft no longer supports or works on the standalone version and currently only working on the integrated version that is included in Visual Studio.
There is a Uservoice going on which asks Microsoft to update the standalone FxCop version. See this link.