Just to make my life easier, now that I corrected the mistake and
double-checked that I haven't committed component violation again, I am
back to having exactly the same problem.
Pyro doesn't find anything to put in a patch cab and running verbose log
doesn't reveal anything.
Even a nice tool like
I can confirm this now that I produced two MSIs that don't have any
component rules problems. Some history of this problem can be found in
posts titled 'Does Pyro (or Torch) ignore 4-th version number?'.
I have 2 MSIs and 2 corresponding binary wixout files. Using new
patching with wixout input pr
riginal Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 07, 2008 12:04 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] New wix binary delta patching doesn't work
Tony Juricic wrote:
> I have 2 MSIs and 2 corresponding binary
I use one of my main installed folders and go back one level to get the
root. All installed folders become public properties (property name the
same as folder Id) available also during the uninstall if not in
deferred CA.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
I use one of my main installed folders and go back one level to get the
root. All installed folders become public properties (property name the
same as folder Id) available also during the uninstall if not in
deferred CA.
-Original Message-
From: Dmitry Berkovich [mailto:[EMAIL PROTECTED]
I am using condition "NOT PATCH" to change the text in UI to say "Patch"
instead of "Repair" when patch is applied. That works just fine.
Now I want to avoid installing one Registry component during patch
application but not during the repair. I used the same condition (i.e.
NOT PATCH rather than
I tried adding Transitive attribute to the registry component and that
deleted the component when patch was applied. Thus 'NOT PATCH' is a
correct condition since transitive components are removed when condition
changes from true to false.
However, for some reason that I would really love explaine
You can always use custom action to write that part of the Registry.
However that would not be politically correct. I mean, using CA when MSI
database solution is available. Unfortunately sometimes it appears as if MSI
people do everything they can to force us to use CAs even in cases which look
It is a good advice, thanks!
Since I can have patching options configurable via REINSTALLMODE, I see
no good reason to hard-code "PATCH" property conditioning inside wxs, as
I did for registry writing action.
However, just as I accepted thinking in terms of resources inside
components, abstracti
Even if I add comments attribute to PatchInformation element, the
resulting MSP Patch Summary Information Comments editbox is empty when
viewed in Orca. It is also unclear if and how can one set up Title,
Author and Subject parts of Summary Information via WiX.
Have you had any success in somehow using that bootstrapper with WiX
generated MSI?
Can you share some insights/experiences?
For me installing SP1 turned out into a "progress bar sits there not
moving anywhere for hours" experience so the whole idea of a smaller
"Client Profile" footprint turned
I've got one working version and it turned out to be very quick and
easy. I tested it on one pristine XP SP2 installed in Virtual PC and it
works like a charm. Quite a relief after waiting one hour for SP1
install to tell me that I need to close WiX.chm HTML Help file.
The procedure is the followi
I use PATCH property as a condition to change text from 'Repair' to
'Update'. There is nothing wrong - patch is a sort of repair.
-Original Message-
From: postingbox [mailto:[EMAIL PROTECTED]
Sent: Monday, August 18, 2008 7:14 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Re
Don't patch the patch!
Always target:
a) only RTM
b) RTM + another (non-patched) full install built after RTM
c) same as b plus you can add all full install MSI targets built after
RTM and preceding your patch build)
I don't know why 'they' (i.e. secretive installer people who reveal
pieces of a
Good to know! Hopefully WiX compiler can catch these errors in the
future.
What you described looked very similar to my past experience but,
checking the old forum posts I see that it caused a different error:
1328.
Basically I had a case like:
RTM.msi Update1.msi Update2.msi ... etc.
My fir
Ok, that makes sense. However, I can't get it to work either way. The
problem is not in changing just the 4th version number either. I created
a simple C# console executable that has one line of code:
Console.Writeln("This is version 1.0.0.0");
and assembly info AssemblyVersion("1.0.0.0")] and
As
I don't understand why Microsoft expects anybody to bother with .NET
Client Profile?
I am not saying that the idea in itself is bad. It is just too little
too late. In fact so little and so late that I think that it is really
lame, despite the accolades that independent recycling of MS whitepaper
Oops, this was really intended for miscrosoft.public.platformsdk.msi.
I did a test with XP with Framework 2 already installed and then run
Client Profile install. What you get is pretty much the same as if you
had downloaded 3.5 installer from MS site manually and then run it. IOW,
your user will
a1) In theory, using new WiX patching you can simply exclude components
containing binaries that you don't want to patch from the list of
components to patch. This list is child of PatchFamily WiX element. If
using 'old' patchwiz.dll-based patching (i.e. WiX PatchCreation element)
you can use Prote
Regarding programming the Progress Bar
http://msdn.microsoft.com/en-us/library/aa367525(VS.85).aspx
and especially
http://www.mirrorservice.org/sites/download.sourceforge.net/pub/sourcefo
rge/m/ms/msiprogramming/BillboardsAndProgressBars.pdf
is probably the best documentation that you can find
There is also PatchIgnore attribute that can be set on individual file
element. It's a pity that we can't do it for Registry keys and values
too.
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
I had the same problem and switched to self-registering servers, i.e.
setting SelfRegCost attribute on corresponding file elements.
I know this approach is not officially recommended but it is hard to see
what some third-party COM servers do with the Registry.
-Original Message-
From: Eva
You just invoke custom action before files are removed. I don't backup
files but do some COM unregister before files are removed and there are
no problems doing that.
-Original Message-
From: xiaoli [mailto:[EMAIL PROTECTED]
Sent: Friday, September 05, 2008 1:46 AM
To: wix-users@lists.so
I often encounter problems debugging deferred C++ DLL CAs. Most of the
time DebugBreak() works. Now and then it won't and then I use __asm {
int 3 } which, for some reason, tends to work more often than
DebugBreak.
Then I encounter situations when even int 3 won't work in the sense that
Vista (an
Some patches are un-installable:
http://msdn.microsoft.com/en-us/library/aa372102(VS.85).aspx
I'm offering to pay and ship few cases of beer and hamburger patties so
that you guys at Microsoft can meet somewhere at campus, relax, hammer
this out and explain all of it (I mean patching business) to
Answering my own post - the problem was that Product element must have
compressed="no" attribute set when building MSI with no CAB.
I had this attribute set to "yes".
-
This SF.Net email is sponsored by the Moblin Your Move
I am trying to build MSI with no cab and all files uncompressed. I have
the following Media element declaration:
Myproject.wxs(1266): error LGHT0135: The file '_SOMEDATAFILE.TXT' should
be compressed but is not part of a compressed media. Files will be
compressed if either the File/@Compre
I am getting a stack overflow exception when executing deferred custom
action in C++, but I am consuming only a quarter of 1 MB which, I
believe, is the max stack space allowed per process.
Did anybody here have similar things happen to him/her?
I'm wondering if msiexec indeed gives much reduced
ovember 10, 2008 10:57 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Stack available for Custom Actions
What are you doing to run out of stack space? When I get a stack
overflow it has always been a bug in my code.
-Original Message-----
From: Tony Juric
using.
Maybe pick a different 3rd party vendor?
-Original Message-
From: Tony Juricic [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 11, 2008 05:50
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Stack available for Custom Actions
I invoke 3rd-part
Newbie - I have a similar need to use support DLLs and action during
install and uninstall.
Can somebody please explain or provide a link to a sample on how to use
custom action to extract binary files?
-
This SF.net email is
ilto:[EMAIL PROTECTED] On Behalf Of Tony
Juricic
Sent: Tuesday, May 27, 2008 7:09 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Merge Module system folder Id clash problem
I install some files in Windows System32 using directory declaration
like:
...
Additionally, my project
I've seen sample code in blogs like:
hr = WcaGetProperty(L"SQLSERVERPASSWORD", &pszPassword);
ExitOnFailure(hr, "Failed to get property");
.
LExit:
.
ReleaseString(pszPassword);
and I started following this style in my custom actions. However, I
don't know how ar
I am working on a rather complex project using Wix 3 beta. It is
expected that we will eventually generate frequent patches and minor
upgrades (i.e. hotfixes and SPs) so a stable standard Wix plus patching
functionality would be very desirable. Within next few months, if
possible :)
If MSI SDK bo
I'm using the following standard declaration to show ExitDialog:
How do I display the dialog right before this one?
Or do I have to 'cheat' and put in the example above the dialog that I
want shown before 'the true exit dialog' and then link its Next button
to the
, May 29, 2008 12:11 PM
To: Tony Juricic
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Show dialog before ExitDialog
Tony Juricic wrote:
> Or do I have to 'cheat' and put in the example above the dialog that I
> want shown before 'the true exit dialog' and
This is most probably not Wix-specific but anyhow:
Uninstall string that is registered for my app is the following:
MsiExec /X{Product code}
However, when uninstall is selected via ARP this causes uninstall to run
at reduced (or basic, not sure) UI level, with no Wizard dialogs. I want
full GUI
lf Of Tony
Juricic
Sent: Wednesday, June 04, 2008 15:43
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to Uninstall from ARP with full GUI?
This is most probably not Wix-specific but anyhow:
Uninstall string that is registered for my app is the following:
MsiExec /X{Product code}
Ho
I would like to see all custom actions and wcautil functions documented
*with an example*.
One can argue that they are just the wrappers around MSI functions and
thus : read the documentation!
However, initially one approaches these functions in the hope of making
sense out of SDK documentation and
Is there any reason why WcaIsPropertySet takes ASCII string, i.e.
BOOL WIXAPI WcaIsPropertySet(
__in LPCSTR szProperty
);
while all the rest of API uses wide character strings?
-
Check out the new SourceForge.net M
Can anybody give a brief intro on how to use deferred CA data functions
such as
WcaDoDeferredAction,
WcaWriteStringToCaData,
WcaReadStringFromCaData, etc. ?
I have a deferred custom action that needs to read a lot of properties
and these functions seem like the right ones to use.
Deferred action
Data"),
szDirectoryToDelete, &dwlen);
// TODO: Handle error return.
DeleteDirectory(szDirectoryToDelete);
return ERROR_SUCCESS;
}
I hope that helps in some way.
Ryan
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tony
Juricic
Interesting! I am porting InstallShield project to Wix and I see that IS
keeps leading 0s.
-Original Message-
From: Neil Enns [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 18, 2008 12:23 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WiX and Suppo
Yes, you can create custom action that sets one property to the value of
another. And you can Publish multiple DoAction events on button press.
Examples:
MY_PROP_SOMETHING=1
-Original Message-
From: Troy Simpson [mailto:[EMAIL PROTECTED]
Sent: Fr
Build and Tool Settings pages for my existing project in VS 2008 now
show red icon and say:
An error occurred trying to load the page. Value does not fall within
the expected range.
-
Check out the new SourceForge.net Marketpl
I am searching for Notepad in 2 locations like this:
On most systems Notepad is in both locations so property is initialized
to the location of the last find,
As shown here in MSI log:
AppSearch: Property: NOTEPADEXE, Signature: NotepadFile
I have ported InstallShield (version 12) project to Wix 3. InstallShield
has msi embedded in exe and the whole setup.exe is 50 MB large. Wix
creates MSI with embedded compressed CAB which takes 70 MB.
20 MB is a pretty large difference! Am I missing something obvious or is
InstallShield compressio
I closed VS 2008 before installing new WiX version. The problem appeared
as I restarted VS, loaded solution containing the existing WiX project
(among other Custom Action C++ DLL projects) and then clicked on
project's Properties context menu.
I recreated the project from scratch and the problem i
Custom Action scheduled after InstallFinalize do work. I have one that
invokes DLL exported function and, using __asm { int 3 } in my CA C++
code I get JIT debugger started.
I think your problem may be that you are expecting the action to start
the executable, while your action is just assigning o
Beyond that I have to ask the obvious question: are you sure the set of
payload files is the same?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tony
Juricic
Sent: Thursday, June 26, 2008 8:14 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] T
ckage.
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
--- On Thu, 6/26/08, Tony Juricic <[EMAIL PROTECTED]> wrote:
> From: Tony Juricic <[EMAIL PROTECTED]>
> Subject: Re: [WiX-users]
This suggestion touches the question I was thinking to ask for a long
time:
I want to perform file/registry key/etc. copy/removal at various times
during install.
I would prefer to use standard actions for that to gain automatic
rollback.
So I have to schedule standard actions to run multiple
I had similar things happen to me and solved them by using CA like:
In this case above dialog title contained [ProductName] which was not
resolved. Then you schedule CA very early and insert the property name
where you need resolved string.
The only way I can understand this is that MS
I picked this dialog from some Wix UI scheme and it is now compiled into
my project. However, I have no idea how to use it or how to get the
system to invoke it !?
Namely, during my testing, some other, system-provided dialog (i.e. not
part of any UI that I added) pops up and offers to close the
a
I have 10 bitmaps that I would like to cycle among FileInstall and my
custom action that follows FileInstall.
My execute sequence looks like this:
Bitmaps are split between these two actions like in this example:
101 - 155 of 155 matches
Mail list logo
