Rules For Expert Prep Development

Rules for Expert Prep Development 1. Query string should be encrypted. 2. Password should be encrypted. 3. Don’t write JavaScript on page level. 4. Use CSS files should be module wise with one comment CSS. 5. Use Pascal case for Naming classes and methods. 6. Use Camel case for variables. 7. Do not use abbreviations. Use name, address, salary etc. instead of nam, addr, and sal. 8. Do not use single character variable names like i, n, x, etc. Use names like index and temp. 9. Do not use underscores (_) in variable names.

Rules for Expert Prep Development 1. 2. 3. 4. 5. 6. 7.

Query string and Filename should be encrypted. Password should be encrypted. Don't write JavaScript on page level. Use CSS files should be module wise with one comment CSS. Use Pascal case for Naming classes and methods. Use Camel case for variables. Do not use abbreviations. Use name, address, salary etc. instead of nam, addr, and sal. 8. Do not use single character variable names like i, n, x, etc. Use names like index and temp. 9. Do not use underscores (_) in variable names. 10. Encrypted the cookies if any 11. Write one insert /Update/Delete in Sp and all selected mode in another sp 12. Query must be optimize (show to TL if any complex) 13. Do not use * if not required in SQL query 14. Do write the function or code on page load event more than 200 lines, break into functions 15. All the setting/email must come from web.config 16. All the external email must be send by single email generic class 17. All the commons function must be available in single general class 18. If using the update panel for larger or time talking data then also use the "update progress" 19. Each page must be tested in with and without data view