Are we going to get used to this?

**Lunatic3** · Jun 6th, 2003, 02:27 AM

Are we going to get used to ASP.NET specific (yellow) errors in web pages around the world? I have come across lots of pages that break with that kind of errors. Frustrating!

**J Staniforth** · Jun 6th, 2003, 04:35 AM

Can you provide a few examples?

**Lunatic3** · Jun 6th, 2003, 05:28 AM

Well, I dont keep track of all pages with error. The latest one was:
http://www.aspfree.com/authors/gfweis/GetIdentity.aspx

**jesus4u** · Jun 6th, 2003, 08:31 AM

this is the result of not using try catches and deciding appropriately what you are going to do with errors.

**Lunatic3** · Jun 6th, 2003, 09:09 AM

Yes, but till now we were used to get javascript errors and such. And this is quite new and growing.

**Cander** · Jun 6th, 2003, 09:21 AM

I have to ask. Who cares? Its meaningless what the error looks like.

**J Staniforth** · Jun 6th, 2003, 10:08 AM

I think it does matter what the error looks like - its quite scary from a ordinary person to be presented with this! - and not helpful to them at all.
Besides, all that needs to be done it to configure the app in its config (amongst other places) to display custom error page.

**robdotnet00** · Jun 6th, 2003, 10:10 AM

YEah some errors can be trapped at least and you wont get that kind of message. However ive been getting some untrapable errors on some of my apps due to the webserver when certain dll get locked proablly b y viruse protectionnow that sucks

**Lunatic3** · Jun 6th, 2003, 10:14 AM

I have to ask. Who cares?

Sometimes it may show a weak code, not so good for a reputable web site.

Its meaningless what the error looks like.

And its ugly looking.

**J Staniforth** · Jun 6th, 2003, 10:18 AM

Just to clarify - its possible to configure a default error page for the whole app or indivual pages which is presented when unhandled errors occur.

**Cander** · Jun 6th, 2003, 10:24 AM

Originally posted by Lunatic3
Sometimes it may show a weak code, not so good for a reputable web site.

And its ugly looking.

That is why we have something called custom error pages.

**jesus4u** · Jun 6th, 2003, 10:25 AM

Originally posted by robdotnet00
YEah some errors can be trapped at least and you wont get that kind of message. However ive been getting some untrapable errors on some of my apps due to the webserver when certain dll get locked proablly b y viruse protectionnow that sucks

Just remember one word.....Finally.

**Lunatic3** · Jun 6th, 2003, 10:34 AM

That is why we have something called custom error pages.

See, We have at least two good way to avoid that page (trapping errors, and custom error pages) but still growing number of ugly error pages, what does it show?

**jesus4u** · Jun 6th, 2003, 10:37 AM

You know what is REALLY funny? From VS.NET IDE if you try to register your webservice with the UDDI you get the same ugly yellow error page coming from Microsoft's website!

**Cander** · Jun 6th, 2003, 10:39 AM

It doesnt show anything except an error that the site devlopers havent fixed and that didnt make a custom error page.

Again. Who cares? It doesnt effect your project what other people do.

And as far as it being ugly. There are more badly dsigned WORKING websites that are uglier.

**Lunatic3** · Jun 6th, 2003, 10:39 AM

**Lunatic3** · Jun 6th, 2003, 10:42 AM

It doesnt effect your project what other people do.

For sure it doesn't. I am talking about something new that we are going to face more and more in our every day web surfing...

**robdotnet00** · Jun 6th, 2003, 12:47 PM

Finally wouldnt even stop my prob it isnt even hitting the dll because it is locked. no code is being exucuted. Gotta find a asp.net friendly virus checker.

**jesus4u** · Jun 6th, 2003, 12:49 PM

Originally posted by robdotnet00
Finally wouldnt even stop my prob it isnt even hitting the dll because it is locked. no code is being exucuted. Gotta find a asp.net friendly virus checker.

I have friend over here that said that he had to totally uninstall Norton Antivirus because even with the Script Blocking turned off it still caused problems. Maybe that is your problem too?

**robdotnet00** · Jun 6th, 2003, 01:29 PM

I know when they disable it has no problems but when they have it on it locks my files. They policy of the company is to have virus checking on all servers active and up to date. I belive were using mcCafree. But iknow in general virus checking software doesnt like development environments in general. I just think maybe they need to put in place a policy that will not scan the files where i have my apps or skip scanning .dlls in that directory. Sometimes though the software locks parts of the .netframework too so its a fun situation.

**jesus4u** · Jun 6th, 2003, 01:34 PM

Originally posted by robdotnet00
I know when they disable it has no problems but when they have it on it locks my files. They policy of the company is to have virus checking on all servers active and up to date. I belive were using mcCafree. But iknow in general virus checking software doesnt like development environments in general. I just think maybe they need to put in place a policy that will not scan the files where i have my apps or skip scanning .dlls in that directory. Sometimes though the software locks parts of the .netframework too so its a fun situation.

Look into disabling the realtime scanning on your computer. That might help

**hellswraith** · Jun 7th, 2003, 11:12 AM

I think we will definately see more of them around the web as more people start using asp.net. It is super simple to fix, but there are reasons why maybe you want to show them still. For me, I can't debug on my hosting server. So therefor I need errors to show. I am implementing the error logging code from msdn which should help out some, but for testing purposes and catching all the bugs, I need the errors to show.

But, at least I do know how to turn them off and provide a custom error page when I need to do it. When I feel that I have caught 99% of the bugs, then I will turn on the custom error pages and not show those anymore.

Thread: Are we going to get used to this?

Thread Tools

Display

Are we going to get used to this?

Posting Permissions