In DetailForm I would like to validate TextBox1 in case when user try to save record. How to prevent save duplication value? I will appreciate for sample.
View Complete Post
In child form I have SvcTextBox. That is editable field and I would like to prevent user to save duplication value. How it to do?
New Laptop running SQL server express 2008 R2. Did a reinstall of SQL after some had uninstalled the first install.
When logging in now I see the server name twice as well as local twice. How can I remove the duplicate names?
I have an XML which has a dynamic number on elements.
I also don't know the names of the elements
I want to verify using an XSD file that for each child node, no element will repeat himself
meaning, the following is illegal.
<a> b </a>
<a> c </a>
what should I write inside the XSD file?
Back in the day when we were mostly submitting forms from one page to another we used to have to validate all post parameters to make sure that the ids somehow belonged to the user that was currently logged in. After all you didn't want a "hacker" to be able to pull someone else's information. In modern ASP.NET application in a situation where a lot of these keys are part of server controls (ex DataKeys of GridView) and is stored in ViewState which is supposedly stamped with a hash that gets validated on every post back, does anyone still validate that the key that was retrieved in fact belongs to the user?I currently do, my business layer methods tend to take an instance of a "profile" object that is maintained in session for each user, the profile contains all basic information including the company etc. that the user is associated with. Having the profile in every business method I can validate that any piece of information requested by the web layer from the business layer does in fact belong to the user requesting it. Another thought is that the library (business layer) can also be reused outside of ASP.NET where perhaps the input would not be as secure. I am wondering if all of this is overkill as all of my basic GetSomething() methods tend to have extra trips to the database to make sure that an ID
I have enabled the FIPS algorithm policy on our windows server2008 machine. Now, any page that has a viewstate is abending with the following error: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.This is used in a web farm so we have a machine key defined in our machine.config. If I add decryption="3DES" to the end of that key everything works again. My guess is the default is AES which isn't FIPS compliant. I also noticed this is not an issue on my iis 6.0 servers running server 2003. Very similar setup.Is there a better way to handle this situation? I read some articles about doing something similar in the app web config. The web.config worked fine. However, the machine.config change seems better because I won't have to change every application.