/bundles/itninjaweb/img/Breadcrumb_cap_w.png
Hi,
I want to install a xml file under directory c:\Documents and Settings\<Username>\Config
but it getting installed at c:\WINNT\Config. I have created folder structure "Windows\Profiles\Config" in my MSI package, but Profiles folder is getting resolves to location c:\WINNT.
And i want to achive this windows installer package DB without using CustomAction(VB Script,Wise Script)
Please suggest me?
Is it possible
0 Comments   [ - ] Hide Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity

Answers

0
I think you are installing using System Context... so use Active Setup
Answered 02/11/2010 by: mekaywe
Brown Belt

Please log in to comment
0
hi
Answered 02/11/2010 by: shreedhar.ghare
Senior Yellow Belt

Please log in to comment
0
i am not getting your solution about active setup
files getting installed but not at location c:\Documents and Settings\<Username>\Config\confil.xml
package resolves ProfilesFolder ->c:\WINNT and files are getting installed to c:\WINNT\Config\confil.xml
Answered 02/11/2010 by: shreedhar.ghare
Senior Yellow Belt

Please log in to comment
0
If i am correct You are using Wise package studio, use the Set Directory custom action and set ProfileFolder to %USERPROFILE%\Config and place after CostFinalize action
Answered 02/11/2010 by: rakesh.kumar
Senior Yellow Belt

Please log in to comment
0
That's a kludge that will need to be rippled out with every package. If the OP *is* using WPS, it's easier to change the Windows Application template. I snatched a set of 3 Custom Action which appear in most InstallShield-authored MSIs which set properties for The 'All Users' and 'User' profiles and popped them into the template. I think if you search AppDeploy for 'SetAllUsers', you'll turn up a step-by-step walk-through I posted ages ago.

Also, remember that user-level stuff will need to be in a feature which is a child of another feature which has an advertised entry-point, such as a shortcut. This ensures that healing/self-repair takes care of the user-specific install part(s). If your package doesn't have any advertised entry-points, then you need to use Active Setup (AS). For details on AS, use Google.
Answered 02/11/2010 by: VBScab
Red Belt

Please log in to comment