Visual Studio caughing up errors while I"m debugging - what brought this nuissance on Microsoft?

Scot King 116 Reputation points
2023-05-26T02:21:58.36+00:00

"The target process exited with code -2147023895....

If the problem happens regularly, consider disabling the Tools->Options setting Debugging->General->Enable property evaluation and other implicit function calls

I unchecked this option in tools debugging and it did NOT fix the problem. This is real inconvenience. What can I do? I need to see the VALUES in my variables.. It WAS working ok. Why does it now no longer work and I'm sitting here typing this post? Is it infected with a virus? Is this just some general glitch that gets worse as web pages get larger? My code behind page has 17k lines of code but I doubt that has anything to do with this debugging issue.

Visual Studio Debugging
Visual Studio Debugging
Visual Studio: A family of Microsoft suites of integrated development tools for building applications for Windows, the web and mobile devices.Debugging: The act or process of detecting, locating, and correcting logical or syntactical errors in a program or malfunctions in hardware. In hardware contexts, the term troubleshoot is the term more frequently used, especially if the problem is major.
945 questions
0 comments

5 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anna Xiu-MSFT 25,801 Reputation points Microsoft Vendor
    2023-05-26T06:40:49.41+00:00

    Hi @Scot King, 

    Welcome to Microsoft Q&A! 

    Which version of Visual Studio are you using? Please update your Visual Studio and rebuild the solution. 

    You can also refer to: Solution #1: Prevent the debugger from calling the getter property or ToString method. 

    Sincerely,

    Anna

    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". 
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

     

  2. Scot King 116 Reputation points
    2023-05-26T13:50:03.3333333+00:00

    I have rebuilt my program and it doesn't help. I still get this error message when I attempt to hover my mouse over any variable in my program. This is really annoying...

    I have also removed the check from Enable property evaluation and other implicit function calls. This does not help either. Shall I just now uninstall VS 2019? It is worthless to me without a solution to this problem.

    User's image

    User's image

  3. Scot King 116 Reputation points
    2023-05-28T14:23:29.5266667+00:00

    Because I keep backups, I loaded a backup of the program and attempted to recreate the changes I had made previously. It appears that VS doesn't like it when I add additional elseif code blocks to an already large page. I"m going to attempt to clear some variables at the end of a function call to see if that frees up memory on the stack.

  4. Scot King 116 Reputation points
    2023-06-20T03:01:56.9333333+00:00

    I have been able to debug my page only when I first go to another page and place some breakpoints on it and then view a few variables . Once I do this, I can then go to the page I"ve been working on and it will allow me to see variable values. Without first doing what I described, VS will show the pop up box. what is up with this?

  5. Quinones, Carlos 0 Reputation points
    2024-04-22T12:31:56.68+00:00

    Found the answer using CoPilot...

    1. Managed Compatibility Mode:
      • In some cases, enabling Managed Compatibility Mode can address debugging issues. To enable it:
        1. Go to Tools > Options.
          1. Navigate to Debugging > General.
            1. Check the box for Use Managed Compatibility Mode.
              1. Restart Visual Studio and try debugging again.

    Here is what Managed Compatibility Mode is and does:

    • When this mode is enabled, the debugger behaves more conservatively and avoids certain features that might cause issues with managed code debugging.
    • It helps address compatibility problems that can arise due to differences between the debugger's behavior and the behavior of older versions of the .NET runtime.
    • Specifically, it affects how the debugger evaluates expressions, inspects variables, and interacts with the runtime during debugging sessions.Found the answer using CoPilot...
      1. Managed Compatibility Mode: 
        - In some cases, enabling **Managed Compatibility Mode** can address debugging issues. To enable it:

      1. Go to **Tools > Options**.

            1. Navigate to **Debugging > General**.

                  1. Check the box for **Use Managed Compatibility Mode**.

                        1. Restart Visual Studio and try debugging again.
      Here is what Managed Compatibility Mode is and does:
      • When this mode is enabled, the debugger behaves more conservatively and avoids certain features that might cause issues with managed code debugging.
      • It helps address compatibility problems that can arise due to differences between the debugger's behavior and the behavior of older versions of the .NET runtime.
      • Specifically, it affects how the debugger evaluates expressions, inspects variables, and interacts with the runtime during debugging sessions.
    0 comments