you. For maintaining large directories of non-binary files where additions
and removals are common, this tool works very well for me. I just wish it
generated WiX 3.0 code
Jason Swager
- Original Message
From: Neil Enns <[EMAIL PROTECTED]>
To: General discussion for W
ed for configuration.
But with virtualization becoming more common in the enterprise apps area
(install once into a virtual image, then reconfigure on every new instance) is
making the setup program a bad place for configuration once again.
Jason Swager
- Original Message
From:
does MSI do in this case?
Thanks,
Jason Swager
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/dire
When using Return="check", the executable should return zero for success and non-zero for failure. I don't think there is a way to respond to different returns - if it fails, your install halts. If it succeeds, the install continues. If you need to pass information back from the executable, cons
In this particular customer case - nope, admin credentials couldn't be on the system or in the hands of the restricted user. I suggested that the credential be written to the system in some obscure, highly encrypted fashion during the initial install (which had to be done by an Admin), then used i
installation. A bit of of overkill in this case, but it was a good exercise.Bob Arnson <[EMAIL PROTECTED]> wrote: Jason Swager wrote:> This approach has some drawbacks. First, the possibly extra service > running all the time.Which is a source of potential security holes, especially privilege e
This isn't supported as an MSI feature - but there is a way to do it. There was an article somewhere on the MSDN that described it. And I've seen the same practice used in a number of applications.The solution is to use a NT service. If your application installs a service already, you can piggy-
I believe that this is expected behavior for MSI. Conditional features are evaluated during the CostFinalize standard action, which must be executed BEFORE the UI is displayed. This allows for conditional feature installation based on properties that are setup prior to the UI running - such as OS
not as flexible as some would> like, you can play around with the buttons, backgrounds and bitmaps and> make the typical interface rather different.> > Jason Swager> > Magus <[EMAIL PROTECTED]> wrote: > I have no idea where to even begin in this. I need my installer to ha
One possible solution can be found out at http://www.skincrafter.com/skincrafter_installer.html. It uses the MSI API to hook in an external UI. For some people, this isn't an appropiate solution because the MSI gets wrapped up by a boot-strapping EXE.You could heavily modify the normal installati
I don't believe you can do that. MSI allows only public properties to be set via the command line. And a public property is one that is defined to be all upper case. Check the MSI documentation for more details on private, public, and public secure properties.Jason Swager"dangle123 ..." <[EMAIL
There are external UIs that can "skin" a MSI file. From what I understand, the skinning application/engine builds an EXE that contains the MSI file. The EXE is a boot-strapper of sorts that executes the MSI file, but hooks in its own UI. You can find one at http://www.skincrafter.com/installer.h
12 matches
Mail list logo
