June 17, 201015 yr Does anyone have what they feel is a good way to push updates to customers and then import data into their new current file? I'm looking for a non-runtime and non-separation model solution. One of the things that I'm trying to overcome here is to allow the user to have a shortcut to one, seemingly unchanging file. What comes to mind is: - Have the actual solution in a second/related file named by the build number such as 1234.fp7 - Name the file that the user will actually launch using the solutions name (mySolution.fp7) With that as a start, the though is to be able to provide an update using a different filename so the user can maintain a link to one file while having two application files at once allowing the data to be imported from the old to the new using a reasonably smooth interface. If anyone could fill in the blanks or is doing something else, it would be great to learn. Thanks.
Create an account or sign in to comment