Debugging in .NET - Glimpse
•Download as PPTX, PDF•
0 likes•1,027 views
"Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." -- Brian Kernighan. Join us as we try and defy the odds and make Debugging in .NET something that is fun once again. We will look at the various tricks and tools we can use to understand our site, find hard to get bottlenecks and much more.
More Related Content
Similar to Debugging in .NET - Glimpse
Similar to Debugging in .NET - Glimpse (19)
Recently uploaded
Recently uploaded (20)
Debugging in .NET - Glimpse
- 1. DEBUGGING IN
- 2. HELLO my name Anthony van der Hoorn is @anthony_v
- 3. DIAGNOSTICS is one of the hard things we do est
- 4. “Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enou debug it. ” -- BRIAN KERNIGHAN
- 5. 40 - time % 60 is of our debugging spent
- 13. debugging & haven„t really diagnostics changed in the last 20 Years
- 14. these don‟t evolution we address the have seen in the last 20 Years
- 15. too LOW LEVEL
- 20. runtime is only getting more COMPLICATED & COMPLEX
- 22. let„s do BETTER
- 25. know our ran the way we frameworks & code EXPECTED
- 29. let„s learn from the last 20 Years
- 30. ent er GLIMPSE
- 31. DEMO
- 35. 10,000 ft view 8,000 ft view HUD Timeline
- 36. 10,000 ft view 8,000 ft view 5,000 ft view HUD Timeline Tabs
- 37. 10,000 ft view 8,000 ft view 5,000 ft view 2,000 ft view HUD Timeline Tabs Trace
- 38. 10,000 ft view HUD Timeline 8,000 ft view 5,000 ft view Tabs 2,000 ft view Trace 1 ft view Existing Too
- 40. LEARNER
- 41. LEARNER DEBUGGER
- 46. browser cross
Editor's Notes
- This allows us to stop our program at any given point in time and look at the state of the application
- This allows us to stop our program at any given point in time and look at the state of the application
- This allows us to stop our program at any given point in time and look at the state of the application
- This allows us to stop our program at any given point in time and look at the state of the application
- This allows us to stop our program at any given point in time and look at the state of the application
- This allows us to stop our program at any given point in time and look at the state of the application
- This allows us to stop our program at any given point in time and look at the state of the application
- This allows us to stop our program at any given point in time and look at the state of the application
- One of the biggest realizations that we have had is that we now have information at different levelsIf we image that breakpoints and log files are the 1 foot view of our system What would we want to see if we jumped to the 10,000 foot view
- Another realization is that from a diagnostics point on view, we have different modes of developement
- A major realization that we had over the course of Glimpse’s lifecycle, is that if you take away the tabs we ship with, we have a diagnostics platformIf we agree that we like the type of insights that Glimpse provides is valuable, we start asking why can’t I have this for other frameworks and can I do this using Glimpse
- The next evolution of having a diagnostics platform is that we have an ecosystem of different frameworks that are supportedWhen you open your project, you should be able to download packages for each of the various frameworks you are using
- In a web context, most of the time, we are dealing with a click, which:starts on the browser, connects over the network,runs on the server,may connect to other services or data stores,comes back over the network,runs on the client till render,then any other events on the client after thatThis is the picture that we wanted to provide
- In a web context, most of the time, we are dealing with a click, which:starts on the browser, connects over the network,runs on the server,may connect to other services or data stores,comes back over the network,runs on the client till render,then any other events on the client after thatThis is the picture that we wanted to provide
- In a web context, most of the time, we are dealing with a click, which:starts on the browser, connects over the network,runs on the server,may connect to other services or data stores,comes back over the network,runs on the client till render,then any other events on the client after thatThis is the picture that we wanted to provide