[WiX-users] Auto deletion of reg values written by MSI
Hi, Is there a way I can ask the MSI not to delete the registry values it has written to the MSI during uninstallation? I'm looking at the RegistryKey's Action options. create or createAndRemoveOnUninstall both delete the values that are written by RegistryValue element. I need to preserve those registry keys after the uninstallation also. Is there such an option? Thanks, Pratapa. -- Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Can msi external ui write to the MSI properties?
Got it. My assumption was that I can use the UI in callback in place of customized UI in installUISequence for providing user choices to the msi. That seems to be a wrong assumption. Thanks for all the help! :) On Thu, Sep 16, 2010 at 10:32 AM, Wilson, Phil wrote: > You don't collect external data during the callback - that's not what it's > for. It makes no sense to use the external callback to set the list of > features to install, as one example. I think you have some assumption about > how this is working that I'm not aware of. In my case I have a .NET program, > Windows Forms. It shows UI, a feature tree, asks the user various questions, > and all of this is before the install starts and nothing to do with the > callback. When it starts the actual MSI part of install, it does things like > MsiEnableLog, calls MsiSetExternalUIRecordallback, then calls > MsiInstallProduct, the callback supplying feedback to the progress form. I > suspect that you're thinking of external UI only in terms of the callback > function, but that's merely a monitoring scheme for the actual install > process. In fact "monitor" is the word used in the MSDN docs. It's not a > replacement for UI actions like collecting features and showing EULAs, it's > only to monitor the execute sequence of the install when you install the MSI > silently, suppressing any built-in MSI UI. > > Phil Wilson > > > > -Original Message- > From: Pratapa Reddy Sanaga [mailto:pratap.san...@gmail.com] > Sent: Thursday, September 16, 2010 10:16 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Can msi external ui write to the MSI properties? > > Phil, > > I'm not able to understand how you are able to collect user input from > external UI of an MSI and pass it as command line argument for the same > MSI. > The external UI wouldn't show up until the MSI starts executing, so once > the > MSI starts executing, the bootstrapper exe can't provide any more command > line arguments to the already running MSI right? Or, are you talking about > having 2 MSIs, one MSI whose related external UI would collect the > requirements and then the bootstrapper would collect these requirements and > launch the second product MSI with these command line arguments? > > The control flow I have is(with just one msi that will be launched by the > exe) > > 1. Exe sets my callback function as external UI by calling > MsiSetExternalUI. > 2. Exe launches the Msi with some command line args using > MsiInstallProduct. > 3. Exe waits for the MsiInstallProduct call to return. > > In a separate process, > > 1. Msi launches and calls into my callback function. > 2. I show the UI and collect all of the user requirements and return from > external UI. I don't want to fully suppress internal UI, so once I return > from external UI, internal UI will take care of progress messages, > notifications etc. > 3. The collected user requirements are in the context of the external > UI(which can't do MsiSetProperty because of the handler limitation, only > one > msi can be open at a time) and they can also be referenced in the context > of > the exe that launched the MSI. But the exe has already launched this MSI, > so > there is no way the exe can let this MSI know about the user input through > command line args. > > So in order to achieve the results you mentioned(collecting feature list > and > other input from the user and pass it on as command line args), there > should > be atleast 2 MSIs. > > 1. Exe sets your external UI callback func as external UI by calling > MsiSetExternalUI. > 2. Exe launches the MSI that would do nothing more than showing the > external > UI. > 3. Through pvContext variable, the external UI can collect the user input > and the Exe would have an idea about. > 4. Exe creates command line args after this MSI is done installing and > launches the real product MSI with these command line args. (pure guess > work > :)) > > I must have surely misunderstood a big piece as I'm not able to imagine the > external UI to be not able to communicate the user input to its host MSI. > On Thu, Sep 16, 2010 at 9:28 AM, Wilson, Phil >wrote: > > > Without knowing exactly why you think there are "problems with writing > back > > properties to the MSI" I can't really comment too much. What requirement > do > > you think this addresses? I have used an external UI a lot, your 2, and > it > > works fine. Typically you want to show splash screens, a dialog to accept > a > > EULA, then collect a list of features and other properties. Then you > in
Re: [WiX-users] Can msi external ui write to the MSI properties?
Phil, I'm not able to understand how you are able to collect user input from external UI of an MSI and pass it as command line argument for the same MSI. The external UI wouldn't show up until the MSI starts executing, so once the MSI starts executing, the bootstrapper exe can't provide any more command line arguments to the already running MSI right? Or, are you talking about having 2 MSIs, one MSI whose related external UI would collect the requirements and then the bootstrapper would collect these requirements and launch the second product MSI with these command line arguments? The control flow I have is(with just one msi that will be launched by the exe) 1. Exe sets my callback function as external UI by calling MsiSetExternalUI. 2. Exe launches the Msi with some command line args using MsiInstallProduct. 3. Exe waits for the MsiInstallProduct call to return. In a separate process, 1. Msi launches and calls into my callback function. 2. I show the UI and collect all of the user requirements and return from external UI. I don't want to fully suppress internal UI, so once I return from external UI, internal UI will take care of progress messages, notifications etc. 3. The collected user requirements are in the context of the external UI(which can't do MsiSetProperty because of the handler limitation, only one msi can be open at a time) and they can also be referenced in the context of the exe that launched the MSI. But the exe has already launched this MSI, so there is no way the exe can let this MSI know about the user input through command line args. So in order to achieve the results you mentioned(collecting feature list and other input from the user and pass it on as command line args), there should be atleast 2 MSIs. 1. Exe sets your external UI callback func as external UI by calling MsiSetExternalUI. 2. Exe launches the MSI that would do nothing more than showing the external UI. 3. Through pvContext variable, the external UI can collect the user input and the Exe would have an idea about. 4. Exe creates command line args after this MSI is done installing and launches the real product MSI with these command line args. (pure guess work :)) I must have surely misunderstood a big piece as I'm not able to imagine the external UI to be not able to communicate the user input to its host MSI. On Thu, Sep 16, 2010 at 9:28 AM, Wilson, Phil wrote: > Without knowing exactly why you think there are "problems with writing back > properties to the MSI" I can't really comment too much. What requirement do > you think this addresses? I have used an external UI a lot, your 2, and it > works fine. Typically you want to show splash screens, a dialog to accept a > EULA, then collect a list of features and other properties. Then you install > one or more MSI files "silently" as a single transaction, getting progress > and action messages from the callback and showing them in a progress-type of > dialog, handling FilesInUse in your callback by showing a dialog etc. You > set the feature list using ADDLOCAL on the command line when you install the > MSI file(s), and any other properties you have collected in the UI. Your own > silent install of the multiple MSI files means that you suppress all your > UI, and collect things like a feature list and properties to be set from a > response file that your program reads and passes to the MSI command line. > > Phil Wilson > > > -Original Message- > From: Pratapa Reddy Sanaga [mailto:pratap.san...@gmail.com] > Sent: Wednesday, September 15, 2010 5:48 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Can msi external ui write to the MSI properties? > > I'm just making sure I verify all possibilities to show a UI and capture my > design decision in the doc... > > 1. UI in the bootstrapper exe itself - I'm currently thinking this is the > most feasible solution. > 2. UI as msi external UI - As we discussed, problems with writing back > properties to the MSI. > 3. UI in msi embedded UI - I need to compatible with Windows Installer 3.1, > so this is not an option for me. > 4. UI in UI Sequence - My UI should host a WebBrowser control, so the MSI > dialogs are not an option for me. > 5. UI in immediate custom action in InstallExecute sequence - This is > probably another option available to me apart from option 1. The UI > launches > as logged in user, I'll be able to write back to the msi. But I'm not sure > if I should be doing the UI work in this place because the custom action, > eventhough running as logged in user, is running with Integrity Level High > and Elevation Type Full(applicable on Vista+). Since the UI is going to > navigate to a website, this is not secure. Once the process is elevated, > there is no way
Re: [WiX-users] Can msi external ui write to the MSI properties?
I'm just making sure I verify all possibilities to show a UI and capture my
design decision in the doc...
1. UI in the bootstrapper exe itself - I'm currently thinking this is the
most feasible solution.
2. UI as msi external UI - As we discussed, problems with writing back
properties to the MSI.
3. UI in msi embedded UI - I need to compatible with Windows Installer 3.1,
so this is not an option for me.
4. UI in UI Sequence - My UI should host a WebBrowser control, so the MSI
dialogs are not an option for me.
5. UI in immediate custom action in InstallExecute sequence - This is
probably another option available to me apart from option 1. The UI launches
as logged in user, I'll be able to write back to the msi. But I'm not sure
if I should be doing the UI work in this place because the custom action,
eventhough running as logged in user, is running with Integrity Level High
and Elevation Type Full(applicable on Vista+). Since the UI is going to
navigate to a website, this is not secure. Once the process is elevated,
there is no way to go back to non-elevated mode.
6. UI in deferred custom action - The new process that my UI launches is
launching as LocalSystem and I'm not able to launch it as logged in user. So
the security issue is pulling me back from going with this approach.
So what you suggested above(collect data in your own UI and set the
properties on command line) is my option 1. Please correct me if any of my
above statements are wrong.
Thanks,
Pratap.
On Wed, Sep 15, 2010 at 5:08 PM, Wilson, Phil wrote:
> That's correct, it will have started, but if you're following a model where
> you collect data in your own UI and start the install you have an
> opportunity to set the properties on the install command line. I don't see
> why you would try to set properties from your callback - it seems
> non-deterministic to me. Also you can't really show a UI there and expect to
> support a silent install.
>
> Phil Wilson
>
>
> -Original Message-
> From: Pratapa Reddy Sanaga [mailto:pratap.san...@gmail.com]
> Sent: Wednesday, September 15, 2010 4:28 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Can msi external ui write to the MSI properties?
>
> The install would have already started if my external UI is being executed
> right? i.e. the callback would occur only after I call the InstallProduct
> API from my bootstrapper exe, so I don't have any more chance of passing in
> a command line argument I guess.
>
> I'll try using the context to set the property and get back on this
> thread..
>
> Thanks!
> On Wed, Sep 15, 2010 at 4:15 PM, Wilson, Phil >wrote:
>
> > If you haven't started the install yet, you could pass those properties
> on
> > the command line. Alternatively, the first parameter in the UIHandler
> > callback ("context") is (can be cast to) the MSIHANDLE for the install.
> The
> > example callback in MSDN casts it to an MSIHANDLE when it calls
> > MsiFormatRecord(). I've never tried an MsiSetProperty() on it though.
> >
> >
> > Phil Wilson
> >
> > -Original Message-
> > From: Pratapa Reddy Sanaga [mailto:pratap.san...@gmail.com]
> > Sent: Wednesday, September 15, 2010 3:53 PM
> > To: General discussion for Windows Installer XML toolset.
> > Subject: [WiX-users] Can msi external ui write to the MSI properties?
> >
> > Hi,
> >
> > I'm trying to see if I can use msi external ui for my project. Will I be
> > able to get an input from the user using msi external ui and then store
> > that, lets say string, input from the user into one of the msi
> properties?
> > I
> > feel it can't be done because the external ui would probably be running
> in
> > a
> > separate process and it wouldn't have any handle to the currently running
> > msi to set the property. Please assert my understanding.
> >
> > Thanks,
> > Pratap.
> >
> > --
> > Vote for loksatta = vote for a better future
> >
> >
> --
> > Start uncovering the many advantages of virtual appliances
> > and start using them to simplify application deployment and
> > accelerate your shift to cloud computing.
> > http://p.sf.net/sfu/novell-sfdev2dev
> > ___
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
> >
> > *** Confidentiality Notice: This e-mail, including any associated or
> > attached files, is intended solely for the individual o
Re: [WiX-users] Can msi external ui write to the MSI properties?
By calling MsiOpenPackage or MsiOpenDatabase, I'm getting error 1618 when I
call MsiInstallProduct. The example in MSDN gets around this issue by
calling MsiDoAction(hProduct, "") which will execute the default "Install"
action. I will not be able to take that route because I need to pass command
line arguments to the msi for localization. So looks like the external ui is
kind of read only interface, not good for getting user input? But I see so
many custom UIs(Office, Skype installation etc) that take user input. They
must be writing back the user preferences to the msi somehow..
On Wed, Sep 15, 2010 at 4:28 PM, Pratapa Reddy Sanaga <
pratap.san...@gmail.com> wrote:
> The install would have already started if my external UI is being executed
> right? i.e. the callback would occur only after I call the InstallProduct
> API from my bootstrapper exe, so I don't have any more chance of passing in
> a command line argument I guess.
>
> I'll try using the context to set the property and get back on this
> thread..
>
> Thanks!
> On Wed, Sep 15, 2010 at 4:15 PM, Wilson, Phil
> wrote:
>
>> If you haven't started the install yet, you could pass those properties
>> on the command line. Alternatively, the first parameter in the UIHandler
>> callback ("context") is (can be cast to) the MSIHANDLE for the install. The
>> example callback in MSDN casts it to an MSIHANDLE when it calls
>> MsiFormatRecord(). I've never tried an MsiSetProperty() on it though.
>>
>>
>> Phil Wilson
>>
>> -Original Message-
>> From: Pratapa Reddy Sanaga [mailto:pratap.san...@gmail.com]
>> Sent: Wednesday, September 15, 2010 3:53 PM
>> To: General discussion for Windows Installer XML toolset.
>> Subject: [WiX-users] Can msi external ui write to the MSI properties?
>>
>> Hi,
>>
>> I'm trying to see if I can use msi external ui for my project. Will I be
>> able to get an input from the user using msi external ui and then store
>> that, lets say string, input from the user into one of the msi properties?
>> I
>> feel it can't be done because the external ui would probably be running in
>> a
>> separate process and it wouldn't have any handle to the currently running
>> msi to set the property. Please assert my understanding.
>>
>> Thanks,
>> Pratap.
>>
>> --
>> Vote for loksatta = vote for a better future
>>
>> --
>> Start uncovering the many advantages of virtual appliances
>> and start using them to simplify application deployment and
>> accelerate your shift to cloud computing.
>> http://p.sf.net/sfu/novell-sfdev2dev
>> ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>
>>
>> *** Confidentiality Notice: This e-mail, including any associated or
>> attached files, is intended solely for the individual or entity to which it
>> is addressed. This e-mail is confidential and may well also be legally
>> privileged. If you have received it in error, you are on notice of its
>> status. Please notify the sender immediately by reply e-mail and then delete
>> this message from your system. Please do not copy it or use it for any
>> purposes, or disclose its contents to any other person. This email comes
>> from a division of the Invensys Group, owned by Invensys plc, which is a
>> company registered in England and Wales with its registered office at 3rd
>> Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For
>> a list of European legal entities within the Invensys Group, please go to
>> http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77
>> .
>>
>> You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail
>> recept...@invensys.com. This e-mail and any attachments thereto may be
>> subject to the terms of any agreements between Invensys (and/or its
>> subsidiaries and affiliates) and the recipient (and/or its subsidiaries and
>> affiliates).
>>
>>
>>
>>
>> --
>> Start uncovering the many advantages of virtual appliances
>> and start using them to simplify application deployment and
>> accelerate your shift to cloud computing.
>> http://p.sf.net/sfu/novell-sfdev2dev
>> ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforg
Re: [WiX-users] Can msi external ui write to the MSI properties?
The install would have already started if my external UI is being executed
right? i.e. the callback would occur only after I call the InstallProduct
API from my bootstrapper exe, so I don't have any more chance of passing in
a command line argument I guess.
I'll try using the context to set the property and get back on this thread..
Thanks!
On Wed, Sep 15, 2010 at 4:15 PM, Wilson, Phil wrote:
> If you haven't started the install yet, you could pass those properties on
> the command line. Alternatively, the first parameter in the UIHandler
> callback ("context") is (can be cast to) the MSIHANDLE for the install. The
> example callback in MSDN casts it to an MSIHANDLE when it calls
> MsiFormatRecord(). I've never tried an MsiSetProperty() on it though.
>
>
> Phil Wilson
>
> -Original Message-
> From: Pratapa Reddy Sanaga [mailto:pratap.san...@gmail.com]
> Sent: Wednesday, September 15, 2010 3:53 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] Can msi external ui write to the MSI properties?
>
> Hi,
>
> I'm trying to see if I can use msi external ui for my project. Will I be
> able to get an input from the user using msi external ui and then store
> that, lets say string, input from the user into one of the msi properties?
> I
> feel it can't be done because the external ui would probably be running in
> a
> separate process and it wouldn't have any handle to the currently running
> msi to set the property. Please assert my understanding.
>
> Thanks,
> Pratap.
>
> --
> Vote for loksatta = vote for a better future
>
> --
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
> *** Confidentiality Notice: This e-mail, including any associated or
> attached files, is intended solely for the individual or entity to which it
> is addressed. This e-mail is confidential and may well also be legally
> privileged. If you have received it in error, you are on notice of its
> status. Please notify the sender immediately by reply e-mail and then delete
> this message from your system. Please do not copy it or use it for any
> purposes, or disclose its contents to any other person. This email comes
> from a division of the Invensys Group, owned by Invensys plc, which is a
> company registered in England and Wales with its registered office at 3rd
> Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For
> a list of European legal entities within the Invensys Group, please go to
> http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77
> .
>
> You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail
> recept...@invensys.com. This e-mail and any attachments thereto may be
> subject to the terms of any agreements between Invensys (and/or its
> subsidiaries and affiliates) and the recipient (and/or its subsidiaries and
> affiliates).
>
>
>
>
> --
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
Vote for loksatta = vote for a better future
--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Can msi external ui write to the MSI properties?
Hi, I'm trying to see if I can use msi external ui for my project. Will I be able to get an input from the user using msi external ui and then store that, lets say string, input from the user into one of the msi properties? I feel it can't be done because the external ui would probably be running in a separate process and it wouldn't have any handle to the currently running msi to set the property. Please assert my understanding. Thanks, Pratap. -- Vote for loksatta = vote for a better future -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WebBrowser control in custom UI dialog
I have six options for the UI 1. In the bootstrapper exe - retrieve the token using the UI and pass it on as a command line arg to the msi as a serialized string. 2. Msi External UI - I don't quite understand the difference between this and the first option. Any code samples for external UI would be really helpful to me.. Are there any advantage of using the Msi external UI over having the UI in the bootstrapper exe? 3. Msi embedded UI - not an option for me, as I need my msi to work on xp sp3. 4. Immediate custom action in UI sequence - I need to pass a token that I retrieve from the WebBrowser to a deferred custom action. Since UI sequence runs in launching process, I will have difficulty passing on this token to the deferred custom action. I need to SecureCustomProperties to pass on the token from UI sequence to deferred custom action, which can only be done if it is a managed installation. Please correct me if my understanding is wrong here. 5. Immediate custom action in InstallExecute sequence - The UI stays behind the MSI progress bar, not able to bring the focus on to the WebBrowser window. 6. Deferred custom action - CoCreating a WebBrowser interface is actually launching an iexplore.exe process, but running as 'SYSTEM' which is a security risk. So, I'm trying to figure out if I can tell the InternetExplorer.Application1 COM server to run as logged in user. If I can do this, this would be the best place for me to place the UI. If not, option 1 seems to be the best place for the UI. Could you please see if I'm going in the right direction to solve the problem? Thanks, Pratap. On Mon, Sep 6, 2010 at 8:15 PM, Rob Mensching wrote: > Deferred custom action? What user context is that running under? You might > be surfing the web from an elevated process which seems incredibly > dangerous. > > I've been disappointed by embedded UI (random limitations). At this point, > I've focused on building a really solid external UI. > > On Tue, Aug 31, 2010 at 3:17 PM, Pratapa Reddy Sanaga < > pratap.san...@gmail.com> wrote: > > > Infact, I'm able to put up a WebBrowser control in my deferred custom > > action. So, is there any reason why I should not be using a WebBrowser in > > the deferred custom action itself? > > > > Thanks, > > Pratap. > > > > On Thu, Aug 26, 2010 at 11:08 AM, Pratapa Reddy Sanaga < > > pratap.san...@gmail.com> wrote: > > > > > Figured out that embeddedUI is introduced with Windows Installer 4.5, > but > > I > > > need to be compatible with Windows Installer 3.1. So, embeddedUI is not > > an > > > option for me. > > > > > > I'm now left with two options. > > > > > > 1. In the bootstrapper exe, I can show a window, get the user > > credentials, > > > get the token from the service and pass on the token to the msi in a > > public > > > property. > > > 2. Use an external UI to do the same work. > > > > > > What is the difference between using an external UI(msi related) vs > using > > > an external UI in the exe? Are there any advantages of using the MSI > > > external UI? Can someone please point me to any docs talking about the > > msi > > > external ui? MSDN documentation didn't give me enough info about it... > > > > > > Thanks, > > > Pratap. > > > > > > On Tue, Aug 24, 2010 at 2:47 PM, Pratapa Reddy Sanaga < > > > pratap.san...@gmail.com> wrote: > > > > > >> When is my embedded UI called into during the execution sequence? Is > it > > >> called during InstallUISequence or InstallExecuteSequence? > > >> > > >> > > >> On Fri, Aug 20, 2010 at 1:04 PM, Blair wrote: > > >> > > >>> Only via your own UI (either embedded, external (requires a > > bootstrapper > > >>> where you can place your UI), or in your own bootstrapper before > > starting > > >>> the MSI transaction. > > >>> > > >>> You could use IDCRL from a custom action. > > >>> > > >>> -Original Message- > > >>> From: Pratapa Reddy Sanaga [mailto:pratap.san...@gmail.com] > > >>> Sent: Thursday, August 19, 2010 11:45 AM > > >>> To: General discussion for Windows Installer XML toolset. > > >>> Subject: [WiX-users] WebBrowser control in custom UI dialog > > >>> > > >>> Hi, > > >>> > > >>> I'm trying to solve the following problem. > > >>> > > >>> The MSI will enroll the clie
Re: [WiX-users] WebBrowser control in custom UI dialog
Infact, I'm able to put up a WebBrowser control in my deferred custom action. So, is there any reason why I should not be using a WebBrowser in the deferred custom action itself? Thanks, Pratap. On Thu, Aug 26, 2010 at 11:08 AM, Pratapa Reddy Sanaga < pratap.san...@gmail.com> wrote: > Figured out that embeddedUI is introduced with Windows Installer 4.5, but I > need to be compatible with Windows Installer 3.1. So, embeddedUI is not an > option for me. > > I'm now left with two options. > > 1. In the bootstrapper exe, I can show a window, get the user credentials, > get the token from the service and pass on the token to the msi in a public > property. > 2. Use an external UI to do the same work. > > What is the difference between using an external UI(msi related) vs using > an external UI in the exe? Are there any advantages of using the MSI > external UI? Can someone please point me to any docs talking about the msi > external ui? MSDN documentation didn't give me enough info about it... > > Thanks, > Pratap. > > On Tue, Aug 24, 2010 at 2:47 PM, Pratapa Reddy Sanaga < > pratap.san...@gmail.com> wrote: > >> When is my embedded UI called into during the execution sequence? Is it >> called during InstallUISequence or InstallExecuteSequence? >> >> >> On Fri, Aug 20, 2010 at 1:04 PM, Blair wrote: >> >>> Only via your own UI (either embedded, external (requires a bootstrapper >>> where you can place your UI), or in your own bootstrapper before starting >>> the MSI transaction. >>> >>> You could use IDCRL from a custom action. >>> >>> -Original Message- >>> From: Pratapa Reddy Sanaga [mailto:pratap.san...@gmail.com] >>> Sent: Thursday, August 19, 2010 11:45 AM >>> To: General discussion for Windows Installer XML toolset. >>> Subject: [WiX-users] WebBrowser control in custom UI dialog >>> >>> Hi, >>> >>> I'm trying to solve the following problem. >>> >>> The MSI will enroll the client into my service only if the user >>> provides LiveID credentials and the MSI is able to get a federated token >>> from LiveID service. Currently LiveID does not support using ws-trust >>> endpoint to get a token, so I will have to either use IDCRL or use a >>> WebBrowser control. I am trying to look into the option of using a >>> WebBrowser control. >>> Is it possible to have a WebBrowser control in the custom UI dialog, so >>> that the user can provide his LiveID credentials and the WebBrowser >>> control >>> can talk to the LiveID service to get a token? I myself am not sure if >>> what >>> I'm asking for even makes any sense, but there has to be a starting >>> point... >>> :) >>> >>> Thanks, >>> Pratap. >>> >>> -- >>> Vote for loksatta = vote for a better future >>> >>> >>> -- >>> This SF.net email is sponsored by >>> >>> Make an app they can't live without >>> Enter the BlackBerry Developer Challenge >>> http://p.sf.net/sfu/RIM-dev2dev >>> ___ >>> WiX-users mailing list >>> WiX-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/wix-users >>> >>> >>> >>> -- >>> This SF.net email is sponsored by >>> >>> Make an app they can't live without >>> Enter the BlackBerry Developer Challenge >>> http://p.sf.net/sfu/RIM-dev2dev >>> ___ >>> WiX-users mailing list >>> WiX-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/wix-users >>> >> >> >> >> -- >> Vote for loksatta = vote for a better future >> > > > > -- > Vote for loksatta = vote for a better future > -- Vote for loksatta = vote for a better future -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WebBrowser control in custom UI dialog
Figured out that embeddedUI is introduced with Windows Installer 4.5, but I need to be compatible with Windows Installer 3.1. So, embeddedUI is not an option for me. I'm now left with two options. 1. In the bootstrapper exe, I can show a window, get the user credentials, get the token from the service and pass on the token to the msi in a public property. 2. Use an external UI to do the same work. What is the difference between using an external UI(msi related) vs using an external UI in the exe? Are there any advantages of using the MSI external UI? Can someone please point me to any docs talking about the msi external ui? MSDN documentation didn't give me enough info about it... Thanks, Pratap. On Tue, Aug 24, 2010 at 2:47 PM, Pratapa Reddy Sanaga < pratap.san...@gmail.com> wrote: > When is my embedded UI called into during the execution sequence? Is it > called during InstallUISequence or InstallExecuteSequence? > > > On Fri, Aug 20, 2010 at 1:04 PM, Blair wrote: > >> Only via your own UI (either embedded, external (requires a bootstrapper >> where you can place your UI), or in your own bootstrapper before starting >> the MSI transaction. >> >> You could use IDCRL from a custom action. >> >> -Original Message- >> From: Pratapa Reddy Sanaga [mailto:pratap.san...@gmail.com] >> Sent: Thursday, August 19, 2010 11:45 AM >> To: General discussion for Windows Installer XML toolset. >> Subject: [WiX-users] WebBrowser control in custom UI dialog >> >> Hi, >> >> I'm trying to solve the following problem. >> >> The MSI will enroll the client into my service only if the user >> provides LiveID credentials and the MSI is able to get a federated token >> from LiveID service. Currently LiveID does not support using ws-trust >> endpoint to get a token, so I will have to either use IDCRL or use a >> WebBrowser control. I am trying to look into the option of using a >> WebBrowser control. >> Is it possible to have a WebBrowser control in the custom UI dialog, so >> that the user can provide his LiveID credentials and the WebBrowser >> control >> can talk to the LiveID service to get a token? I myself am not sure if >> what >> I'm asking for even makes any sense, but there has to be a starting >> point... >> :) >> >> Thanks, >> Pratap. >> >> -- >> Vote for loksatta = vote for a better future >> >> >> -- >> This SF.net email is sponsored by >> >> Make an app they can't live without >> Enter the BlackBerry Developer Challenge >> http://p.sf.net/sfu/RIM-dev2dev >> ___ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> >> >> -- >> This SF.net email is sponsored by >> >> Make an app they can't live without >> Enter the BlackBerry Developer Challenge >> http://p.sf.net/sfu/RIM-dev2dev >> ___ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> > > > > -- > Vote for loksatta = vote for a better future > -- Vote for loksatta = vote for a better future -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WebBrowser control in custom UI dialog
When is my embedded UI called into during the execution sequence? Is it called during InstallUISequence or InstallExecuteSequence? On Fri, Aug 20, 2010 at 1:04 PM, Blair wrote: > Only via your own UI (either embedded, external (requires a bootstrapper > where you can place your UI), or in your own bootstrapper before starting > the MSI transaction. > > You could use IDCRL from a custom action. > > -Original Message- > From: Pratapa Reddy Sanaga [mailto:pratap.san...@gmail.com] > Sent: Thursday, August 19, 2010 11:45 AM > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] WebBrowser control in custom UI dialog > > Hi, > > I'm trying to solve the following problem. > > The MSI will enroll the client into my service only if the user > provides LiveID credentials and the MSI is able to get a federated token > from LiveID service. Currently LiveID does not support using ws-trust > endpoint to get a token, so I will have to either use IDCRL or use a > WebBrowser control. I am trying to look into the option of using a > WebBrowser control. > Is it possible to have a WebBrowser control in the custom UI dialog, so > that the user can provide his LiveID credentials and the WebBrowser control > can talk to the LiveID service to get a token? I myself am not sure if what > I'm asking for even makes any sense, but there has to be a starting > point... > :) > > Thanks, > Pratap. > > -- > Vote for loksatta = vote for a better future > > > -- > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > -- > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- Vote for loksatta = vote for a better future -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WebBrowser control in custom UI dialog
Hi, I'm trying to solve the following problem. The MSI will enroll the client into my service only if the user provides LiveID credentials and the MSI is able to get a federated token from LiveID service. Currently LiveID does not support using ws-trust endpoint to get a token, so I will have to either use IDCRL or use a WebBrowser control. I am trying to look into the option of using a WebBrowser control. Is it possible to have a WebBrowser control in the custom UI dialog, so that the user can provide his LiveID credentials and the WebBrowser control can talk to the LiveID service to get a token? I myself am not sure if what I'm asking for even makes any sense, but there has to be a starting point... :) Thanks, Pratap. -- Vote for loksatta = vote for a better future -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How to request live id credentials from the user during installation
Hi, I'm trying to figure out how to request live id credentials from the user during installation. Here is what I'm thinking: 1. Use some custom UI to show a simple message to enter the live id and password with Login and Cancel buttons. This will be executed in InstallUISequence. 2. Save the login and password in two secure public properties. 3. A custom action in InstallExecuteSequence would take these properties and submit them to the live service for authentication. My assumptions for the above process are: 1. Putting up a custom UI to request for credentials should be simple, something similar to this - http://wix.sourceforge.net/manual-wix3/WixUI_customizations.htm 2. Secure public property is the best approach to securing the password unless WIX has something better to offer for saving passwords. 3. It is possible to save data from the UI into some wix properties for login and password. Could someone review this and let me know if I'm missing anything? Thanks, Pratap. -- Vote for loksatta = vote for a better future -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How does network installation work?
Hi, I'm trying to create an MSI that would refer to a resource from the network location during installation. I see an MSDN article about how office does network installation for different SKUs based on a config.xml file. >From the article : http://technet.microsoft.com/en-us/library/cc179214(office.12).aspx How it works The 2007 Office system consists of a number of MSI files. None of the files by itself represents the complete installation. However, you assign the 2007 Office system by assigning only the main product MSI file. The next time the computer starts, this MSI file is accessed and a Windows Installer Custom Action recognizes that Office is deploying with Group Policy. The additional Office MSI and support files are then retrieved from the network installation point and the complete product is installed. My questions: 1. How does the custom action recognize that Office is being deployed with GP? Are there any standard APIs to recognize this or maybe Office just sees that it is being installed in silent mode? 2. How does office MSI(when deployed through GP) know which network location to refer to for the additional files? Thanks, Pratap. -- Vote for loksatta = vote for a better future -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Transforms in Wix 2.0
Thank you very much. This helped me a lot! On Mon, Jun 7, 2010 at 1:20 PM, Blair wrote: > In v2 it was $(loc.StringId). That was changed to !(loc.StringId) in v3 > (IMHO to make it more obvious when the replacement happens [precompile vs. > late-stage linking/binding]). > > V2 users must use MSI-SDK tools for creating transforms. See MSDN for > examples. > > -Original Message----- > From: Pratapa Reddy Sanaga [mailto:pratap.san...@gmail.com] > Sent: Monday, June 07, 2010 12:22 PM > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] Transforms in Wix 2.0 > > Hi, > > Does Wix 2.0 have support for creating transforms? I see that Torch tool > has > been introduced in Wix 3.0. How did Wix 2.0 users create transforms? > > Also, !(loc.StringIdForError) format for custom error message localization > doesn't work when the MSI is created with Wix 2.0 tools. Maybe Wix 2.0 had > some other syntax for string localization? Can someone help me with that? > > We use Wix 2.0 toolset at work and I am trying to figure out if we must > upgrade to Wix 3.0 tools to do that above tasks. > > Thanks, > Pratap. > > -- > Vote for loksatta = vote for a better future > > > -- > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > -- > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- Vote for loksatta = vote for a better future -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix V2.0 sourcecode?
I somehow couldn't find the sources in that folder. Downloaded from this location - http://wix.sourceforge.net/releases/. Hope it would be helpful for others. On Tue, Jun 8, 2010 at 8:41 PM, Rob Mensching wrote: > WiX v2.0 source code is on CodePlex in the wix20 branch. The WiX 2.0 MSI is > at http://wix.codeplex.com/releases/view/44406, Look at the right. > > On Tue, Jun 8, 2010 at 5:30 PM, Pratapa Reddy Sanaga < > pratap.san...@gmail.com> wrote: > > > Hi, > > > > I'm trying to download the source code for Wix V2.0, but I'm getting > > redirected from http://wix.sourceforge.net/downloadv2.html to this link > > for > > V3.0 download - http://wix.codeplex.com/. Can someone give me a pointer > to > > V2.0 pointer? > > > > > > Thanks, > > Pratap. > > > > > > -- > > Vote for loksatta = vote for a better future > > > > > -- > > ThinkGeek and WIRED's GeekDad team up for the Ultimate > > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > > lucky parental unit. See the prize list and enter to win: > > http://p.sf.net/sfu/thinkgeek-promo > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > > -- > virtually, Rob Mensching - http://RobMensching.com LLC > > -- > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- Vote for loksatta = vote for a better future -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Localization - ProductCode property
Certificates are not based on ProductCode. So how do I make sure that my cert is not deleted during a major upgrade, but deleted during an uninstall? Also, my msi's functionality does not change from language to language, like it doesn't install any language specific packs etc... All my MSI does is to install a redist of a component that doesn't care about languages, talk to a webservice and get down a certificate. So, if we are to do a major upgrade, it should be a well planned act by us and we will change the ProductCode for all languages at that time. On Thu, Jun 17, 2010 at 11:08 AM, Blair wrote: > Your certificates are based on ProductCode? There is no reason I can think > of that a Major Upgrade can't retain/reuse files or configuration from a > previous installation. > > -Original Message- > From: Pratapa Reddy Sanaga [mailto:pratap.san...@gmail.com] > Sent: Thursday, June 17, 2010 8:31 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Localization - ProductCode property > > It is kind of complicated in my case. The IT admin would be installing a > package on the machine. During installation, it is going to talk to the > server and take up one slot in the account(receives a cert). The next time > either the IT admin or the local admin runs the package on this machine, it > will see that it has already received a cert from the server and hence make > this execution a NOOP. So, even if the system locale is changed and the > package is run again, I want the package to verify that certificate is > present and, if yes, make the execution a NOOP. I won't be able to have > this > functionality if I have a different ProductCode for each language, because > it will then be considered a major upgrade, right? > > > Looking at the previous year's thread on this - > > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/When-to-change > > -Product-Id-ProductCode-two-editions-of-the-same-product-td3832979.html#a383 > 2979. > I don't have a patching story for my installation package. The admin will > just install it once. There is no repair story or upgrade story to it. The > package would either enroll the client into the service or it fails. If it > succeeds, then future runs of the same package(of any language) should be > NOOP. If it fails, admin will fix the problem on the client machine and run > the package again or get a new package from us and run it. As I said, my > main scenario is that the package should never do a major upgrade, because > it eats up an account slot, unnecessarily, for which the admin paid money. > > So, I'm trying to see if I'm missing anymore scenarios where I would get > into trouble if I use the same productCode for all the languages. > > -Pratap. > > On Wed, Jun 16, 2010 at 6:56 PM, Sascha Beaumont > wrote: > > > Check the archives for more information, I asked a similar question > > sometime last year. I can't find the exact thread, but ended up being > > convinced to make the change. I did however find a list of pointers > > from Rob around localization - changing the PackageCode was important > > enough to be item 0 ;) > > > > > > > 0. *Every* MSI should have a different PackageCode. Even two builds > of > > > the same MSI. > > > > > > Sascha > > > > > > > > On Thu, Jun 17, 2010 at 2:28 AM, Pratapa Reddy Sanaga > > wrote: > > > Hi, > > > > > > I was going through an example for localization and came across this > MSDN > > > page http://msdn.microsoft.com/en-us/library/aa372369. It says that we > > must > > > change the productCode for every localized package. Is this a necessary > > > condition or just a good practice? I'm planning to create MSIs for > > different > > > languages, create transforms with english as base package, embed these > > > transforms into the base package and have a bootstrapper that would > apply > > > the right transform and install the package. So, for this scenario, do > I > > > need to create different ProductCodes for different language MSIs? > > > > > > If I have the same product code for all the language MSIs and tomorrow > if > > I > > > find a localization bug in one language, will there be any implications > > in > > > this servicing process because of the same productCode used in the > first > > > place? > > > > > > Thanks, > > > Pratap. > > > > > > -- > > > Vote for loksatta =
Re: [WiX-users] Localization - ProductCode property
It is kind of complicated in my case. The IT admin would be installing a package on the machine. During installation, it is going to talk to the server and take up one slot in the account(receives a cert). The next time either the IT admin or the local admin runs the package on this machine, it will see that it has already received a cert from the server and hence make this execution a NOOP. So, even if the system locale is changed and the package is run again, I want the package to verify that certificate is present and, if yes, make the execution a NOOP. I won't be able to have this functionality if I have a different ProductCode for each language, because it will then be considered a major upgrade, right? Looking at the previous year's thread on this - http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/When-to-change-Product-Id-ProductCode-two-editions-of-the-same-product-td3832979.html#a3832979. I don't have a patching story for my installation package. The admin will just install it once. There is no repair story or upgrade story to it. The package would either enroll the client into the service or it fails. If it succeeds, then future runs of the same package(of any language) should be NOOP. If it fails, admin will fix the problem on the client machine and run the package again or get a new package from us and run it. As I said, my main scenario is that the package should never do a major upgrade, because it eats up an account slot, unnecessarily, for which the admin paid money. So, I'm trying to see if I'm missing anymore scenarios where I would get into trouble if I use the same productCode for all the languages. -Pratap. On Wed, Jun 16, 2010 at 6:56 PM, Sascha Beaumont wrote: > Check the archives for more information, I asked a similar question > sometime last year. I can't find the exact thread, but ended up being > convinced to make the change. I did however find a list of pointers > from Rob around localization - changing the PackageCode was important > enough to be item 0 ;) > > > > 0. *Every* MSI should have a different PackageCode. Even two builds of > > the same MSI. > > > Sascha > > > > On Thu, Jun 17, 2010 at 2:28 AM, Pratapa Reddy Sanaga > wrote: > > Hi, > > > > I was going through an example for localization and came across this MSDN > > page http://msdn.microsoft.com/en-us/library/aa372369. It says that we > must > > change the productCode for every localized package. Is this a necessary > > condition or just a good practice? I'm planning to create MSIs for > different > > languages, create transforms with english as base package, embed these > > transforms into the base package and have a bootstrapper that would apply > > the right transform and install the package. So, for this scenario, do I > > need to create different ProductCodes for different language MSIs? > > > > If I have the same product code for all the language MSIs and tomorrow if > I > > find a localization bug in one language, will there be any implications > in > > this servicing process because of the same productCode used in the first > > place? > > > > Thanks, > > Pratap. > > > > -- > > Vote for loksatta = vote for a better future > > > -- > > ThinkGeek and WIRED's GeekDad team up for the Ultimate > > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > > lucky parental unit. See the prize list and enter to win: > > http://p.sf.net/sfu/thinkgeek-promo > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > -- > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- Vote for loksatta = vote for a better future -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Localization - ProductCode property
Hi, I was going through an example for localization and came across this MSDN page http://msdn.microsoft.com/en-us/library/aa372369. It says that we must change the productCode for every localized package. Is this a necessary condition or just a good practice? I'm planning to create MSIs for different languages, create transforms with english as base package, embed these transforms into the base package and have a bootstrapper that would apply the right transform and install the package. So, for this scenario, do I need to create different ProductCodes for different language MSIs? If I have the same product code for all the language MSIs and tomorrow if I find a localization bug in one language, will there be any implications in this servicing process because of the same productCode used in the first place? Thanks, Pratap. -- Vote for loksatta = vote for a better future -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Wix V2.0 sourcecode?
Hi, I'm trying to download the source code for Wix V2.0, but I'm getting redirected from http://wix.sourceforge.net/downloadv2.html to this link for V3.0 download - http://wix.codeplex.com/. Can someone give me a pointer to V2.0 pointer? Thanks, Pratap. -- Vote for loksatta = vote for a better future -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] End dialog UI
The issue was that I was using Wix V2 version of light.exe. Could you please provide me a pointer to the syntax for doing the same with Wix v2 version? I'm guessing there should have been some way to do the string localization with V2 too... On Mon, Jun 7, 2010 at 9:56 AM, Blair wrote: > I don't know if it as simple as removing the quotes or not: > > > !(loc.Error_25001) > > > Also, your light.exe commandline looks more like WiX v2 instead of WiX v3. > > -Original Message- > From: Pratapa Reddy Sanaga [mailto:pratap.san...@gmail.com] > Sent: Monday, June 07, 2010 7:57 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] End dialog UI > > I'm hitting some issues with localization. > > I created error 25001 as follows and called MsiProcessMessage from a custom > action: > > > "!(loc.Error_25001)" > > > And created a file named wix_eng.wxl with the following content > > > http://schemas.microsoft.com/wix/2006/localization"; > > > English - Error string > 25001 > > > Linked the wxl using > > light.exe -nologo -v -w1 -wx EP.wixobj wixui.wixlib -loc WixUI_en-us.wxl > -loc ..\Package\wix_eng.wxl -out EP_English.msi > > Now when I run EP_English.msi, I get a message window as expected, but the > error text displayed in it is !(loc.Error_25001) instead of the expected > localized string. I tried following the steps mentioned in this site for > localization, but I'm not sure why it is not working... > http://www.tramontana.co.hu/wix/lesson2.php#2.6. How do I show localized > custom error messages using MsiProcessMessage? > > > Can you please help me with this? > > Thanks, > Pratap. > > On Fri, Jun 4, 2010 at 10:46 AM, Blair wrote: > > > To use your new error 25001 you need to call (something in your custom > > action that will eventually call) MsiProcessMessage passing it the > > INSTALLMESSAGE_ERROR value and a record that includes your error number > as > > described in the page http://msdn.microsoft.com/library/aa371614.aspx. > > > > The custom action itself shouldn't return 25001. It should return the > > documented return values for the type of custom action you created. > > > > -Original Message- > > From: Pratapa Reddy Sanaga [mailto:pratap.san...@gmail.com] > > Sent: Friday, June 04, 2010 10:28 AM > > To: General discussion for Windows Installer XML toolset.; Pratap Sanaga > > Subject: Re: [WiX-users] End dialog UI > > > > Thanks Nick! > > > > I want to end the installation(in case of failure) with a custom message > > like "Installation failed with 0x80240437. Please check that your system > > clock is showing the correct time and retry installation again." > > > > I created a localizable error table with error code 25001 for the above > > message. I'm not able to figure out how to link this custom error 25001 > to > > the MSI UI so that the message pops up on the UI. > > > > This link http://msdn.microsoft.com/en-us/library/aa368554(VS.85).aspx, > > talks about 25000 to 3 error codes for authors of custom actions. So, > > if > > I return a specific 25001 error from my custom action that fails the > > installation, what more should I do for the corresponding message to show > > up > > in the UI? > > > > Thanks, > > Pratap. > > > > On Fri, May 21, 2010 at 2:47 PM, Nick Ramirez > > wrote: > > > > > > > > You could get the WixUI_Minimal.wxs file from the WiX source code, save > > it > > > to > > > your project under a different name, like "CustomWixUI_Minimal.wxs". > Open > > > it > > > up and change the UI element's Id to "CustomWixUI_Minimal". > > > > > > > > > > > > Add a UIRef element to your main .wxs file with an Id that matches. > > > > > > > > > > > > Going back to CustomWixUI_Minimal.wxs, comment out the Welcome dialog. > > > > > > > > > > > > That should just leave you with the dialogs that show the progress bar, > > the > > > message at the end and handle any errors. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > psanaga wrote: > > > > > > > > I'm trying to find out which UI library would be most suitable for my
[WiX-users] Transforms in Wix 2.0
Hi, Does Wix 2.0 have support for creating transforms? I see that Torch tool has been introduced in Wix 3.0. How did Wix 2.0 users create transforms? Also, !(loc.StringIdForError) format for custom error message localization doesn't work when the MSI is created with Wix 2.0 tools. Maybe Wix 2.0 had some other syntax for string localization? Can someone help me with that? We use Wix 2.0 toolset at work and I am trying to figure out if we must upgrade to Wix 3.0 tools to do that above tasks. Thanks, Pratap. -- Vote for loksatta = vote for a better future -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] End dialog UI
Please ignore the previous mail about localization issues. I was using light.exe from Wix V2.0, so I was not seeing localized strings. Once I started using Wix 3.0 toolset, I'm able to see the localized texts. Thanks for the help folks! Thanks Blair and Nick! On Mon, Jun 7, 2010 at 7:57 AM, Pratapa Reddy Sanaga < pratap.san...@gmail.com> wrote: > I'm hitting some issues with localization. > > I created error 25001 as follows and called MsiProcessMessage from a custom > action: > > > "!(loc.Error_25001)" > > > And created a file named wix_eng.wxl with the following content > > > http://schemas.microsoft.com/wix/2006/localization"; > > > English - Error string > 25001 > > > Linked the wxl using > > light.exe -nologo -v -w1 -wx EP.wixobj wixui.wixlib -loc WixUI_en-us.wxl > -loc ..\Package\wix_eng.wxl -out EP_English.msi > > Now when I run EP_English.msi, I get a message window as expected, but the > error text displayed in it is !(loc.Error_25001) instead of the expected > localized string. I tried following the steps mentioned in this site for > localization, but I'm not sure why it is not working... > http://www.tramontana.co.hu/wix/lesson2.php#2.6. How do I show localized > custom error messages using MsiProcessMessage? > > > Can you please help me with this? > > Thanks, > Pratap. > > On Fri, Jun 4, 2010 at 10:46 AM, Blair wrote: > >> To use your new error 25001 you need to call (something in your custom >> action that will eventually call) MsiProcessMessage passing it the >> INSTALLMESSAGE_ERROR value and a record that includes your error number as >> described in the page http://msdn.microsoft.com/library/aa371614.aspx. >> >> The custom action itself shouldn't return 25001. It should return the >> documented return values for the type of custom action you created. >> >> -Original Message- >> From: Pratapa Reddy Sanaga [mailto:pratap.san...@gmail.com] >> Sent: Friday, June 04, 2010 10:28 AM >> To: General discussion for Windows Installer XML toolset.; Pratap Sanaga >> Subject: Re: [WiX-users] End dialog UI >> >> Thanks Nick! >> >> I want to end the installation(in case of failure) with a custom message >> like "Installation failed with 0x80240437. Please check that your system >> clock is showing the correct time and retry installation again." >> >> I created a localizable error table with error code 25001 for the above >> message. I'm not able to figure out how to link this custom error 25001 to >> the MSI UI so that the message pops up on the UI. >> >> This link http://msdn.microsoft.com/en-us/library/aa368554(VS.85).aspx, >> talks about 25000 to 3 error codes for authors of custom actions. So, >> if >> I return a specific 25001 error from my custom action that fails the >> installation, what more should I do for the corresponding message to show >> up >> in the UI? >> >> Thanks, >> Pratap. >> >> On Fri, May 21, 2010 at 2:47 PM, Nick Ramirez >> wrote: >> >> > >> > You could get the WixUI_Minimal.wxs file from the WiX source code, save >> it >> > to >> > your project under a different name, like "CustomWixUI_Minimal.wxs". >> Open >> > it >> > up and change the UI element's Id to "CustomWixUI_Minimal". >> > >> > >> > >> > Add a UIRef element to your main .wxs file with an Id that matches. >> > >> > >> > >> > Going back to CustomWixUI_Minimal.wxs, comment out the Welcome dialog. >> > >> > >> > >> > That should just leave you with the dialogs that show the progress bar, >> the >> > message at the end and handle any errors. >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > psanaga wrote: >> > > >> > > I'm trying to find out which UI library would be most suitable for my >> > > project. Currently I use LimitUI property in the wix file and with >> this >> > > property, I don't get an end dialog which informs the user about >> > > success/failure of the installation. I want to add another modal >> dialog >> > > which would inform the user about success or failure and also a help >> text >> > > to >> > > the user in case of a failure. >> > > >> > >
Re: [WiX-users] End dialog UI
I'm hitting some issues with localization. I created error 25001 as follows and called MsiProcessMessage from a custom action: "!(loc.Error_25001)" And created a file named wix_eng.wxl with the following content http://schemas.microsoft.com/wix/2006/localization"; > English - Error string 25001 Linked the wxl using light.exe -nologo -v -w1 -wx EP.wixobj wixui.wixlib -loc WixUI_en-us.wxl -loc ..\Package\wix_eng.wxl -out EP_English.msi Now when I run EP_English.msi, I get a message window as expected, but the error text displayed in it is !(loc.Error_25001) instead of the expected localized string. I tried following the steps mentioned in this site for localization, but I'm not sure why it is not working... http://www.tramontana.co.hu/wix/lesson2.php#2.6. How do I show localized custom error messages using MsiProcessMessage? Can you please help me with this? Thanks, Pratap. On Fri, Jun 4, 2010 at 10:46 AM, Blair wrote: > To use your new error 25001 you need to call (something in your custom > action that will eventually call) MsiProcessMessage passing it the > INSTALLMESSAGE_ERROR value and a record that includes your error number as > described in the page http://msdn.microsoft.com/library/aa371614.aspx. > > The custom action itself shouldn't return 25001. It should return the > documented return values for the type of custom action you created. > > -Original Message- > From: Pratapa Reddy Sanaga [mailto:pratap.san...@gmail.com] > Sent: Friday, June 04, 2010 10:28 AM > To: General discussion for Windows Installer XML toolset.; Pratap Sanaga > Subject: Re: [WiX-users] End dialog UI > > Thanks Nick! > > I want to end the installation(in case of failure) with a custom message > like "Installation failed with 0x80240437. Please check that your system > clock is showing the correct time and retry installation again." > > I created a localizable error table with error code 25001 for the above > message. I'm not able to figure out how to link this custom error 25001 to > the MSI UI so that the message pops up on the UI. > > This link http://msdn.microsoft.com/en-us/library/aa368554(VS.85).aspx, > talks about 25000 to 3 error codes for authors of custom actions. So, > if > I return a specific 25001 error from my custom action that fails the > installation, what more should I do for the corresponding message to show > up > in the UI? > > Thanks, > Pratap. > > On Fri, May 21, 2010 at 2:47 PM, Nick Ramirez > wrote: > > > > > You could get the WixUI_Minimal.wxs file from the WiX source code, save > it > > to > > your project under a different name, like "CustomWixUI_Minimal.wxs". Open > > it > > up and change the UI element's Id to "CustomWixUI_Minimal". > > > > > > > > Add a UIRef element to your main .wxs file with an Id that matches. > > > > > > > > Going back to CustomWixUI_Minimal.wxs, comment out the Welcome dialog. > > > > > > > > That should just leave you with the dialogs that show the progress bar, > the > > message at the end and handle any errors. > > > > > > > > > > > > > > > > > > > > > > > > > > psanaga wrote: > > > > > > I'm trying to find out which UI library would be most suitable for my > > > project. Currently I use LimitUI property in the wix file and with this > > > property, I don't get an end dialog which informs the user about > > > success/failure of the installation. I want to add another modal dialog > > > which would inform the user about success or failure and also a help > text > > > to > > > the user in case of a failure. > > > > > > I tried using WixUI_Minimal dialog library, but it has lot of > unnecessary > > > dialogs that I don't need(start and license screens). I just want a > > simple > > > UI with which the user wouldn't have to interact at all, except for the > > > end > > > dialog. How can I do this? > > > > > > Thanks, > > > Pratap. > > > > > > > > > -- > > > Vote for loksatta = vote for a better future > > > > > > > > -- > > > > > > ___ > > > WiX-users mailing list > > > WiX-users@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > > &
Re: [WiX-users] End dialog UI
Thanks Nick! I want to end the installation(in case of failure) with a custom message like "Installation failed with 0x80240437. Please check that your system clock is showing the correct time and retry installation again." I created a localizable error table with error code 25001 for the above message. I'm not able to figure out how to link this custom error 25001 to the MSI UI so that the message pops up on the UI. This link http://msdn.microsoft.com/en-us/library/aa368554(VS.85).aspx, talks about 25000 to 3 error codes for authors of custom actions. So, if I return a specific 25001 error from my custom action that fails the installation, what more should I do for the corresponding message to show up in the UI? Thanks, Pratap. On Fri, May 21, 2010 at 2:47 PM, Nick Ramirez wrote: > > You could get the WixUI_Minimal.wxs file from the WiX source code, save it > to > your project under a different name, like "CustomWixUI_Minimal.wxs". Open > it > up and change the UI element's Id to "CustomWixUI_Minimal". > > > > Add a UIRef element to your main .wxs file with an Id that matches. > > > > Going back to CustomWixUI_Minimal.wxs, comment out the Welcome dialog. > > > > That should just leave you with the dialogs that show the progress bar, the > message at the end and handle any errors. > > > > > > > > > > > > > psanaga wrote: > > > > I'm trying to find out which UI library would be most suitable for my > > project. Currently I use LimitUI property in the wix file and with this > > property, I don't get an end dialog which informs the user about > > success/failure of the installation. I want to add another modal dialog > > which would inform the user about success or failure and also a help text > > to > > the user in case of a failure. > > > > I tried using WixUI_Minimal dialog library, but it has lot of unnecessary > > dialogs that I don't need(start and license screens). I just want a > simple > > UI with which the user wouldn't have to interact at all, except for the > > end > > dialog. How can I do this? > > > > Thanks, > > Pratap. > > > > > > -- > > Vote for loksatta = vote for a better future > > > -- > > > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/End-dialog-UI-tp5085685p5086435.html > Sent from the wix-users mailing list archive at Nabble.com. > > > -- > > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- Vote for loksatta = vote for a better future -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] End dialog UI
I'm trying to find out which UI library would be most suitable for my project. Currently I use LimitUI property in the wix file and with this property, I don't get an end dialog which informs the user about success/failure of the installation. I want to add another modal dialog which would inform the user about success or failure and also a help text to the user in case of a failure. I tried using WixUI_Minimal dialog library, but it has lot of unnecessary dialogs that I don't need(start and license screens). I just want a simple UI with which the user wouldn't have to interact at all, except for the end dialog. How can I do this? Thanks, Pratap. -- Vote for loksatta = vote for a better future -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Showing progress bar messages using MsiProcessMessage
Hi, Has anyone successfully tried the example shown in this MSDN page? http://msdn.microsoft.com/en-us/library/aa367525(VS.85).aspx I’m trying to use the sample code to show some messages in my MSI, but I just can’t see any text in the progress bar. Can someone please help me with showing progress messages from the custom action? Thanks, Pratapa. -- Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Extracting a certificate from binary table
Hi, I'm placing a .pfx certificate in the binary table and wish to retrieve it in my deferred custom action dll. From what I read on the forum, I see that this can be achieved by reading the certificate using immediate custom action, write it to custom action data(or to a temporary file, which I don't prefer) and then call the deferred custom action that can use this data. Can someone please help me with the following doubts: 1. What APIs should I be looking at, to write to custom action data in an immediate custom action? 2. The certificate is purely binary data and all the APIs return strings. So, I'm afraid that I'd loose some data if there is a NULL in the binary data. How can I handle this situation? 3. I have a URI that should also be placed in the custom action data. So, how can I append the certificate's binary stream to the custom action data(which contains the URI already)? Thanks, Pratapa. -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
