ASP.NET Errors Print

  • 0

Here are some typical isssues and solutions for ASP.NET developers. Pleasebe sure to consult your documentation as well.


Seeing error messages:


A very common issue for newbie .NET developers is the infamous .NET errormessage. By default your web.config file as well as the web server is set todisplay a "friendly" error message. This is for security reasons, because itwould otherwise display sensitive information regarding your website. E.G.Server paths, Datasource names application variables etc.. Unfortunately, thisalso causes problems when trying to figure out what's wrong with yourapplication!


The solution is simply to follow the on-screen instructions and make achange to your web.config file to display the pproper error message, It maytake 30 minutes for the error to be displayed, so please have patience. If youare still unable to see the error message or unable to figure out what itmeans, please open a support ticket:


Parent Paths:


If you enable Classic ASP, .NET1 or .NET2 we suggest you also check the box above to enable Parent Paths as it may be needed for legacy appplications.


Trust Levels:


ASP.NET1 or .NET2 users should note that we operate in a Medium Trust environment which means your scripts may not work correctly if they attempt to use some of the more advanced features for these languages. This is for security reasons and for everyone's benefit. Please attempt to work within Medium Trust by consulting your .NET documentation for solutions. There are very few applications that truely require a higher level of trust than medium. This will keep your application cleaner and portable. We will enable a higher level of trust, as needed, on a case-by-case basis.

Was this answer helpful?

« Back