J
Jenny
I've used previous versions of the packaging wizard extensively but the 2003
one seems different. In older versions I created 2 templates - 1 for new
installations with runtime included and 1 for updates with no runtime, and I
could select to always overwrite the version of my software on the customers
machine. The 2003 version does not have this feature, and the older version
of my software on the customer's machine is not being overwritten. From the
reading I've done, it seems 2003 wizard is different, but I can't quite get
my head around it! How does the "upgrade code" on page 5 of the wizard affect
the updating process on the customer's machine -(I do change the minor
version number on page 6 with each release)? And what do I have to do to get
the installation procedure to always overwrite the existing version of my
software on the customer's machine? Thanks - Jenny
one seems different. In older versions I created 2 templates - 1 for new
installations with runtime included and 1 for updates with no runtime, and I
could select to always overwrite the version of my software on the customers
machine. The 2003 version does not have this feature, and the older version
of my software on the customer's machine is not being overwritten. From the
reading I've done, it seems 2003 wizard is different, but I can't quite get
my head around it! How does the "upgrade code" on page 5 of the wizard affect
the updating process on the customer's machine -(I do change the minor
version number on page 6 with each release)? And what do I have to do to get
the installation procedure to always overwrite the existing version of my
software on the customer's machine? Thanks - Jenny