userControl breaks on 404 page?

[darrel]

We have a bunch of usercontrols we are using on our site. One of them calls
functions in a compiled DLL (is that a 'resource' in VS.net terminology?)

The pages that contains all of these controls work just fine. We've made a
new page, error.aspx that we're going to use for our custom 404 page. If we
load/navigate directly to this page, no problem. If we get to this page via
IIS redirect (for page not found) the one control that depends on this
external DLL breaks. I think the issue has to do with it wanting to grab a
querystring/URL. But I'm not sure exactly, WHAT to look for. It appears that
the redirect process 'breaks' the url and the function can't 'see' it?

Does that sound familiar, or am I just making stuff up here? ;o)

Worse case scenario, we'll just put in an if page=error then ignore, but I
thought I'd check to see if there are any common issues with redirected
pages via .net and specific functions.

-Darrel

 

[Scott Allen]

Hi Darrel:

Can you define "breaks"? Is there an exception message?

 

[darrel]

Can you define "breaks"? Is there an exception message?

I think it was one of the genric 'instance of object not...' type of errors.
It wasn't specific at all.

This isn't actually a page I was working on but a co-developer. They just
gave up and wrote the page by hand instead of using the control, but I was
wondering if there was a common issue with error pages.

A bit of research indicates that a 404 error page isn't handled the same
way, but it's not very clear and doesn't really explain the issue we were
having.

Apologies for the vagueness of the question. ;o)

-Darrel