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] 4 4480
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]
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
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]
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 This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
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...
|
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...
|
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...
|
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...
|
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...
|
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,...
|
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...
|
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...
|
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...
|
by: DolphinDB |
last post by:
The formulas of 101 quantitative trading alphas used by WorldQuant were presented in the paper 101 Formulaic Alphas. However, some formulas are complex, leading to challenges in calculation.
Take...
|
by: DolphinDB |
last post by:
Tired of spending countless mintues downsampling your data? Look no further!
In this article, you’ll learn how to efficiently downsample 6.48 billion high-frequency records to 61 million...
|
by: ryjfgjl |
last post by:
ExcelToDatabase: batch import excel into database automatically...
|
by: isladogs |
last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM).
In this month's session, we are pleased to welcome back...
|
by: PapaRatzi |
last post by:
Hello,
I am teaching myself MS Access forms design and Visual Basic. I've created a table to capture a list of Top 30 singles and forms to capture new entries. The final step is a form (unbound)...
|
by: CloudSolutions |
last post by:
Introduction:
For many beginners and individual users, requiring a credit card and email registration may pose a barrier when starting to use cloud servers. However, some cloud server providers now...
|
by: Defcon1945 |
last post by:
I'm trying to learn Python using Pycharm but import shutil doesn't work
|
by: Shællîpôpï 09 |
last post by:
If u are using a keypad phone, how do u turn on JavaScript, to access features like WhatsApp, Facebook, Instagram....
|
by: af34tf |
last post by:
Hi Guys, I have a domain whose name is BytesLimited.com, and I want to sell it. Does anyone know about platforms that allow me to list my domain in auction for free. Thank you
| |