- Original Message -
Subject: Re: [WiX-users] Problems with custom bitmaps with wixUI
> Anthony Wieser wrote:
>> I checked with SPY++, and the bitmap is 493 pixels wide (at least on my
>> Vista system, the way it's set up at the moment).
>>
>
> That's normal for XP too and that's wh
I'm sorry, the exact error message is:
"The Windows Installer service cannot update the system file
c:\WINDOWS\System32\mfc42.dll because the file is protected by Windows. You may
need to update your operating system for this program to work correctly"
When the installation was done with a vb6
Hi,
Is it dangerous to use Heat with wix 2.0 if I only use it for dll
registration?
I don't find a doc of heat. Is there a way to generate wix file only for
selfregister dll with heat (all my files are ine the same folder)
-
Bob Arnson wrote:
> Votive doesn't support WiX v2 but you can install the v2 binaries .zip.
> Or wait for v3 -- it should soon have the COM+ CAs.
>
There's a download for Votive 2.0.4820 available. I've got 2.0.4415 installed.
I don't use the any
of the project stuff, but it is good for the
Stuart A. Malone wrote:
> ICE69: Mismatched component reference. Entry 'DesktopShortcut' of
> the Shortcut table belongs to component 'DesktopShortcut'. However,
> the formatted string in column 'Target' references file
> 'Life_Balance.exe' which belongs to component 'MainApplication'.
I found by myself.
A short cut can contain a target attribute.
So you can put the shortcut in a different component (And not only as child of
file tag) and set a condition on this component.
-Message d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la
Hi,
I'm trying to set up my project to automatically sign my msi files, so I've
added a a post build step that looks like this:
signcode -t
http://timestamp.verisign.com/scripts/timstamp.dll
$(TargetDir)AutoSharesWx.msi
and the run post build event is set to:
"When the build updates the proj
Hello,
I've created an application installer with WiX toolset (v2.0).
Everything works fine during my tests.
But today I tested the installer with the Microsoft Setup Analysis Tool (SAT)
(included in the Microsoft Application Compatibility Toolkit) and I got the
error message "setup_installer.m
Hi Dhaval,
Does uninstall work too?
I mean will the dll also deregistered if I uninstall the package?
Thanks in advance,
Peter
Don Tasanasanta wrote:
>
> Your solution helped me find what was wrong with mine. For some reason
> the CA didn't like what I was putting in for the Directory value.
I'm trying to create a custom DLL that sets an installer property that
the user can then modify, so I tried starting with a simple example:
extern "C" UINT __stdcall TestFn(MSIHANDLE hInstall)
{
MsiSetProperty(hInstall,TEXT("AGENTID"),TEXT("AgentID from
DLL"));
return ERROR_SUCCES
Original message from Friedrich [trimmed in places] with my comments
inline and prefixed by "RJF":
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Friedrich
Dominicus
Sent: Thursday, March 22, 2007 3:27 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [
You know what, I checked again and it looks like I was looking at the v2
.chm. That would probably explain why it wasn't there :)
I tried referring to util:XmlConfig though, and I'm still getting errors
from Candle. I tried both your suggestion and a fully qualified example
(empty, I know, but
I am using a C# installer class, during installation, I am able to call my
C# install function, however I am not able hook uninstall in wix to call my
C# uninstall function.
In Wix, I am using the following XML to hook uninstall... but the MSI log
shows that this custom action is being invoked du
Have you tried something like this:
INSTALLED
This should execute the action only if the product is installed.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Nitin
Chaudhari
Sent: Thursday, March 22, 2007 9:37 AM
To: wix-users@lists.sourcefor
Is the entry point exposed properly? Either through a definition file, or I
think the other way is
through a pragma.
Rob
Chris Bardon wrote:
> I'm trying to create a custom DLL that sets an installer property that
> the user can then modify, so I tried starting with a simple example:
>
> ext
<[EMAIL PROTECTED]> writes:
> 1) At first I installed the difxapp tools
>- Howerver it is unclear to me if a printer falls under it's
> requirements.
>
> [Snip]
>
> I assume Printer falls under PlugAndPlay.
>
> RJF: That was also my assumption, but as mentioned before I have not
> worked
Did you try the Validate option in Orca?
It will show you all ICE errors and warnings ;)
Regards,
Albert
-Oorspronkelijk bericht-
Van: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Namens Michael Saupe
Verzonden: donderdag 22 maart 2007 13:41
Aan: wix-users@lists.sourceforge.net
Onderwe
Just rereading a few pages On
http://msdn2.microsoft.com/en-us/library/aw2dz878(VS.80).aspx
One can read
To deploy to another computer
|1.
|
| In Windows Explorer, navigate to your project directory and
| find the built installer. The default path will be \Documents and
| Settings\yo
Looks like it. I had a #pragma in there similar to the one in the
sample at http://www.tramontana.co.hu/wix/lesson3.php#3.3 (#pragma
comment(linker, "/EXPORT:[EMAIL PROTECTED]")), but I tried adding a .def
file in addition to that-still nothing.
When I check the verbose log, I don't even see the
Ah, I think I solved it. Moved the tag from the InstallExecuteSequence
section to the InstallUISequence one, and it executed like it was
supposed to. Is there a convention for where these types of things
should go? I want to populate some property values from an included XML
file before installi
Chris Bardon wrote:
> The first attempt tells me that the namespace prefix "Util" (upper or
> lower case) isn't defined, and the fully qualified example says that the
> component element contains an unexpected child element. All I did for
> the DLL was to reference WixUtilExtension and rebuild-is
Jacquet Fabian wrote:
I'm sorry, the exact error message is:
"The Windows Installer service cannot update the system file
c:\WINDOWS\System32\mfc42.dll because the file is protected by
Windows. You may need to update your operating system for this program
to work correctly"
When the installa
Rob Hamflett wrote:
> There's a download for Votive 2.0.4820 available. I've got 2.0.4415
> installed. I don't use the any
> of the project stuff, but it is good for the Intellisense.
>
In the WiX v3 installer, the schemas for IntelliSense can be installed
without Votive. But they're the W
Friedrich Dominicus wrote:
> This suggest that maybe the setup.exe may be used to first install the
> merge module and after that the installer. Is it supposed to work that
> way?
>
Merge modules are only installed when merged into an .msi installer.
They're not standalone entities. That topi
Chris Bardon wrote:
> Is there a convention for where these types of things should go?
The thing with Custom Actions is that they're there for when you want to do
unconventional things,
so I guess you just put them wherever they need to be. The only thing of note
is that a CA that
modifies t
I'm testing a scenario where our software has been installed with the
old installer, and I install a newer version of the software over top of
it using the wix 2.0 based installer.
I wanted to test that if a file could not be written it would cause an
error of some sort. Every file in my inst
Yes, I tried the Validate option in Orca.
The Orca validation result is: no errors or warnings.
But I get the mentioned error using the Microsoft Setup Analysis Tool.
Regards,
Michael
Original-Nachricht
Datum: Thu, 22 Mar 2007 15:29:33 +0100
Von: "Albert van Peppen" <[EMAIL PRO
Hello Jacquet,
Could you post a working example of that?
As you can see in my thread "Shortcut targeting file in a different
component?", I've been trying to do exactly what you're describing,
but have been unable to get it to work. I would certainly love to see
an example of the correct s
Do you know when is evaluated a condition in a Component?
I have a condition on a property which is changed in the UI and the
result of this condition doesn't change with the UI choice.
-
Take Surveys. Earn Cash. Influence
Hi,
I was wondering, is there a certain way to define a public property so that
whatever value u give it on install for example, will still be there when u
initiate a repair, or modify, or uninstall.
For example, this is how I define a public property:
Is this expected behavior and I am doin
Hello,
I'm new to WiX though I have some simple installers working.
I am trying to get the XmlConfig Element to work but I get an "element
contains unexpected child element" error when I use the "XmlConfig" element.
I can't find much on Google or the Archives, there are some mentions but no
sati
I don't know if the functionality you're thinking of exists, but
alternatively you could set the property based on a registry entry you
set during installation.
Chris
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Lindsay
Harris
Sent: Thursd
Hi Chris, thanks for your reply, I have already started implementing it that
way, I guess I was hoping there was a more elegant solution.
Thanks,
Lindsay
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 22, 2007 11:23 AM
To: Lindsay Harris; wix-users@lists.sourceforge.net
Do you mind logging a bug on the _TimeStampAfterCompile? I'll look into
that.
As far as forcing a recompile... You can do that by including your inputs
into your .wixproj project file as elements. In Votive, you do
this by selecting "Content" from the Build Type property in the property
browser (
I'm working on replacing an existing setup procedure with a Wix
installer, and I think I have almost all of the components I need. The
one thing I'm missing however, is a piece of functionality we have in
Installshield that's pretty important to how our applications are
delivered. We have a clien
MOTORISTS MUST REMAIN ALERT AS ANY ADDITIONAL RISES MAY PUT WATER OVER
THE ROAD OR PUSH DEBRIS INTO THE DRIVING LANES.
0 QUINCY 17 15. 1 FEET WAS BELOW THE 9 FOOT FLOOD STAGE.
VANDALIA 535 AM CDT THU MAR 22 2007 .
AND IF THESE STORMS DO STRENGTHEN LARGE HAIL AND DAMAGING WINDS WILL
It's so easy to get lost in this song when you hear it.
Of course there are far more french wines that I'm willing to drink than movies
I'm willing to watch - but lets not ruin the plan here.
Still it may not all be obvious. 2007 20:31:57leckerDer vorbereitende Einkauf
will bedacht sein. It's a
Hello,
I'm converting an existing InstallShield merge module to Wix. This
merge module puts some files in the Windows Installer cache directory to
support maintenance operations.
My code is as follows:
It might be a good idea to schedule this based on the state of the component
or feature. That way you can tie the custom action's execution to whether
or not the specific component is being installed/uninstalled based on that
state.
$TheComponent=2 (component is being uninstalled)
$TheComponent>
It looks like several people, including me, have asked recently how
to create an optional shortcut -- that is, how to create a shortcut
that is only installed if a checkbox is checked in the UI. Thanks to
some private help from another member of the list (who can identify
himself if he'd
Hello,
I've fixed my problem but I'm not entirely sure why the fix works and
I'd like to know. In fact, I made the change so I could search my
verbose log a little easier.
I ended up changing the Directory Id and short name for the Guid
directory to something like Xyz so that it would be e
You really should not be writing to the Installer directory. Why are you doing
that?
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Svare
Sent: Thursday, March 22, 2007 2:29 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] FW: Directories/Merge Modules
Hello,
I've been trying to figure out how to copy some files located in the
directory the msi file is being run from to the Install directory, the
big problem being that I couldn't find an easy way to fetch the value
of the source directory.
SourceDir leads to the root of the drive and CURRENTDIRECTORY i
MOSTLY CLOUDY WITH RAIN SHOWERS THROUGH THE MORNING. THE FLOOD ADVISORY FOR
RAIN AND MELTING SNOW REMAINS IN EFFECT UNTIL 600 AM ADT FRIDAY FOR CAPE
FAIRWEATHER TO CAPE SUCKLING COASTAL AREA. SOUTHEAST WINDS ARE EXPECTED TO
INCREASE TO 20 TO 30 MPH WITH GUSTS TO 45 MPH BY LATE TONIGHT THROUGH F
Why are you copying files from the original media instead of just using the
File element?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Geoff Finger
Sent: Thursday, March 22, 2007 3:45 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Accessin
Rob,
There have been some maintenance/uninstall issues with needing physical
media that have be avoided by putting UI type dll's there. I'll find
out the entire history tomorrow and post.
I'm very interested to see if this is necessary or what the recommended
course is for the situation.
I believe that but why are you putting stuff in the Windows directory? If
you're not part of Windows don't freakin' put stuff in the Windows directory
(unless some Windows API puts stuff in the Windows directory, like installing
assemblies to GAC). And I mean that in the nicest sense.
From
Hi Dana,
Thanks for the reply, having $TheComponent=2 in my custom action did solve
the issue. So now the following works.
$MainDLL=2
$MainDLL=2
On similar lines I tried $MainDLL>2 for rollback and commit
actions... it did not seem to work... any pointers to related
documentation.
My curren
Hi,
What do u mean by set the property based on a registry entry?
I have this property :
And this Custom action which sets the above property
There is another custom action which uses the above property
The installation log shows the following:
…
Action start 19:08:22: LaunchConditions
From: "Rob Mensching" <[EMAIL PROTECTED]>
To: "Geoff Finger" <[EMAIL PROTECTED]>;
Sent: Friday, March 23, 2007 12:28 AM
Subject: Re: [WiX-users] Accessing the Source Directory
> Why are you copying files from the original media instead of just using the
> File element?
>
While I'm not the ori
Here is an exemple
DesktopIcon = "1"
The only problem I have is DesktopIcon property is used in a dialog (with a
checkbox control) and it doesn't change anything. Checked or not, the shortcut
is installed only if I initialize DesktopIcon property to 1. I'm searching
In my product I need support functionallity of downgrading. For example,
after release of the version 2.0.5 and version 2.1.0 and after installing
2.1.0 user can install 2.0.5 and it installs correctly. But how to implement
this without bootstrapping, using only MSI functionality?
If I use major u
Hi Thomas
The C:\Windows\Installer\ folder is hidden system folder which is
used by Windows Installer INTERNALY. It means that you should not
install any files to this folder (I think).
Anyway, you should use the
to get the correct Windows folder location.
Regards
Stefan
Thomas Svare wrote:
>
Thank you for this explanation.
I don't really understand why you add a registry key...
Maybe I don't know what is a keypath
-Message d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Stuart A. Malone
Envoyé : vendredi 23 mars 2007 8:00
À : wix-users@lists.sourcefo
54 matches
Mail list logo
