Altova XMLSpy Professional 2008

Version: 2
Views: 4.4k  |  Created: 07/09/2008

Average Rating: 0
XMLSpy Professional 2008 has 1 inventory records, 2 Questions, 0 Blogs and 0 links. Please help add to this by sharing more!

Deployment Tips (3)

Most Common Setup Type
Not Determined
Average Package Difficulty Rating
Rated 0 / 5 (Not Rated) based on 0 ratings
Most Commonly Reported Deployment Method
Not Determined
or cancel
120
Note
This note is applicable to XMLSpy Professional 2008 rel.2

This comes in an EXE, but it is [obviously] easy to get the MSI from the %TEMP% folder before proceeding with the install.

Once you have the MSI, copy it to a safe location and make another copy of it in the same folder (you'll see why in a minute)

Install the app (from the MSI or the EXE, doesn't matter) and run it.

Upon first run in actually generates the license (.lic) file which is placed nowadays under %AllUsersProfile%\App...Data\Altova\XMLSpy2008.
(which is also correctly pointed here: http://www.appdeploy.com/messageboards/tm.asp?m=35948&mpage=1è±® >Thanks MRaybone

Grab the said .LIC file and copy it to your safe location (network drive etc...)

Open your WfWI and select New/Other Templates/Transform.
Select one of the MSIs (remember - we have two, as above) and go to the 'Files' tab.

Under Windows/Profiles/All Users/Application Data folder (in the bottom left browse box) create a folder named 'Altova' and then one more folder within 'Altova' (not under App...Data again) named 'XMLSpy2008'.

Within the top browse box navigate to your safe location.
Add (from the top right box) the xmlspy.lic file in the newly created folder.

Save your MST and close WfWI.

Basically you're done here, but you have to install [XMLSpy] in the future using TRANSFORMS= etc... etc... and keeping all 3 files together.

Here is how to add more style to your package and also the explanation of why we have two MSIs:

Run ORCA and open ONE of the MSI files.
[Without closing the first ORCA] Run ORCA again and open the OTHER msi. To this second window drag the previously created MST.
(so that's why you needed the 2 MSIs :-)

Obviously you can now see which tables have changed.

Just copy SOME of the changes from the Transformed MSI to the other one, simply using 'Copy Rows' and 'Paste Rows'.

Then simply save this newly changed edited MSI and voila - no need for the MST to be involved in any future deployment, just the .CAB file.

Here are the Tables/Rows which I copied:

- Component: the 'xmlspy.lic' row. Notice the value in the third column 'Directory' - XMLSPYPROFESSIONAL2008COMMONAPPDATA... hmmmm... so XMLSpy had this directory location pre-created... even better - as such we don't need to create any entries in the Directory Table

- Directory - don't copy anything: for the above reasons, as well as the fact that we don't need the Wise generated WWWROOT, RecentFolder and similar entries...

- FeatureComponents - the 'xmlspy.lic' component (within the XMLSpyProfessional Feature near the top

- File - the 'xmlspy.lic' entry at the very bottom

- Media - second row. You can rename the CAB file to something more meaningful than XMLSpyWISETRFM_2.cab, just make sure to put the correct filename in the Column 'Cabinet'

- MsiFileHash - the 'xmlspy.lic' row at the bottom.

- Property Table - just to add more style you can create in there these rows:
REBOOT ReallySuppress
REBOOTPROMPT S
ProductID none
InstallMode Complete

and change these:

AgreeToLicense Yes
ALLUSERS 1
HtmlIsXhtml Yes (this 'ticks' the box 'Treat HTML files as XHTML conformant...' during setup. ONLY change this property if you really need it.

Save the resulting MSI file.

Remember to keep both the MSI and the [your renamed] CAB file together.

Enjoy!
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
120
Note
This note is applicable to XMLSpy Professional 2008 rel.2

This comes in an EXE, but it is [obviously] easy to get the MSI from the %TEMP% folder before proceeding with the install.

Once you have the MSI, copy it to a safe location and make another copy of it in the same folder (you'll see why in a minute)

Install the app (from the MSI or the EXE, doesn't matter) and run it.

Upon first run in actually generates the license (.lic) file which is placed nowadays under %AllUsersProfile%\App...Data\Altova\XMLSpy2008.
(which is also correctly pointed here: http://www.appdeploy.com/messageboards/tm.asp?m=35948&mpage=1è±® >Thanks MRaybone

Grab the said .LIC file and copy it to your safe location (network drive etc...)

Open your WfWI and select New/Other Templates/Transform.
Select one of the MSIs (remember - we have two, as above) and go to the 'Files' tab.

Under Windows/Profiles/All Users/Application Data folder (in the bottom left browse box) create a folder named 'Altova' and then one more folder within 'Altova' (not under App...Data again) named 'XMLSpy2008'.

Within the top browse box navigate to your safe location.
Add (from the top right box) the xmlspy.lic file in the newly created folder.

Save your MST and close WfWI.

Basically you're done here, but you have to install [XMLSpy] in the future using TRANSFORMS= etc... etc... and keeping all 3 files together.

Here is how to add more style to your package and also the explanation of why we have two MSIs:

Run ORCA and open ONE of the MSI files.
[Without closing the first ORCA] Run ORCA again and open the OTHER msi. To this second window drag the previously created MST.
(so that's why you needed the 2 MSIs :-)

Obviously you can now see which tables have changed.

Just copy SOME of the changes from the Transformed MSI to the other one, simply using 'Copy Rows' and 'Paste Rows'.

Then simply save this newly changed edited MSI and voila - no need for the MST to be involved in any future deployment, just the .CAB file.

Here are the Tables/Rows which I copied:

- Component: the 'xmlspy.lic' row. Notice the value in the third column 'Directory' - XMLSPYPROFESSIONAL2008COMMONAPPDATA... hmmmm... so XMLSpy had this directory location pre-created... even better - as such we don't need to create any entries in the Directory Table

- Directory - don't copy anything: for the above reasons, as well as the fact that we don't need the Wise generated WWWROOT, RecentFolder and similar entries...

- FeatureComponents - the 'xmlspy.lic' component (within the XMLSpyProfessional Feature near the top

- File - the 'xmlspy.lic' entry at the very bottom

- Media - second row. You can rename the CAB file to something more meaningful than XMLSpyWISETRFM_2.cab, just make sure to put the correct filename in the Column 'Cabinet'

- MsiFileHash - the 'xmlspy.lic' row at the bottom.

- Property Table - just to add more style you can create in there these rows:
REBOOT ReallySuppress
REBOOTPROMPT S
ProductID none
InstallMode Complete

and change these:

AgreeToLicense Yes
ALLUSERS 1
HtmlIsXhtml Yes (this 'ticks' the box 'Treat HTML files as XHTML conformant...' during setup. ONLY change this property if you really need it.

Save the resulting MSI file.

Remember to keep both the MSI and the [your renamed] CAB file together.

Enjoy!
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
0
Note

The MSI of XMLSpy 2012 can be found under C:\Windows\Downloaded Installations\{GUID}

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment

Inventory Records (1)

View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.

Versions

XMLSpy Professional 2008

Version

2

Questions & Answers (2)

Questions & Answers related to Altova XMLSpy Professional 2008

Blogs (0)

Blog posts related to Altova XMLSpy Professional 2008

Reviews (0)

Reviews related to Altova XMLSpy Professional 2008