472,958 Members | 2,373 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 472,958 software developers and data experts.

validation controls not working on production server

I recently deployed a web application which contains a user registration
form with the usual fields: name, address, email, password, etc. Each of the
TextBoxes uses a validation control to verify the input. On my development
server, this form works precisely as expected.

When I deploy the app to the production server (a hosting service), the
client-side validation quits working altogether. Now, I KNOW that scripts
are enabled and working in my browser (I use the same browser to access the
app on both development and production servers), and I've changed NOTHING
whatsoever before uploading the application. All other functionality works
the same on both servers.

Any help with this issue would be greatly appreciated.

---e[ch]
Nov 17 '05 #1
4 4458
It is most likely your WPP does not have the JavaScript scripts installed in
your application space. This is done with aspnet_regiis. If I remember
correctly, the correct flag for scripts is /c. Without the scripts
installed, you will either have to subclass the validation controls to point
at your own copies of the script, or ditch client side validation
altogether.

Now I will add a note about how to properly use validation. Despite having
Client Side validation, you should always check Page.IsValid prior to
submitting any code. This stops hackers from working around your form
validation to get errors to figure out your code, et al.

The Client side script is still useful, albeit when working, as it reduces
load on the server from multiple trips for validation. NOTE that validation
does not work, client side, in all browsers. This alone is a good reason for
server side checking.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

************************************************** ********************
Think Outside the Box!
************************************************** ********************
"earwicker" <ea*******@sbcglobal.net> wrote in message
news:xW*************@newssvr22.news.prodigy.com...
I recently deployed a web application which contains a user registration
form with the usual fields: name, address, email, password, etc. Each of the TextBoxes uses a validation control to verify the input. On my development
server, this form works precisely as expected.

When I deploy the app to the production server (a hosting service), the
client-side validation quits working altogether. Now, I KNOW that scripts
are enabled and working in my browser (I use the same browser to access the app on both development and production servers), and I've changed NOTHING
whatsoever before uploading the application. All other functionality works
the same on both servers.

Any help with this issue would be greatly appreciated.

---e[ch]

Nov 17 '05 #2
greg---

Thanks for your reply, but in the interim I have learned that you are not
entirely correct. You say:

"you will either have to subclass the validation controls to point

at your own copies of the script, or ditch client side validation

altogether."

This is false. You needn't go through the pain of subclassing the controls
at all. All you need to do is upload your own copy of WebUIValidation.js
(and the SmartNav script files, too, if you need them) to some directory
within your web application, and add the following line to your web.config
file:

<webControls
clientScriptsLocation="YourApp/YourScriptsDirectory/" />

And voila! It all works fine. Quick, easy, and painless.

Don't configuration files rock???

Thanks for your help,

---earwicker[ch]



"Cowboy (Gregory A. Beamer)" <No************@comcast.netNoSpamM> wrote in
message news:<OP**************@TK2MSFTNGP10.phx.gbl>...
It is most likely your WPP does not have the JavaScript scripts installed in your application space. This is done with aspnet_regiis. If I remember correctly, the correct flag for scripts is /c. Without the scripts installed, you will either have to subclass the validation controls to point at your own copies of the script, or ditch client side validation altogether. Now I will add a note about how to properly use validation. Despite having Client Side validation, you should always check Page.IsValid prior to submitting any code. This stops hackers from working around your form validation to get errors to figure out your code, et al. The Client side script is still useful, albeit when working, as it reduces load on the server from multiple trips for validation. NOTE that validation does not work, client side, in all browsers. This alone is a good reason for server side checking. -- Gregory A. Beamer MVP; MCP: +I, SE, SD, DBA


Nov 17 '05 #3
It is most likely your WPP does not have the JavaScript scripts installed in
your application space. This is done with aspnet_regiis. If I remember
correctly, the correct flag for scripts is /c. Without the scripts
installed, you will either have to subclass the validation controls to point
at your own copies of the script, or ditch client side validation
altogether.

Now I will add a note about how to properly use validation. Despite having
Client Side validation, you should always check Page.IsValid prior to
submitting any code. This stops hackers from working around your form
validation to get errors to figure out your code, et al.

The Client side script is still useful, albeit when working, as it reduces
load on the server from multiple trips for validation. NOTE that validation
does not work, client side, in all browsers. This alone is a good reason for
server side checking.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

************************************************** ********************
Think Outside the Box!
************************************************** ********************
"earwicker" <ea*******@sbcglobal.net> wrote in message
news:xW*************@newssvr22.news.prodigy.com...
I recently deployed a web application which contains a user registration
form with the usual fields: name, address, email, password, etc. Each of the TextBoxes uses a validation control to verify the input. On my development
server, this form works precisely as expected.

When I deploy the app to the production server (a hosting service), the
client-side validation quits working altogether. Now, I KNOW that scripts
are enabled and working in my browser (I use the same browser to access the app on both development and production servers), and I've changed NOTHING
whatsoever before uploading the application. All other functionality works
the same on both servers.

Any help with this issue would be greatly appreciated.

---e[ch]

Nov 17 '05 #4
greg---

Thanks for your reply, but in the interim I have learned that you are not
entirely correct. You say:

"you will either have to subclass the validation controls to point

at your own copies of the script, or ditch client side validation

altogether."

This is false. You needn't go through the pain of subclassing the controls
at all. All you need to do is upload your own copy of WebUIValidation.js
(and the SmartNav script files, too, if you need them) to some directory
within your web application, and add the following line to your web.config
file:

<webControls
clientScriptsLocation="YourApp/YourScriptsDirectory/" />

And voila! It all works fine. Quick, easy, and painless.

Don't configuration files rock???

Thanks for your help,

---earwicker[ch]



"Cowboy (Gregory A. Beamer)" <No************@comcast.netNoSpamM> wrote in
message news:<OP**************@TK2MSFTNGP10.phx.gbl>...
It is most likely your WPP does not have the JavaScript scripts installed in your application space. This is done with aspnet_regiis. If I remember correctly, the correct flag for scripts is /c. Without the scripts installed, you will either have to subclass the validation controls to point at your own copies of the script, or ditch client side validation altogether. Now I will add a note about how to properly use validation. Despite having Client Side validation, you should always check Page.IsValid prior to submitting any code. This stops hackers from working around your form validation to get errors to figure out your code, et al. The Client side script is still useful, albeit when working, as it reduces load on the server from multiple trips for validation. NOTE that validation does not work, client side, in all browsers. This alone is a good reason for server side checking. -- Gregory A. Beamer MVP; MCP: +I, SE, SD, DBA


Nov 17 '05 #5

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

0
by: Juma | last post by:
Hi, I have an have an application at a production server that is running on the .NET Framework 1.1.The version which I used while developing the application was 1.0. For some reason the...
3
by: Juma | last post by:
Hi, I have an have an application at a production server that is running on the .NET Framework 1.1.The version which I used while developing the application was 1.0. For some reason the...
0
by: Juma | last post by:
Hi, I have an have an application at a production server that is running on the .NET Framework 1.1.The version which I used while developing the application was 1.0. For some reason the...
2
by: Martyn Fewtrell | last post by:
Dear All I have a Windows 2003 Server with IIS6 where the validation controls on ASP.Net pages no longer work. I believe it to be specific to the server as if I create an ASP.Net page on the...
4
by: Craig HB | last post by:
I have build a web form using asp.net validation controls to make sure the users fill in the required fields and enter a valid email address for one of the fields. This works when I test it on...
6
by: charliewest | last post by:
In my development environment, the validation controls work fine. (Incidentally, i am using almost all of them). However, when i deploy my ASP.NET application to the live production environment,...
2
by: AnandaSim | last post by:
Hi All, A really puzzling phenomenon. I develop to a Windows 2000 development server in VS 2003. I use Copy Project to deploy the project to a production server. The webpage I'm having...
5
by: Kyle | last post by:
On my Development System, all the page validation controls work fine (WinXP Pro + SP2, VS.NET 2003, .NET v1.1.4322). On the Production System, none of the page validation controls are working...
3
by: Just D. | last post by:
All, Did anybody see this bug? We're having two login pages in a huge application, both are with validation controls. Everything works just great on two developer's machines working under...
0
by: lllomh | last post by:
Define the method first this.state = { buttonBackgroundColor: 'green', isBlinking: false, // A new status is added to identify whether the button is blinking or not } autoStart=()=>{
2
by: DJRhino | last post by:
Was curious if anyone else was having this same issue or not.... I was just Up/Down graded to windows 11 and now my access combo boxes are not acting right. With win 10 I could start typing...
0
by: Aliciasmith | last post by:
In an age dominated by smartphones, having a mobile app for your business is no longer an option; it's a necessity. Whether you're a startup or an established enterprise, finding the right mobile app...
2
by: giovanniandrean | last post by:
The energy model is structured as follows and uses excel sheets to give input data: 1-Utility.py contains all the functions needed to calculate the variables and other minor things (mentions...
4
NeoPa
by: NeoPa | last post by:
Hello everyone. I find myself stuck trying to find the VBA way to get Access to create a PDF of the currently-selected (and open) object (Form or Report). I know it can be done by selecting :...
3
NeoPa
by: NeoPa | last post by:
Introduction For this article I'll be using a very simple database which has Form (clsForm) & Report (clsReport) classes that simply handle making the calling Form invisible until the Form, or all...
3
by: nia12 | last post by:
Hi there, I am very new to Access so apologies if any of this is obvious/not clear. I am creating a data collection tool for health care employees to complete. It consists of a number of...
0
isladogs
by: isladogs | last post by:
The next online meeting of the Access Europe User Group will be on Wednesday 6 Dec 2023 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, Mike...
2
by: GKJR | last post by:
Does anyone have a recommendation to build a standalone application to replace an Access database? I have my bookkeeping software I developed in Access that I would like to make available to other...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.