DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones AWS Cloud
by AWS Developer Relations
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones
AWS Cloud
by AWS Developer Relations

Know Your Debugger Part 4: Modifying Your Application During Execution

Dane Morgridge user avatar by
Dane Morgridge
·
Sep. 30, 10 · Interview
Like (0)
Save
Tweet
Share
2.53K Views

Join the DZone community and get the full member experience.

Join For Free
In this installment of "Know your Debugger", I am going to show you one of the lesser known secrets of debugging with Visual Studio.  You can actually make changes to objects while execution is broken.  I have a simple block of code with a breakpoint set and when hit you can see that the int i is equal to 5.



Notice that I am writing the output to the console twice.  I will step past the first time and then while broken on the second Console.WriteLine call I will change the int value to 7.  This is done through the same dialog that you use when inspecting objects.  You can click into values and actually change them:



Changing 5 to 7:



Now that I have changed the value, I will step through and allow the Console.WriteLine to run producing the following output in the console window:



In addition to being able to do this inline, you can also do it from the Intermediate Window, the  Locals and Watch windows:



Now you might be thinking to yourself, this is cool and all but when would I ever actually use this?  I find it most useful when I am testing and need to try my code with different values without having to stop execution, make a change to a value and restart.  I have found the ability to do this to be invaluable when trying to track down a problem and build a fix.
Execution (computing) application

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • When to Choose Redpanda Instead of Apache Kafka
  • 5 Software Developer Competencies: How To Recognize a Good Programmer
  • Reliability Is Slowing You Down
  • Container Security: Don't Let Your Guard Down

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: