Dealing with Database changes between version branches/rollbacks in ASP.NET

edit removed. check Dealing with Database 开发者_运维问答changes between version branches/rollbacks in ASP.NET

Just off the top of my head, using stored procedures would help with this, as your pages wouldn't need to know the schema. Additionally, you update your stored procedures once, and you don't have any additional changes to make in your code (unless it's an incredibly massive schema change).