Because the ASP.NET 1.x does not support grouping validators, so when you click the button all the validators in the web page will be running. In this case, you might consider implementing your own custom validator.
There are a couple of options here that you might consider:
+ You are still able to use the ASP.NET validators, but depending on which button is clicked you need to disable the validator accordingly (set the enabled property to false. The validators in the web page are basically stored in the Page_Validators array at the client side.
+ You provide your own client side functions like you did in the classic ASP.
+ You can implement your own custom validator that basically only runs when a specific button is clicked. You can do a simple checking in the client side validation function.
+ You can use the ASP.NET validators and store them in the seperate arrays, depending on which button is clicked you can get the validators from an array to run.
The only way there might be a difference depending on the server, is if the security settings in the browser is different for the servers. Still, this is a setting in the browser, and has nothing to do with the server itself.
I am having a typical problem ,I am using management classes to get the path for shared folders and files of the system.The code is working fine for console and winforms,but it is not working for web applications.I have tried giving admin rights to aspnet account,but the problem remains there.Please help
searcher1=new ManagementObjectSearcher("SELECT * FROM Win32_Share");
foreach(ManagementObject share in searcher1.Get())
s=share["Path"].ToString();//for asp.net pages giving null obj ref exception
In a nutshell, the Application_Start event gets fired when the application starts, and the Session_Start event occurs when a new Session is created. In the life of an application, the Application_Start event happens only one time and the Session_Start can be raised multiple times. For more information about this file, you can see Global.asax File[^]
1 - Your maximum connections have been passed programatically, this is not very common.
2 - The more normal reason is that your close connection + dispose is not being called, this leads to the same sort of error.
IMO the best way to handle this is to keep the scope local and ensure correct handling of errors etc guaraantees that your connection is always closed and disposed of when it is no longer needed and then the connections goes out of scope as your function or sub is released to the garbage collector.
Last Visit: 31-Dec-99 18:00 Last Update: 23-Jun-17 9:37