Updating a solution (non-seperation model)

Discussion created by madmike6537 on May 14, 2014
Latest reply on Jun 3, 2014 by wsvp

Hello Devs,


I am curious how others are approaching updates to their solution. My solution is set up as a single file solution for simplicity reasons (considering a move to seperation down the road) and I am working with the live data on the server to make updates.


Frankly, I am scared to death that I am going to delete an important record or something worse. I have already had a couple mishaps with a deleted record and one case of an infinite loop (and about 1,000 added records.. oops)!


I could of course make a copy of the database and work on it offline. But then how do I get all their records and information into the new build? Do I somehow import it all?


I guess I am just looking for how others out there provide updates to their software after the initial release without messing up all the data. Maybe the answer is the seperatation model?