BEGIN:VCALENDAR PRODID:-//github.com/rianjs/ical.net//NONSGML ical.net 4.0//EN VERSION:2.0 BEGIN:VTIMEZONE TZID:America/Phoenix X-LIC-LOCATION:America/Phoenix END:VTIMEZONE BEGIN:VEVENT DESCRIPTION:Imagine this. You spend months iterating\, designing\, and bui lding the next revolutionary enterprise application. You roll out your so lution to a production environment that is locked down in a secure IT env ironment\, deployed to a cloud server\, or rolled out onto customer serve rs. Then in the height of your celebration\, the calls and support ticket s start rolling in. Your application is crashing. There are memory leaks. The CPU is spiking. You sit on the phone for hours trying to guide the u ser through some alternatives to get them back and running\, but the prob lems continue to persist. This would be so much easier if you could just launch Visual Studio to reproduce the problem\, but you can't. So what do you do? \; \; \; \;In this presentation\, we'll take an adva nced look at debugging production issues in .NET applications. Using real world scenarios and tools\, you will learn how you can monitor productio n systems\, capture data and memory dumps\, and explore the memory dumps using WinDbg and other tools to find problems. We will use demos of real- life badly behaving programs and walk through the problem resolution proc ess so that you can see how these techniques worked in real support cases . DTEND;TZID=America/Phoenix:20140405T104500 DTSTAMP:20260608T015339Z DTSTART;TZID=America/Phoenix:20140405T094500 GEO:33.293070;-111.796620 LOCATION:Chandler - Gilbert Community College - IRN-124 ORGANIZER: SEQUENCE:0 STATUS:CONFIRMED SUMMARY:Imagine this. You spend months iterating\, designing\, and buildin g the next revolutionary enterprise application. You roll out your soluti on to a production environment that is locked down in a secure IT environ ment\, deployed to a cloud server\, or rolled out onto customer servers. Then in the height of your celebration\, the calls and support tickets st art rolling in. Your application is crashing. There are memory leaks. The CPU is spiking. You sit on the phone for hours trying to guide the user through some alternatives to get them back and running\, but the problems continue to persist. This would be so much easier if you could just laun ch Visual Studio to reproduce the problem\, but you can't. So what do you do? \; \; \; \;In this presentation\, we'll take an advanced look at debugging production issues in .NET applications. Using real wor ld scenarios and tools\, you will learn how you can monitor production sy stems\, capture data and memory dumps\, and explore the memory dumps usin g WinDbg and other tools to find problems. We will use demos of real-life badly behaving programs and walk through the problem resolution process so that you can see how these techniques worked in real support cases. UID:d9319dfd-348e-46f8-8098-9c2f5ba0f8ff END:VEVENT END:VCALENDAR