Showing posts with label appear. Show all posts
Showing posts with label appear. Show all posts

Monday, March 26, 2012

Trouble getting the ASP.NET error page to appear remotely

I have been developing a web application on a local host and then
using 'Copy Project' to copy all the files up to the ISP location.
When I run the application locally then all is OK. When I run the
application from the ISP site I get an runtime error.
Because the default page does not givem me any indication as to what
the actual problem is, then I change the web.config file using the
recommended custom error tags as follows:
<customErrors mode= "Off" />
This did not result in me getting the detailed page that would have
been displayed at the server on the ISP. So I tried to create a custom
page by creating a HTML file 'mycustompage.htm' and the modifying the
tag to give:
<customErrors mode= "RemoteOnly" defaultRedirect="mycustompage.htm" />
But the result is still the default page with no indication of error.
It is as if the application is not reading the web.config file.
The tag above had been entered inside the existing <system.web> tag.
Any help would be appreciated.
John L"John Lundrigan" <jonel@.glenavon1.demon.co.uk> wrote in message
news:gkqac05vk2ctuc2bchs18iru81muov4q21@.
4ax.com...
> I have been developing a web application on a local host and then
> using 'Copy Project' to copy all the files up to the ISP location.
> When I run the application locally then all is OK. When I run the
> application from the ISP site I get an runtime error.
...

> But the result is still the default page with no indication of error.
> It is as if the application is not reading the web.config file.
Maybe it isn't reading it. Try introducing a syntax error into the
web.config file and see if the syntax error is caught.
Are you sure your ISP has your app set up as an application in IIS?
--
John Saunders
johnwsaundersiii at hotmail

Trouble getting the ASP.NET error page to appear remotely

I have been developing a web application on a local host and then
using 'Copy Project' to copy all the files up to the ISP location.
When I run the application locally then all is OK. When I run the
application from the ISP site I get an runtime error.

Because the default page does not givem me any indication as to what
the actual problem is, then I change the web.config file using the
recommended custom error tags as follows:

<customErrors mode= "Off" /
This did not result in me getting the detailed page that would have
been displayed at the server on the ISP. So I tried to create a custom
page by creating a HTML file 'mycustompage.htm' and the modifying the
tag to give:

<customErrors mode= "RemoteOnly" defaultRedirect="mycustompage.htm" /
But the result is still the default page with no indication of error.
It is as if the application is not reading the web.config file.

The tag above had been entered inside the existing <system.web> tag.

Any help would be appreciated.

John L"John Lundrigan" <jonel@.glenavon1.demon.co.uk> wrote in message
news:gkqac05vk2ctuc2bchs18iru81muov4q21@.4ax.com...
> I have been developing a web application on a local host and then
> using 'Copy Project' to copy all the files up to the ISP location.
> When I run the application locally then all is OK. When I run the
> application from the ISP site I get an runtime error.
...

> But the result is still the default page with no indication of error.
> It is as if the application is not reading the web.config file.

Maybe it isn't reading it. Try introducing a syntax error into the
web.config file and see if the syntax error is caught.

Are you sure your ISP has your app set up as an application in IIS?
--
John Saunders
johnwsaundersiii at hotmail

Saturday, March 24, 2012

Trouble with ASP.net validation

I built this website. It works and the validation works. I want in addition to the star to appear the label on the left for the text to turn red.

www.nodebt.com

The old website which i did too in classic asp http://www.nodebt.com/form.asp - it works as i want it.I ran both pages. The old style changed the label to read and did not show the '*'.

In Microsoft's validators, you have limited formatting options. You can hide the '*' by setting the Display property to "none". You cannot automatically change the color of another field's label. You'd have to write code on the server side that detected if each validator IsValid property is false and change the style of the associated label. If you use the client-side validation (a benefit of ASP.NET), there isn't a clean hack to help you.

I wrote my productProfessional Validation And More for ASP.NET to solve these formatting limitations. I encourage you to review my site to learn what I've done and all the other limitations of Microsoft's validators so you can determine the best course of action. In my product, you can indicate the label and have it change to a different style when the error is shown. It works fully within client-side validation.