Author: CuteKids | Posted on: 1/21/2010 12:25:18 AM | Views : 230

My application consists of a windows form application which controls web pages at my remote server.  The user downloads the windows form application on their PC.  I use the windows form web browser and its properties to navigate throughout my remote web application.
My problem is avoiding the remote debugging feature.  When my users encounter a web page problem, a generic panel ask if they wish to use Internet Explorer to debug.  If the user wishes, they can view my asp.net code and some script with this debugging feature.  Obviously, I do not wish that the user see any of my code.
The web pages are being controlled by windows form web browser and not directly by Internet Explorer.  Thus, web.config commands such as 'compilation debug = "false"' and 'customErrors defaultRedirect = "Generic.aspx" mode = "On"' are not preventing the remote debugging feature. Go to the complete details ...