This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- XML File Changes: modify only some nodes?
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 06, 2009
03:22 AM
XML File Changes: modify only some nodes?
With IS 2009, InstallScript project, can I modify only some nodes in the XML File Changes and not all the nodes?
I need this because on UPDATEMODE I have to change only some nodes and leave unchanged the others (note that I can't update the other nodes during installation because user can have modified them meanwhile...).
Any suggestion is appreciated!
I need this because on UPDATEMODE I have to change only some nodes and leave unchanged the others (note that I can't update the other nodes during installation because user can have modified them meanwhile...).
Any suggestion is appreciated!
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 06, 2009
02:14 PM
What have you tried so far?
Seems like you should just be able to import the file in the XML File Changes view, then delete the nodes you don't want.
Now, if you're wanting to edit some nodes on first install and some on upgrade...here's how I'd tackle it.
For first install, go ahead and associate that set of changes with whatever component makes the most sense.
For the upgrade, import the file again, same name, but a different component - a dummy one. Set that component to install on condition "Installed" and have it reevaluate the condition everytime.
Haven't tried it myself, but seems like it ought to work. 🙂 Let's hear how it goes!
Seems like you should just be able to import the file in the XML File Changes view, then delete the nodes you don't want.
Now, if you're wanting to edit some nodes on first install and some on upgrade...here's how I'd tackle it.
For first install, go ahead and associate that set of changes with whatever component makes the most sense.
For the upgrade, import the file again, same name, but a different component - a dummy one. Set that component to install on condition "Installed" and have it reevaluate the condition everytime.
Haven't tried it myself, but seems like it ought to work. 🙂 Let's hear how it goes!
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 09, 2009
08:03 AM
Hi Saier!
Thanks for reply!
It is not clear how can I set the component to install on condition "Installed" ...
I use InstallScript ... is this options only available for the other IS setup project? Because I can't find it....
Thanks for reply!
It is not clear how can I set the component to install on condition "Installed" ...
I use InstallScript ... is this options only available for the other IS setup project? Because I can't find it....
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 09, 2009
01:43 PM
Yes, my apologies - I did answer from a Basic MSI perspective even though you very clearly stated it was an InstallScript project.
And - my further apologies - I have no idea how to do anything in InstallScript world and hope that someone else can jump in to help you.
And - my further apologies - I have no idea how to do anything in InstallScript world and hope that someone else can jump in to help you.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 10, 2009
02:05 AM
:eek: Oh my God...!
Sairen, I put all my hopes in you (...) 😉
Apart from the jokes, If someone know how to edit xml files via DOS command I can use this method....
I trust in you...
Sairen, I put all my hopes in you (...) 😉
Apart from the jokes, If someone know how to edit xml files via DOS command I can use this method....
I trust in you...
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)