Hello,
I created an MSI and transform for it that uses the AppSearch action. All the
AppSearch related data (AppSearch, DrLocator, RegLocator and Signature tables)
is in the transform. What I wanted to do is find a path in the registry and
than check that a file exists in that path. So it was vita
Hello,
can someone tell me a way to change font styles on WixUI_FeatureTree dialogs
other that re-defining the whole dialog set?
--
Szentpáli János
--
Download Intel® Parallel Studio Eval
Try the new software tools for y
I'm trying to extract COM registration information from an .ocx file. If I run
the
regsvr32 file.ocx
command it registers fine. If I run the
heat.exe file file.ocx -out file.wxs
command I get the following error:
heat.exe : warning HEAT5150 : Could not harvest data from a file that wa
You could use HTA technology (something like XUL, but coming from Microsoft)
to create a custom installer application that has nothing to do with MSI. All
you need to know is a little HTML, a little CSS, alittle DOM and a little
VBScript or JScript. Very flexible and customisable ;).
Though I shou
Don Tasanasanta (Volt) írta:
> Does reference counting rely on the file name? or is it the component GUID?
>
> If I have a product that installs a file and a second product that installs
> the same file do I need the component GUIDS for that file to be the same in
> order for reference counting
Bob Arnson írta:
> Szentpali Janos wrote:
>> Can you suggest some strategy to help one install components that do not
>> come in msi-s or msm-s but that are shared/common components that
>> could/would possibly be installed by non msi setups
>
> If you're not using
Bob Arnson írta:
> Szentpali Janos wrote:
>> Does that mean that the same file, installed by two unrelated setup
>> packages into the same path, with two distinct component and file ids
>> (guids) will still be correctly uninstalled/managed?
>
> No, that's wha
Bob Arnson írta:
> Szentpali Janos wrote:
>> "Merge modules are generally now considered bad practice..." If this
>> is true than what is the point of the whole MSI system? I mean if I
>> have a 3rd party component (x.dll) that 4th party and 5th party are
>>
"Merge modules are generally now considered bad practice..."
If this is true than what is the point of the whole MSI system? I mean if I
have a 3rd party component (x.dll) that 4th party and 5th party are using too,
how does the system decide that the x.dll component installed by the 4th
party'
I should also mention that I only use VBScript to set the INSTALLDIR
property based on something I read from the registry...
--
Szentpáli János
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R
Hi,
I am using VBScript custom actions. I had no problem with antivirus
software so far.
I guess the real issue is the presence of the runtime on older systems
like win95 or winnt 4.0.
If the OS you deploy on is newer than those, I think you can stick with
VBScript custom actions.
János
Just a thought/remark: it sais the SDK, not just framework: "Building
WiX requires .NET Framework 1.1 -->SDK<--"... as far as I know no SDK is
part of most OSes.
János
-
SF.Net email is sponsored by:
Check out the new SourceF
This is what I used (also a child of the product element) in one of my
installs and it did not through any errors:
Of course you have to have the arp.ico in the same folder as the .wxs file.
--
Szentpáli János
-
I don't think the ("TYPE_E_CANTLOADLIBRARY ($80029C4A)") error comes
from the way it is installed. It is more likely a dependency problem:
another COM component that your library is using (maybe a type library
that it implements) might be missing (or is in the path in the context
of the user that r
DEÃK JAHN, Gábor Ãrta:
> On Fri, 07 Dec 2007 14:18:07 +0200, Szentpali Janos wrote:
>
> János,
>
>
>> so important. I noticed that most of you tend to use the improper
>> way of replying to mails: reply is placed on top of the quoted
>> message.
>>
David Reed (MCS - HOUSTON) írta:
>> From: Szentpali Janos
>> Just curious :D Why would anyone want to have the same application
>> installed many times on a single computer?
>>
>
> In a hosted environment where server consolidation is occurring, multiple
David Reed (MCS - HOUSTON) írta:
> Howdy, again, folks. I have been trying to "reuse" a single installer to
> deploy multiple "instances" of the same product to a single machine, and this
> seems to be impossible with a single MSI. The installing user will specify
> the instance name, path, etc,
Dear wix-user list users,
I want to raise your attention to something basic and seemingly not so
important. I noticed that most of you tend to use the improper way of
replying to mails: reply is placed on top of the quoted message. I know
most of you are doing this for as long as you can remember,
Can someone enlighten me regarding the upgrade of merge modules?
Let's say a merge module containing a COM component (.dll file) was
installed. The COM dll defined an interface.
Later a new interface is added to the new component. How can I make a
new merge module, so that no matter in which order
Bryan C. Boettcher írta:
> That works for most of our components, there's still a third party OCX that
> needs to be included. Are MergeModules the way to go?
>
> -Original Message-
> From: Szentpali Janos [mailto:[EMAIL PROTECTED]
> Sent: Monday, December 03, 2007
Bryan C. Boettcher írta:
> I'm packaging shared components in my MSI. These components (like
> COMDLG32.OCX or MSCOMCTL.OCX) are installed into %system32%. However, I've
> got an issue with the files not upgrading properly. I always want to have
> the newest version of the shared component on
Schuett, Michael wrote:
> I converted all my wx* files to utf-16 and saved them as Unicode with the
> same result.
>
> Thanks,
> Mike
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Szentpali Janos
> Sent: Friday, November
Schuett, Michael wrote:
> Hello,
>
> If I use an accented character in a Shortcut Name, the following error
> results...
>
> D:\WiX\ClientInstall\Application.wxs(39,0): Error LGHT0204: ICE03: Invalid
> Filename; Table: Shortcut, Column: Name, Key(s): TrayAppShortcut
>
> Here's the section from Ap
Schuett, Michael wrote:
> Hello,
>
> If I use an accented character in a Shortcut Name, the following error
> results...
>
> D:\WiX\ClientInstall\Application.wxs(39,0): Error LGHT0204: ICE03: Invalid
> Filename; Table: Shortcut, Column: Name, Key(s): TrayAppShortcut
>
> Here's the section from Ap
>
>
>
>
> This snippet can sit immediately beneath your regular "TARGETDIR" element.
> You'll need to reference the component in your feature tree. Hope this
> helps.
>
> On Nov 29, 2007 7:02 PM, Szentpali Janos <[EMAIL PROT
Hi,
I have a setup that contains:
...
...
...
What should i do for the shortdut to be created not in the Programs
Start menu folder, but in a subfolder of it?
I am very new to Wix and the documentation related to the Shortcut
element is empty :D. Thanks in advance.
--
Szentpáli Jáno
remélem valaki ír valami értelmes megoldást erre az annyira
> csak nem bonyolult kérdésre...
>
>
> 2007/11/29, Szentpali Janos <[EMAIL PROTECTED]>:
>
>> János Brezniczky wrote:
>>
>>> Let's assume the file has been successfully replaced by the
János Brezniczky wrote:
> Let's assume the file has been successfully replaced by the new "version".
> Should that new version be later uninstalled together with the package which
> overwritten it?
>
>
> 2007/11/29, Szentpali Janos <[EMAIL PROTECTED]>:
&g
I have an executable x.exe that I need to install over x.exe if it
already exists. I want to replace an existing executable which may or
may not be there. I want to do that overwriting no matter what :D. If it
is there it is not through MSI installation but through manual copying.
How can I do that
John Hall wrote:
>> As I previously said (though in private mail) the solution is rather
>> simple:
>>
>> SelfRegCost='1'
>>
>> Anything else is just a waste of your life by
>> overcomplicating simple things and reinventing the wheel :D
>>
>
> Except that the MSI documentation strongly sugge
John Hall wrote:
>> As I previously said (though in private mail) the solution is rather
>> simple:
>>
>> SelfRegCost='1'
>>
>> Anything else is just a waste of your life by
>> overcomplicating simple things and reinventing the wheel :D
>>
>
> Except that the MSI documentation strongly sugge
As I previously said (though in private mail) the solution is rather
simple:
SelfRegCost='1'
Anything else is just a waste of your life by overcomplicating simple
things and reinventing the wheel :D
János
Andrew Sampson wrote:
> I've had a similar problem - our Wise MSIs were previously using
chandan Koushik wrote:
> Hi All,
> I apologize for posting this if it has been answered several times but I am
> unable to get this working.I am using wixV3 .I just want to call a vbscript
> file which sets permission for user.It takes folder name as argument.
> when i run it from the command line
33 matches
Mail list logo
