As the title says, should this technique be used only for test purposes or could it be used in programs that will be used by anyone?
Thanks for any suggestion.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
As the title says, should this technique be used only for test purposes or could it be used in programs that will be used by anyone?
Thanks for any suggestion.
It’s good and tested and ready for any kind of testing or deployment or production purposes. Though, I would second the opinion of @Betty of not using the database dropping/recreating functionality. Since a minor glitch in the database might make you lose all your data .
I have used this in my Asp.net project which is currently online for a month or so and it’s working charm. Microsoft has pulled amazing thing and you shouldn’t worry about. It’s a complete project, if anything only advance features will be added and nothing else.