I have a couple of merge modules that consistently generate these warnings, and
I have not been able to determine how the string is generated that it is
complaining about.
Is this documented anywhere, or can anyone provide some tips as far as how to
correct this?
Here is an example of the
Or dotnetinstaller - http://dotnetinstaller.codeplex.com/
Palbinder Sandher
Software Deployment IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the Virtual Environment**
Integrated Environmental Solutions Limited.
Hi all,
Just did some dialog modifying. When combining WiXUI_FeatureTree.wxs +
WiXUI_InstallDir.wxs I mentioned the property WixUI_Mode which is set
accordingly to the name of the dialog theme. Has this property
Property Id=WixUI_Mode Value=FeatureTree /
some special function except for
Open the corresponding merge module with orca and search for the
string. This should lead to the trouble causing string. But I think
ignoring this warning is the best way than manipulating a 3rd party
merge module.
Regards,
Tobias
2011/2/2 John Bergman john.berg...@xpedienttechnologies.com:
I
No impersonations myself. This started occurring when there was a problem with
my Custom UI which among other things prompted for a password. The UI was not
showing up and so the password was not valid. But the install continued. It got
to ServiceIntall and ServiceControl and the ServiceControl
Hello all,
I am in need to add a Features tree with checkbox selection to my msi. Can
any one point me to some sample as how to achieve this.
Sincere thanks!
--
View this message in context:
Or dotnetinstaller - http://dotnetinstaller.codeplex.com/
I don't want to create a dependency on .net if I don't have to. :/
--
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class
I'm chaining several MSIs and believe it or not, I want to show the UIs of
each package. Is there a way to turn that on/off per package (and
subsequently remove the default burn UI's install location?)?
Not today.
So is there a chance that this feature could be introduced in the future?
Hi,
Every time when I upgrade my software, install location dialog shows the
default install location, It does not picks the previously installed
location automatically. Is there any way to do this other than
storing/searching registry keys. Pointer to a article is also welcome.
Thanks in
Out of curiosity, is there any documentation or tutorials describing how to use
setup.exe/setupbld.exe?
I came up short last time I tried looking for some info on
setup.exe/setupbld.exe.
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax:
Its my merge module.
It looks like the names generated are:
AssemblyReferenceBinaries
AssemblyReferenceSymbols
Etc
To me, this seems like a bug in the way Wix is generating the MSI database, if
the generated names are too long, WiX (IMHO) should change them to fit, and/or
issue a fatal error
A usual way to validate credentials is to use the LogonUser() Win32 API, but
that's a logon that can fail, which is what you don't want. The only other way
I'm aware of is SSPLogonUser(), huge C++ example here:
http://support.microsoft.com/kb/180548
Phil Wilson
-Original Message-
I believe the registry is the only way:
http://robmensching.com/blog/posts/2010/5/2/The-WiX-toolsets-Remember-Pr
operty-pattern
You could set the ARPINSTALLLOCATION
http://robmensching.com/blog/posts/2011/1/14/ARPINSTALLLOCATION-and-how-
to-set-it-with-the-WiX-toolset but I don't know how you
Assuming that I can translate this to C#, what would be the WiX code that needs
to be in place to call this function? I am fairly new to 3.x and I remember
that with 2.0 there needed to be a fair amount of plumbing in place to call a
C# (managed) custom action.
Kevin Burton
Senior Software
There should be simpler method like MigrateFeatures in
UpgradeVersionelement.
On 02-02-2011 12:24, Neil Sleightholm wrote:
I believe the registry is the only way:
http://robmensching.com/blog/posts/2010/5/2/The-WiX-toolsets-Remember-Pr
operty-pattern
You could set the ARPINSTALLLOCATION
Setting ARPINSTALLLOCATION allows retrieval of the location using
MsiGetProductInfo(...INSTALLPROPERTY_INSTALLLOCATION...) so I guess the other
than storing registry keys requirement would be met, but storing/retrieving
the install location from the registry is trivial anyway with built-in MSI
what will be way to do this using WIX ?
I ruled out the registry storing/retrieving method, because there is a
considerable amount of xml needs to be written for it. I would not mind
it if there is some straightaway method of getting older install
location using WIX.
Regards,
Sanjay Rao
On
Feel free to contribute the implementation and documentation.
From: Sanjay Rao [mailto:s...@noida.interrasystems.com]
Sent: Wednesday, February 02, 2011 8:48 PM
There should be simpler method like MigrateFeatures in
UpgradeVersionelement.
On 02-02-2011 12:24, Neil Sleightholm wrote:
Hate to say this, but write it to a registry key and read it back is the only
way I am aware of to do this.
Its not very much XML: You need a component with a registry entry, a property
with a registry search.
Michael
-Original Message-
From: Sanjay Rao
Has no one read :-)
http://robmensching.com/blog/posts/2011/1/14/ARPINSTALLLOCATION-and-how-to-set-it-with-the-WiX-toolset
---
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention? E-Mail Me
Alex Shevchuk has a component search example here..
http://blogs.technet.com/b/alexshev/archive/2008/02/10/from-msi-to-wix-part-3.aspx
Phil Wilson
-Original Message-
From: Sanjay Rao [mailto:s...@noida.interrasystems.com]
Sent: Wednesday, February 02, 2011 1:02 PM
To:
Hello,
I am trying to use Wix to make a installer for the following scenario: my
application has 3 critical components: foo, bar and baz. Foo is created on
demand when a user clicks the download link. Bar and baz remain unchanged
and they both depend on foo. They are also quite large and I want
I have but I don't see how that helps, on upgrade I don't think it
restores your install location - unless I am mistaken.
Neil
-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com]
Sent: 02 February 2011 21:20
To: General discussion for Windows Installer
Hi,
I need to ask again. We need to register Classic ASP in IIS 7 if it is
not registered as ISAP extension. With 3.0 this worked fine, but with
3.5 it will fail the install if there is already something installed.
Via UI I can register the asp.dll as often as I want, no problem. Last
time
Hi,
I would like to join wix user list. This is my email id:
thangananga...@iinterchange.commailto:thangananga...@iinterchange.com
--
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a
25 matches
Mail list logo
