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.
I’m using a Database Project to create all the tables needed for my .NET MVC application. What I am wondering is, is there a common “best practice” for populating my lookup tables? I’m new to .NET database projects, and I don’t know where to put a script for this, or whether I should even use a script. (I’m thinking I should though.)
You can use the Post-Deployment script to perform actions like this. You can still keep individual scripts for the actions necessary for each table, and “include” them into the Post-Deployment script.
This combined script will then be appended to the deployment script on every deployment.