Hi,
I am testing Setup Factory. I can't find a possibility to create environment variables or to register COM servers (xxx.exe /REGSERVER).
Can someone tip me?
Kind regards,
Jelle van der Linden
Professional Software Development Tools
Hi,
I am testing Setup Factory. I can't find a possibility to create environment variables or to register COM servers (xxx.exe /REGSERVER).
Can someone tip me?
Kind regards,
Jelle van der Linden
You may need to compile and run .bat or .cmd files using
the File.Run with 'command parameters' to achieve what you want.
(if not a batch file..a sequence of file.run actions)
to register Comms:
in a command prompt type: regsvr32.exe /?
to show the possible commands
As for setting environment variables..same thing at command prompt
type SET /?
You may need the "enable file extensions on expansion" call or similar
at or near the beginning of a batch file for this one though,
to give more control and additional commands option.
There have been posts in the AMS5 forums on these two.
However they can be done using SUF7
some one will probably come up with some code for you
..does the file properties function in the build environment allow for
register comms ..does for activex I know that much..
Last edited by SUF6NEWBIE; 10-22-2004 at 11:13 PM.
Hi,
I just saw that there is a Shell.Execute action. I think I will write a very simple VB program, that queries the user about the configuration he wants to activate. From VB, it is simple to create system and users environment variables. Registering a COM .exe can be done with the same method (Shell.Execute). The inconvenience is of cause the break in user dialog; my VB progam will not have the same look and feel as the installetion program.
I "just" need to find out where the user has installed the SW.
This is typically a postinstall action.
Jelle
Yep, sorry I can't help you with this..out of my 'league' !!
where the SW has been installed ..should be able to 'record'
during setup using SessionVar.Expand actions or similar ?
could create a small permanent ini file with your path info in say
the systm's application data folder or write-refer to ini in %TempLaunchFolder%
..again post install actions etc as you said...
Last edited by SUF6NEWBIE; 10-22-2004 at 11:47 PM.