Problems with copied project
Posted: Wed May 14, 2008 1:54 am
Hi,
first I created an IA Project "3dPreview" which I compiled without web updates.
no to not have to start from scratch, I copied all the files and renamed the project to "2dRelease". I changed all the relevant fields : ProductName, ProductVersionm ProductCode, RevisionCode, ...
The new Project has much more files, is compiled as WebDeploy and supports web updates.
Now on machines, which didn't install 3dPreview, the install for 2dRelease works, but on the machines that have 3dPreview installed, the user gets prompted to locate 3dPreview.msi. Of course he didn't find it, so he uninstalled 3dPreview and tried again.
This time he gets an error message saying : "Runtime error in script ... Line11 trying to access an undefined variable UPDATE_CONFIGURED"
I found the place in the updates script where it tries to access UPDATE_CONFIGURED and I don't see where the variable is defined.
I think define the variable the line before would be too simple...?
But more important, why comes the installer into maintenance mode when installing the second product with different name and product code?
first I created an IA Project "3dPreview" which I compiled without web updates.
no to not have to start from scratch, I copied all the files and renamed the project to "2dRelease". I changed all the relevant fields : ProductName, ProductVersionm ProductCode, RevisionCode, ...
The new Project has much more files, is compiled as WebDeploy and supports web updates.
Now on machines, which didn't install 3dPreview, the install for 2dRelease works, but on the machines that have 3dPreview installed, the user gets prompted to locate 3dPreview.msi. Of course he didn't find it, so he uninstalled 3dPreview and tried again.
This time he gets an error message saying : "Runtime error in script ... Line11 trying to access an undefined variable UPDATE_CONFIGURED"
I found the place in the updates script where it tries to access UPDATE_CONFIGURED and I don't see where the variable is defined.
I think define the variable the line before would be too simple...?
But more important, why comes the installer into maintenance mode when installing the second product with different name and product code?