Hi Jim,...
You can of course use the files which are in WDK:
C:\Program Files\Microsoft Platform SDK for Windows Server 2003
R2\Samples\SysMgmt\Msi\database\INTL
These files include already translated texts for common Action and
Error texts.
You can create simple script to create the wxl files fro
There is a topic in the MSI SDK about creating multiple instance MSI files.
It is pretty tricky and a fair bit of work (not much different than
proposed, but transforms are used to minimize the number of MSIs
distributed).
I do *not* recommend using CopyFile to try and solve this problem.
-Or
0. I was not intimately involved with the NGen development
so if I sound like I don't know what I'm talking about, I don't and I'm sorry.
1. Verbose log of the failed uninstall should show much more
detail.
2. Not sure. It looks like install and uninstall use
the same entry poin
Also, note that there is a tool called "WixCop" that
will automagically upgrade your WiX v2 source code to WiX v3 source code.
It handles cases like this. It can save you significant amounts of time.
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mike
Dimmick
Sent:
You mean add a hyperlink to a MSI dialog? If so, then "No,
the Windows Installer does not support hyperlinks." You'd have to go
to an external UI handler and that is a whole lot of work that just isn't worth
it. I'd suggest a button instead.
From: [EMAIL PROTECTED]
[mailto:[EM
All of the issues have (hopefully) been fixed and the new build should be
good to go. You can find it at
http://wix.sourceforge.net/releases/3.0.2120.0/Wix3.msi. Let me know what
you think!
Thanks,
Justin
-
Take Surveys. Ear
Thanks, Mike. As I understand, ARPHELPLINK property can be
used to add product support URL at Add/Remove programs panel. What I intend to
do is to add URL at the setup UI dialog. Any suggestion?
-ning
From: Mike Dimmick
[mailto:[EMAIL PROTECTED]
Sent: Thursday, September 21, 2
I think you need to include difxapp.wixlib in the command line to light.exe. I believe difxapp.wixlib is in the WDK.
If this doesn't work (the DIFxApp documentation on MSDN seems to refer to WiX 2.0) then my next question is around case-sensitivity: the documentation refers to MsiProcessDriver
Awesome! It worked! Thanks! My xml skills
are poor, plus I didn’t realize you could have more than one xmlns*
argument in the Wix element.
-Matt
From: Mike Dimmick
[mailto:[EMAIL PROTECTED]
Sent: Thursday, September 21, 2006
1:51 PM
To: Matthew Janulewicz;
wix-users@list
Use a element to set the ARPHELPLINK property. See http://msdn.microsoft.com/library/default.asp?url=""> for details.
--
Mike Dimmick
From: [EMAIL PROTECTED] on behalf of Ning YangSent: Thu 21/09/2006 21:06To: wix-users@lists.sourceforge.netSubject: [WiX-users] how to add URL info in MSI
I’m still trying to grasp the binding between
properties and dialog controls. I have looked at the SampleWixUIAddDlg sample
and it looks as though the example does not actually capture the user
registration data. Going with that sample, if I had declared properties for user
name, organiza
WebSite appears to have been moved into the http://schemas.microsoft.com/wix/IIsExtension namespace. You'll need to add an xmlns:iis attribute to the Wix element, and reference WebSite as iis:WebSite. I think. I'm not too hot on XML Namespaces, but I think it should look like:
xmlns
Hi,
I’m looking for the way to add URL info in MSI. When
ask user to choose the options also add a hyper-link to provide more
information.
Is there any way to do it?
Thanks a lot.
Ning
-
Take Surv
I sent this to wix-devs and then realized is should probably
go to wix-users.
I get an error LGHT0094 : Unresolved reference to symbol
‘CustomAction:MSIProcessDrivers’ in section
‘Fragment:’. When trying run light on my project. The
command line I’m running is light –ext WixDifxAppExt
I’m a Wix newbie, sorta. About a
month ago. I had some installers for our websites using Wix 2. We are in the
process of moving to VisualStudio 2005 so I thought I’d get a head start
on converting the installers. I’m getting this error in Candle:
C:\localdev\Installation\GetMyGreenIns
I’m using this element in WiX 2.0. For the most
part it’s been fine, but with internal product builds I’ve had a
few users hit a failure with uninstall where ngen returns that the assembly has
already been uninstalled. This causes uninstalls to fail. I
haven’t been able to get repro st
Hi Marcel,
> What about the order when the user customized his "Start
> menu"? (i.e. by disabling the option "Enable dragging and
> Dropping" or by Sorting the menu (which isn't an option if
> you have the previous option disabled...))
I tested this by customizing the start menu. The surprise
Hi Charly,
What about the order when the user customized his "Start menu"? (i.e. by
disabling the option "Enable dragging and Dropping" or by Sorting the menu
(which isn't an option if you have the previous option disabled...))
I could imagine that Windows is only looking for this Reg key when th
Title: Re: [WiX-users] Controls and Events Help
CDATA is an XML-ism which is used to escape the <> which would otherwise be interpreted as an XML element and throw the parser off (since it's an unnamed element which isn't permitted in XML). Basically anything that uses one of XML's reserved toke
Heat is trying to extract self-registration information from the DLLs. To do this, it uses the RegOverridePredefKey API to get a clean version of the HKEY_CURRENT_USER, HKEY_LOCAL_MACHINE keys so that the actual machine environment isn't affected, and to simplify working out what was written. It
You need to debug your CustomAction. For some reason it is
failing. Can't offer much more help without understanding the whole
CustomAction and how it is scheduled.
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Sean Wang
(MSN)
Sent: Wednesday, September 20, 2006 1
Unfortunately, there isn't a list right now. There is actually a bug
assigned to Derek saying he should document them but he "left the building"
before doing so. I guess, we'll just have to piece it all back together
ourselves.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
Excuse me while I remove my shoe and proceed to kick my bottom!!! I was
so focused on WiX syntax that I completely overlooked the XML
requirements.
I apologize for the brain blackout.
__
Doug Watts
Advectis, Inc.
Direct:678.460.4605
Cell:770.314.6704
Doug,
It's an XML encoding thing. You can't have the < or > characters inside
an element (at least not in the way they need to be there) unless you
encode them (use < and >), or put them in a CDATA block.
Regards,
Richard
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTE
I guess part of my problem is understanding the syntax. In your
example, you have the following:
TEST_ENVIRONMENT = "1" OR QA_ENVIRONMENT =
"1" OR PROD_ENVIRONMENT = "1"
AND AND
In one place you test the TEST_ENVIRONMENT property using this syntax:
TEST_ENVIRONMENT = "1"
Elsewhere y
Doug:
See if this helps. I sent it this morning to the list and Deak (Tutorial).
http://sourceforge.net/mailarchive/forum.php?thread_id=30596548&forum_id=39978
David Adams
MSN MessengerID: [EMAIL PROTECTED]
>From: "Douglas Watts" <[EMAIL PROTECTED]>
>To:
>Subject: [WiX-users] Controls and
As a newbie to WiX, I am still trying to understand the
eventing mechanism in dialogs. Basically, I’m trying to understand
how controls use and set properties; and how they consume and expose
events. Can someone provide a very simple explanation of the following?
1.
How
What about version specs in your Wix UpgradeVersionElement? I don't know
how Wix behaves in the absence of them, but there's nothing in your Wix
that targets the versions you want to upgrade.
Phil Wilson
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Je
The standard way to persist that ("the main application directory") is
to use a type 51 custom action and set the ARPINSTALLLOCATION property,
then it will get persisted in the MSI way (meaning that
MsiGetProductInfo with INSTALLPROPERTY_INSTALLLOCATION and other
standard APIs can get it).
Phil W
It knows all your paths because given a ProductCode and a component guid
it can use things like MsiGetComponentPath to find them. "it knows all
your properties" is too general to reply to, but it certainly doesn't
persist the values of properties that you create during your first
install (unless th
Hi Mike,
Heat runs but many of our DLLs in our
product have a manifest in them indicating this dependency. I noticed
that we have at least a dozen DLLs with manifests requiring VC80.CRT"
version="8.0.50608.0 but the pop-up error saying it cannot find
MSVCR80.DLL only comes up 4 times. Ma
As promised, here was the solution to the problem. I am attaching my new
dialog (EnvironmentDlg.wxs) to the email and will reference a subsection of
it to explain what I did.
Background: I wanted to create an installer that would install the same
application across our staged environments (De
Sorry, I was assuming that the problem was that heat.exe
wouldn't run because MSVCR80.DLL was missing, but I see that Heat is a .NET
Framework executable. I have to assume that you're trying to include the Visual
C Runtime in your package. You should ignore this dependency from
Heat.
The s
Hello David,
> I use the element of the to retrieve previous
> user-selected property values on uninstalls. I think you could do the same
> thing for updates.
>
>
> Type="raw"
>Key="SOFTWARE\YourCompany\YourSection\YourKey"
> />
>
>
> In this case, the p
I checked and I do have that policy file
and but I don’t think the redirect is working.
heat still cannot find MSVCR80.DLL.
From: Mike Dimmick
[mailto:[EMAIL PROTECTED]
Sent: Thursday, September 21, 2006
4:51 AM
To: Steven Chin;
wix-users@lists.sourceforge.net
Subject:
Dmitry:
Are you attempting to install the same application to multiple websites
(i.e. each with an individual IP address? Can you give a few more details
on what you are trying to do?
David Adams
MSN MessengerID: [EMAIL PROTECTED]
>From: Dmitry Briliuk <[EMAIL PROTECTED]>
>Reply-To: Dmitr
Mike, thanks for your response.
I intend using the correct component GUIDs for all the files. As far as
I know there are no merge modules for msxml prior to version 3?
I guess my examples were not very sensible.
The examples I gave were just a few obvious ones - there are many many
more.
I am t
Alex:
I use the element of the to retrieve previous
user-selected property values on uninstalls. I think you could do the same
thing for updates.
In this case, the property value is retreived from the registry if found.
If the key is not found in the registry, then the property val
Emma:
What problem are you having specifically?
The bug report deals with a problem in the server custom action dlls.
ConfigureIIS appears to have a buffer overflow on machines with multiple web
sites. I have not heard a status on the bug.
We are currently working around it by crossing binar
Mike,
Thanks for the response.
> -Original Message-
> From: Mike Dimmick [mailto:[EMAIL PROTECTED]
> Sent: Monday, September 18, 2006 5:40 AM
> To: Reggie Burnett; wix-users@lists.sourceforge.net
> Subject: RE: [WiX-users] Component spanning directories
>
> Windows Installer only permits
Cullen
Thanks for the response. That makes some sense and I had not thought about
the patching scenario (since we don't do that).
> -Original Message-
> From: Cullen Waters [mailto:[EMAIL PROTECTED]
> Sent: Friday, September 15, 2006 3:37 PM
> To: Reggie Burnett; wix-users@lists.source
For all the files you mention, you should be using the MSMs. If you
generate your own component GUIDs for these files, you risk breaking
other applications when they are uninstalled. See Rob Mensching's blog
post 'Component Rules 101' for details
(http://blogs.msdn.com/robmen/archive/2003/10/18/564
Could someone offer suggestions as to the best way of dealing with self
registering files that share registry entries.
There are a number of examples of this -
1. Later versions of files with different names (e.g. msxml.dll,
msxml3.dll, etc)
2. Files that use other files (e.g. olepro32.dll uses ole
Salut,
did it this way
and it works quite well.
Thanks,
Stefan
--
View this message in context:
http://www.nabble.com/Installing-extension-for-firefox-tf2305983.html#a6425889
Sent from the wix-users mailing list archive at Nabble.com.
Thanks
It seems my strategy should be:
- place several static checkboxes/selectors for each copy of web app
- make several hard-coded copies of web app, each of them will take it settings
from corresponding check box
- implement custom action, which will read settings for each app to make it
poss
It is required to intall web application multiple times on the same server
(i.e. into different web sites), or make multiple copies during single install.
Each copy should have its own location (at least own Web.Config file) and
perhaps own item in unistall list, preferable each copy to have ow
It's worse than that. Components should always have the same path, so
you really need to generate new GUIDs for all the components for each
instance.
MSDE 2000 duplicates every component that needs to be isolated to an
instance and uses a condition 'InstanceComponentSet.n' where n is 1 to
16 to ch
seems the answer: http://sourceforge.net/mailarchive/message.php?msg_id=36584651
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT
there is a virtual folder, which name is configured from UI:
defaultfoldername
...
...
however, if we change "defaultfoldername" to something else (i.e. to
"newfoldername"), uninstallation does not appl
It is required to intall web application multiple times on the same server
(i.e. into different web sites), or
make multiple copies during single install.
Each copy should have its own location (at least own Web.Config file) and
perhaps own item in unistall list, preferable each copy to have ow
Hello,
is there a way to get/access properties like INSTALLDIR and other custom
properties from a previous installation which i update with an major
upgrade using standard WIX functions?
Thanks
Alex
-
Take Surveys. Earn C
Title: Message Queue Help Needed
The deferred execution stage of Windows Installer - when
the installation script actually runs - runs using the local computer's
LocalSystem security context. This only has the network credentials of the
machine account (in an Active Directory domain) or NULL
Assembly='.net' is for installing to the GAC. Your assembly does not have a
strong name signature and therefore cannot be installed to the GAC.
If you're not planning to put it in the GAC, omit the Assembly attribute. If
you are, make sure you strong-name sign the assembly.
--
Mike Dimmick
--
Do you think the doubled directory separators could have
any significance? The [ProgramFilesFolder] property includes a trailing
directory separator, so you normally use it like
[ProgramFilesFolder][Manufacturer]\[ProductName]
to build a TARGETDIR.
--
Mike Dimmick
From: [EMAIL PROTEC
Yes, it does indeed do this. However, you should have a
publisher policy installed on your machine which redirects to 8.0.50727.42. I
also have one which redirects to 8.0.50727.163. I'm running Windows XP SP2 with
all current patches.
Look in
%SystemRoot%\WinSXS\Policies\x86_policy.8.0.Mic
Changing the product code on its own isn't enough. Take a look here
http://www.tramontana.co.hu/wix/lesson4.php
Rob
Adam Clay wrote:
> I have a question, about changing versions and upgrading,
> in previos versions, i have made a registry key
> "HKEYLOCALMACHINE\...\version 2.0", but now in an
56 matches
Mail list logo
