02-15-2018 02:33 PM
Is there a way to copy an existing .tsd deployment file to save time from having to reconfigure a new full deployment but reset the version number to 1.0.0? It seems the deployment when copied will only let you start from an incremented state, 1.0.1 for example. If I've released a build and made a quick fix, wanted to rebuild at 1.0.0, is this possible without having to totally reconfigure the deployment from scratch?
Solved! Go to Solution.
02-15-2018 06:35 PM
There's not any way to do this currently. Part of the reason for this is that reverting back to a previous version of an installer can cause installers to have potentially unexpected behavior. See this doc for more specific details:
Upgrade Codes That Affect Installer Behavior
In short, the generated installer would have the same upgrade code by default, but an earlier installer version than the one you've already released.... meaning you can't run the installer without first uninstalling the existing one.
You could get around this by generating a new upgrade code, but unfortunately TSDU still has the limitation of not being able to revert versions.... so the current answer to this is to use version control (SCC, SVN, etc..) to keep the 1.0.0 version of the TSD file, and make sure you use a different upgrade code if you reuse the TSD file for multiple installers.
-Trent