ning,
how did u resolve the problem?
did u make new referrences?
can i see ya code?
cheers
Siva.
Ning Lin wrote:
>
> Thanks for your help! It has resolved my problem now.
>
> Ning
>
> On 2/3/07, Mike Dimmick <[EMAIL PROTECTED]> wrote:
>>
>> Just a nitpicking correction: .wixlib files _
If your love warrior is too small, you may lose this war!
http://xeaei.sideeventsonline.com
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
htt
Thanks. In fact, the "Property" does work, Things are like the following:
if i want to the following sequence: myDlg->VerifyReadyDlg, the following
things work:
but i don't know why i can't make the back button of VerifyReadyDlg run through
the same method.> Date: Thu, 27 Mar 200
Hello Mark
Did you figure out the usage for $(var.Platform)? I need to know the
platform on which the wxs was compiled and then use that in the Wix file
itself.
Thanks,
Sameeksha
Justin Rockwood wrote:
>
> There's a complete list in wix.chm. Here's the list again if you need it:
>
>
>
>
>
Hello
I need to set the 'Platforms' attribute on the 'Package' element to be x64
or otherwise depending on the arguments supplied while building the wxs. Is
there an in-built variable in Wix that will help me determine that? Builds
are generated for both the x86 and x64 platforms by Buildtracker
Any update on this?
Thanks,
Jacob
On Sun, Mar 23, 2008 at 8:44 PM, Sajo Jacob <[EMAIL PROTECTED]> wrote:
> are you testing by running from an elevated command prompt? I believe
> this will cause impersonated actions to be elevated.
> No, Running uninstallation from an elevated command prompt is
> From: Anidil
> Sent: Thursday, March 27, 2008 10:19 AM
>
> It works fine during repair when i change the condition to
> "Installed".But it doesn't launch automatically after the
> installation unless i make it "NOT Installed" , in that
> case repair doesn't work :(...strange..
What's strange?
Hi,
I've created a localizable string variable(SQLSrvName), linked it to a
property(SQLServerName) of an edit of a dialog.
the variables receive the values, BUT, the Server = "!(loc.SQLSrvName) " do not
repass the value to the connection string.
log line:
MSI (s) (B0!40) [15:18:28:388]: PROPERT
To answer my own question:
NO -- the CLR loaded will be 32-bit and all "downstream" calls into .NET
custom actions will run as 32-bit and be victims of registry redirection.
Sanin wrote:
>
> Bob, thanks for your reply.
>
> To make sure let me summarize:
>
> Although my CLR loader, which is a
My permanent component didn't work just right the first time, so I need
to try it again. If there's really no way to uninstall a permanent
component for debugging, then is there a way to force a permanent
component to be re-installed?
Thanks,
Robert Skinner
Senior Software Developer
The Bentley S
Hi all,
If I want to uninstall my product over Add/Remove programs it does not
work
Here are some code snippets:
Snippet 1:
Snippet 2:
Can anybody say what is missing?
Best regards
Not sure if you'll hit a problem if each MSI if for a different client & they
are unlikely to install each others MSI.
That said, an error could occur & a component for client X is built into an MSI
for client Y - client Y installing that MSI might have an issue.
Sorry I can't give a straight ans
Oi,
Hohe hoholulu
Two hundred and eightythree acadians remained to it again.
thus it was that mrs. Brownlow flattered time. But these
inquests and coroners, they always ken 'at ye wad hae ony
but yer ain fowk! I hae abilities and industry, and you
will be a welllooking after half t
When people require files removed I've marked them as transitive components
with a condition that evaluates false. As you know, removing components during
a minor update is not supported.
Phil Wilson
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob
But that's irrelevant. You're looking for UpgradeCodes of other installed
products, and that's got nothing to do with new ProductCodes you want to assign
to your setups.
Phil Wilson
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of dmcweeney
Sent: Thursd
I'm maintaining a handful of MSI packages created with WiX 2.0.4820.0.
These packages are essentially variants of a single package that are
customised for specific clients.
My concern is that the GUID for any given component in the various
packages is the same. The files associated with the co
You can't the ScrollableText control does not publish any event to get
known to this. You will have to use an external UI or hook into the
installer UI somehow...
Best regards,
Sebastian Brand
Instyler Software - http://www.instyler.com
On Mar 12, 2008, at 17:17 , Arthur Curvello wrote:
>
Georgi Shopov wrote:
> Can anybody tell me what is the preferred way to remove files during minor
> upgrades?
>
The need to remove files is a sign that you should consider using a
major upgrade. It's possible to remove files but you've discovered the
drawback. You need to add RemoveFile tabl
Sanin wrote:
> Although my CLR loader, which is actually a C++ custom action for WiX, is
> 32-bit IT WILL be able to load the 64-bit CLR into the installer process and
> kick off .NET custom actions, which in turn may write files and registry
> keys without redirection, right?
>
Sorry, I don't
Alperstein, Kenny wrote:
This is hard to explain, but it seems as if WIX, stored the
publisherpolicy.config files in a structure it created that was
relative to the directory where I created the msi. When installing
the package, WIX then looked for the publisherpolicy.config, in the
same st
Benas wrote:
> After license agreement dialog i got an error box which says: "Please
> wait while installer finishes determining your disk space
> requirements." How to rid of that error?
Add a feature and component.
--
sig://boB
http://joyofsetup.com/
--
Christopher Butcher wrote:
The service does uninstall, the files are deleted by the MSI ok. It's
just that whatever registry entries which enable the service to appear
in SERVICES.MSC are left in place. If I delete them manually and then
reboot then the service is removed from SERVICES.MSC. B
Kiran Subhedar (Sogeti) wrote:
But somehow this is not working for me. The command simply fails and
InstallFinalize returns a value of '3'.
Check a verbose log. WiX custom actions log fairly detailed error
information.
--
sig://boB
http://joyofsetup.com/
Markus Kuehni wrote:
> So MSI just switches them off in maintenance mode. I can understand this
> logic. But then why not do the same in install mode?
>
What do you mean by "switches them off"? Are they not visible in a
feature selection tree? What are the feature conditions?
--
sig://boB
dmcweeney wrote:
> I could use the upgrade mechanism alright and that would work, however I want
> to assign neww product codes to the various kits, thus the reason for
> asking.
>
You can search for multiple, arbitrary upgrade codes. They don't have to
match the upgrade code of the package be
How about just "1" as Condition to have the CA executed always?
Best regards,
Sebastian Brand
Instyler Software - http://www.instyler.com
On Mar 27, 2008, at 11:18 , Anidil wrote:
>
> It works fine during repair when i change the condition to
> "Installed".But it
> doesn't launch automaticall
Xu nanxuan wrote:
>
>
> For example, I need the following sequence: WelcomeDlg --> VerifyReadyDlg.
> But i've no idea how to realize the Back button in the latter dlg so that
> i can move back from VerifyReadyDlg during installation. I've tried the
> following methods but none work:
>
>
>
I could use the upgrade mechanism alright and that would work, however I want
to assign neww product codes to the various kits, thus the reason for
asking.
Sound
Donal
--
View this message in context:
http://www.nabble.com/product-search-using-product-code--tp16306215p16324309.html
Sent from t
Hi Alex,
Thanks for the quick response.
My guess is I would have to write a dll to implement this custom action? ;-(
It was installed per machine. The problem I am trying to get around is that
the 4 kits - 2 x x86 and 2 x x64 share the same product code! (I know I
know, I inherited it) and that
It works fine during repair when i change the condition to "Installed".But it
doesn't launch automatically after the installation unless i make it "NOT
Installed" , in that case repair doesn't work :(...strange..
Here is a snip of my code
...
..
Installed
Installed
Instal
Kill your pain! http://saczi.superwildside.com
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038
For example, I need the following sequence: WelcomeDlg --> VerifyReadyDlg. But
i've no idea how to realize the Back button in the latter dlg so that i can
move back from VerifyReadyDlg during installation. I've tried the following
methods but none work:
Fact is i can click the Back btn i
32 matches
Mail list logo
