Debugging | The Best C# Programmer In The World - Benjamin Perkins

CodeDom provider type could not be located

By Benjamin Perkins · December 25, 2016 · Debugging

Server Error in ‘/’ Application. Configuration Error Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately. Parser Error Message: The CodeDom provider type “Microsoft.CodeDom.Providers.DotNetCompilerPlatform .CSharpCodeProvider, Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35” could not be located. Source Error: […]

Read More →

Dynatrace Extension causes application crashes after WS2016

By Benjamin Perkins · December 7, 2016 · Azure, Debugging

Some customers have reported that since Windows Server 2016 their applications are crashing unexpectedly. Restarts and scaling did not help. This has been isolated to an issue with versions of the Dynatrace Extension (installed through the Azure portal) prior to v1.18. The current version of the extension is 1.18.1009 and old versions can be updated […]

Read More →

Troubleshooting a hung or long running WebJob

By Benjamin Perkins · December 7, 2016 · Azure, Debugging

If you can reproduce the slow running WebJob behavior you have hosted with your Azure App Service Web App, Mobile App or API App then you can find out why using the following article. Additionally, if the WebJob is in a hung state, skip right to the portion where you take the memory dump of […]

Read More →

Create a memory dump of your App Service when it consumes too much memory

By Benjamin Perkins · June 26, 2016 · App Service, Azure, Debugging

I have written a number of troubleshooting labs here, one of which is Lab 21: WinDbg – Memory Consumption. In this article I will identify how to capture a memory dump of a process that is consuming too much memory. In this case it is running on an Azure App Service Web App. NOTE: This […]

Read More →

Capture a Trace for troubleshooting Azure Portal issues

By Benjamin Perkins · June 26, 2016 · Azure, Debugging

If you ever need to capture trace from within the Azure Portal to troubleshoot an issue, here are the steps required to do that. Login to the portal here. Navigate to the step just prior to where the issue is happening. Press F5 or refresh. Press F12 to start the browser Developer Tools (IE and […]

Read More →

Remote debug your Azure App Service Web App

By Benjamin Perkins · June 26, 2016 · App Service, Azure, Debugging

I created a sample ASP.NET application that you can download from here that contains a slow running request, a handled and an unhandled exception. UPDATE: I wrote an article here about remote debugging in Visual Studio 2017 and ASP.NET Core here, titled “Remote debug your Azure App Service 2017 including ASP.NET Core”, JIC you are […]

Read More →

MEX Debugging Extension for WinDbg

By Benjamin Perkins · June 26, 2016 · Debugging

This has been my favorite WinDbg extension for a long time and I am very happy to see that it has been made public. It can be downloaded from here. To load the MEX extension, copy the MEX.DLL into the winext directory under which your WinDbg client is running. It can be placed any where […]

Read More →

Lab 21: Debugging a W3WP process with high memory consumption

By Benjamin Perkins · June 8, 2016 · Debugging, IIS

Setup: Install Debugging Tools for Windows – for WinDbg Install and configure CSharpGuitarBugs on an IIS server as described in Lab 1 Place PROCDUMP executable on the IIS Server Review memory dump collection process for W2K8 and W2K12 Lab 21.1 Open the main page of the CSharpGuitarBugs website so that a W3WP process is instantiated […]

Read More →

Lab 20: Debugging a low CPU hang W3WP process using WinDbg

By Benjamin Perkins · June 8, 2016 · Debugging, IIS

Setup Install Debugging Tools for Windows – For WinDbg Install and Configure CSharpGuitarBugs on an IIS server as described in Lab 1 Place PROCDUMP executable on the IIS Server Review Memory Dump using PROCDUMP on 2008R2 or 2012R2: Lab Open the CSharpGuitarBugs website Click on the ‘Enter Payment Information’ link and note about how long […]

Read More →

Lab 19: Debugging a high CPU hang W3WP process using WinDbg

By Benjamin Perkins · June 8, 2016 · Debugging, IIS

Setup Install Debugging Tools for Windows – For WinDbg Install and Configure CSharpGuitarBugs on an IIS server as described in Lab 1 Place PROCDUMP executable on the IIS Server Read this HOW TO here. Read about the !runaway command here and copy dbghelp.dll into the c:\temp directory Lab Open Task manager so that the CPU […]

Read More →

Cookie	Duration	Description
cookielawinfo-checkbox-analytics	11 months	This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional	11 months	The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary	11 months	This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others	11 months	This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance	11 months	This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
viewed_cookie_policy	11 months	The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.

The Best C# Programmer In The World - Benjamin Perkins

articles about C# and numerous other technologies

Tags: Debugging

CodeDom provider type could not be located

Dynatrace Extension causes application crashes after WS2016

Troubleshooting a hung or long running WebJob

Create a memory dump of your App Service when it consumes too much memory

Capture a Trace for troubleshooting Azure Portal issues

Remote debug your Azure App Service Web App

MEX Debugging Extension for WinDbg

Lab 21: Debugging a W3WP process with high memory consumption

Lab 20: Debugging a low CPU hang W3WP process using WinDbg

Lab 19: Debugging a high CPU hang W3WP process using WinDbg