I'm still trying to track down the PYRO0252 error from Pyro. I think it may be
due to the ComponentRef element(s) in the PatchFamily element of the WSX source
file. All the samples are very, very simple with just one component. My setup
has many, many components.
I found in the documentation of
I have two applications, "A" and "B". They are actually 99% the same
assemblies, basically differing only in config files which dictate which
classes obtain control (a very pluggable architecture). Thus we normally
install all the assemblies, and pass the extra config file in the shortcut.
They
Take a look at http://msiext.codeplex.com that has some wix extensions that
might allow you to do all of what you want.
Here's from the MSSQLDatabase sample:
Hope this helps,
-dB.
dB. @ dblock.org
Moscow|Geneva|Seattle|New York
-Original Message-
From: Simon Topley [mail
This is working code for a list that already has an item.
LONG insert_index = index;
for each (const std::wstring& name in names)
{
// the first record is inserted at index 2, there's at least one
default item in the view
MsiHandle hRec(MsiCreateRecord(4));
It's tricky. There's a product out there that belongs to a very big corporation
(not Microsoft), that has severe complications when you tell it that it should
be putting logs into a path with parenthesis. Because we need those logs, we
needed to put our software into a path without parenthesis.
http://msiext.codeplex.com has a CA to get extensive user info that uses Win32
API.
Here's what it returns:
\return USER_FQN DNS domain name followed by a backward-slash and the SAM
username
\return USER_NAME full username, includes the domain for domain users
\return USER_DOMAIN qualified do
If I had two applications which shared some core assemblies, how would
these handled between two installers? If I shared a WiX fragment source
file between two WiX projects, the components would have the same GUIDs.
Would that cause a problem or conflict? Could the two projects be
installed, f
I have a WiX MM project that builds through Visual Studio without any
validation errors. However if I use ORCA to validate the module ( using the
mergemod.cub found in the WiX directory ) I get a series of ICE68 error
messages complaining that the CA type is invalid.The CA name's and types
Nope, I don't see them being updated. I am checking this with Orca. Even the
custom actions that I got working, I had to add them to a patch family.
Thanks,
Sharat Janapareddy
~ 40269
-Original Message-
From: Heath Stewart
Sent: Friday, November 20, 2009 2:34 PM
To: Sharat Janapareddy
> Hi, I've created a patch from 2 MSI files (unfortunately I don't have
> the original wix object files so have to use MSIs) using the
> following, which all seemed to go fine:
>
>
>
> The patch seems to have been created fine and seems to run fine except
> for one problem.
>
> One of the comp
FYI, I was able to figure out how to include CustomActions in the patch. But
the one thing that I don't see in the WIX documentation is how to patch
Standard Actions.
Thanks,
Sharat Janapareddy
~ 40269
-Original Message-
From: Sharat Janapareddy [mailto:sharat.janapare...@microsoft.com
I'm building an msp using wix v3 for an msi that was built with version v2.
So If I provide the msi I get this :
torch -p -ax "C:\F14patch\OCS\EN-US\Error\extracted\fso.msi"
"C:\F14patch\OCS\EN-US\Fixed\Extracted\fso.msi" -out diff.wixmst
torch.exe : error TRCH0280 : The -ax option requires a di
We made some changes to the MSI installer that was released this year and we
are releasing the SP soon. One of those changes include adding support to
uninstall the patches. For this, we modified some Custom elements in
InstallExecuteSequence table of the MSI generating WXS file. (I am not sure
I just started using smoke for verification, I notice that many of the
messages have the same warning/error id, even when the ICE number and
message content are different. For example:
warning SMOK1076 : ICE30: The target file 'rwfvlhtq.lm8|ATL80.dll' might be
installed in '[SystemFolder]' by t
Hi,
My scenario needs to create/update registry values on Install/Change.
My code to create the registry is:-
The registry is created on install with the value of MYPUBLICPROP. However
after install, if I choose 'Change' to update the public property the registry
value is
Hi, I've created a patch from 2 MSI files (unfortunately I don't have
the original wix object files so have to use MSIs) using the following,
which all seemed to go fine:
msiexec /a orig\Installer.msi TARGETDIR=c:\src\patch\orig\admin
msiexec /a new\Installer.msi TARGETDIR=c:\src\patch\new\admin
Since several of you have suggested trying the torch/pyro method of creating a
patch, I am trying that. Sorry to be a pain, but I'm stuck on the pyro step.
Gabor's tutuorial uses the word "Sample" in a LOT of places and no matter what
I try in my actual example, I get a PYRO0252 error. The text
Alexander Miseler wrote:
> I basically want a one file setup, but my content is way above 2 GByte. Thus
> I will have something like my_product.exe, my_product2.cab, my_product3.cab,
> ...
> The EXE contains the MSI, the my_product1.cab, and some other stuff. When
> executed the content of the EXE
Yan Sklyarenko wrote:
>FileA.txt.patched (the one installed by the patch)
>
I'm not a patching guru, but I highly doubt that's going to be possible.
The resource (file) would no longer represent how it's defined in the
component.
--
sig://boB
http://joyofsetup.com/
-
rahul.ekb...@sungard.com wrote:
> When we installs our product, though we choose other drive like d: or e:
> still it checks the space of c: drive. It asks minumn 700MB empty space on
> c: drive.
>
http://blogs.msdn.com/heaths/archive/2008/07/24/why-windows-installer-may-require-so-much-disk
Rich Daniel wrote:
> KeyPath="yes">
>
You should consider making the executable file the keypath for the
component; patching and upgrades work a lot better if there's a
versioned file as keypath.
>
>
>/>
>
>
Please consider contributing a fix to WixU
The MSI works with this new fragment:
Thanks
- Rich
-Original Message-
From: Rich Daniel [mailto:rdan...@microsoft.com]
Sent: Friday, November 20, 2009 10:31 AM
To: General discussion for
http://dotnetinstaller.codeplex.com does this via MsiEnumProducts.
http://dotnetinstaller.codeplex.com/sourcecontrol/changeset/view/34925?projectName=dotnetinstaller#640592
http://dotnetinstaller.codeplex.com/sourcecontrol/changeset/view/34925?projectName=dotnetinstaller#640586
Hope this helps
No.
No its not working. I tried different ways.
Let me copy the code here and show what exactly I changed.
This is the custom dialog code
INSTALLTYPE
="CompleteServer"
INSTALLTYPE
="CompleteDatabaseServer"
INSTALLTYPE="CompleteWorkstation"
I am pleased to announce the open-sourcing of AppSecInc. MSI Extensions under
the Eclipse Public License.
http://msiext.codeplex.com/
This is a collection of MSI custom actions and WIX extensions, originally
developed for a large enterprise product, and now open-sourced under the
Eclipse Publi
Here's what I recall from memory - the MSI is cached under
[Windows]\Installer folder, which takes up space. Space is also
required on the drive that Windows is installed on in order to unpack
local copies of files/cabs before they're placed in their final
destinations.
If you review the MSI docu
After diffing the registry changes between the WiX and Installer setups, I
think I found the difference.
In the installer, there is an extra CategoryOptions key that is set to 3. After
some digging, I found this article
(http://blogs.msdn.com/bclteam/archive/2005/03/16/396856.aspx) explaining w
In article ,
Uday Kumar writes:
> In wix-msi how can I pass the values between two dialog boxes. I will
> select one item from combo box of first screen/dialog, based on the
> selection, secon d screen combo box should populate. How can i pass the
> values of screen one to second screen.
I
Sounds interesting, but I don't understand how I would do that from the help
page. It talks about two text files - are those supposed to represent the
hundreds of files in my installation?
Can you point me towards any sort of tutorial using pyro, etc., because as I
stated earlier, I have no i
I basically want a one file setup, but my content is way above 2 GByte. Thus
I will have something like my_product.exe, my_product2.cab, my_product3.cab,
...
The EXE contains the MSI, the my_product1.cab, and some other stuff. When
executed the content of the EXE is copied to a temp directory and
Ah you are right. I misunderstood the part where you were talking about
*other* applications sharing file type registrations. Apologies for any
confusion.
-Original Message-
From: Jan Wester [mailto:happyhon...@gmail.com]
Sent: 20 November 2009 12:03
To: General discussion for Windows Ins
On Fri, Nov 20, 2009 at 10:59 AM, Peter Shirtcliffe
wrote:
> I was looking at sharing file extension registrations between
> applications only yesterday. This page and its related content were most
> useful
> http://msdn.microsoft.com/en-us/library/bb166183(VS.80).aspx
That is an interesting post
Thank you Blair, I'm using Vista with 4.5.
Hopefully the RemoveFile table will solve the problem. :)
Thanks,
William L.
On Fri, Nov 20, 2009 at 5:24 PM, Blair wrote:
> Which version/build of Windows Installer?
>
> Much of what ends up in Windows Installer logs is itself undocumented and
> some
On Fri, Nov 20, 2009 at 10:22 AM, Blair wrote:
> Aaron's blog will help you with building your two MSIs (32- & 64-bit) using
> the exact same sources. On a 64-bit OS, explorer.exe will be a 64-bit app,
> so you won't need the 32-bit mirrored installation. However, if you feel you
> really need the
On Thu, Nov 19, 2009 at 11:00 PM, Chad Petersen
wrote:
> Aren't shell extensions either a DLL or OCX file as the entry point?
> Think about what you have to do to manually deploy your shell extensions
> and write down the steps (if it helps). These are the steps that you
> would then author in WiX
The wxs effectively does what is described on the following page:
http://msdn.microsoft.com/library/aa371878.aspx, which produces a
registration in the system registry of the performance counter. A quick
search for me didn't reveal what the implementation of the
PerformanceCounterInstaller class do
I was looking at sharing file extension registrations between
applications only yesterday. This page and its related content were most
useful
http://msdn.microsoft.com/en-us/library/bb166183(VS.80).aspx
-Original Message-
From: Happy Hondje [mailto:happyhon...@gmail.com]
Sent: 19 Novembe
Hello WiX Community,
I have been analyzing the log file of my patch installation, and faced
with a weird numbers I don't know the origin of. Here's the snippet:
"
...
TRANSFORM: The minimum 'Media.DiskId' value inserted by a patch
transform is 100
TRANSFORM: The maximum 'Media.DiskId' value inser
Which version/build of Windows Installer?
Much of what ends up in Windows Installer logs is itself undocumented and
sometimes doesn't seem to continue in the next released build of MSI.
As to folders not being removed: folders won't ever be removed if any files
(that the MSI doesn't "own") are le
Aaron's blog will help you with building your two MSIs (32- & 64-bit) using
the exact same sources. On a 64-bit OS, explorer.exe will be a 64-bit app,
so you won't need the 32-bit mirrored installation. However, if you feel you
really need them, you could use the preprocessor command and
"duplicat
I haven't looked into the code yet, but would "TEMP" (or even "TMP") move the
remaining locations?
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Thursday, November 19, 2009 8:22 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-u
Hi all
I have problem that is described on:
http://sourceforge.net/tracker/?func=detail&atid=642714&aid=2887011&group_id=105970
In short:
Language transformation created using command:
torch.exe -t language Package_EN.msi Package_DE.msi -out 1031.mst
does not contain the ProductLanguage property.
Say hello to MSI 4.x and embedded chainers.
-Original Message-
From: akihiro.shib...@jp.yokogawa.com
[mailto:akihiro.shib...@jp.yokogawa.com]
Sent: Tuesday, November 17, 2009 5:29 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to create main and sub installer?
Hi, All,
My understanding is that patching always has REINSTALL set. Try "msiexec
/update mypatch.msp /l*vx patch.log" and examine the properties to see what
is and isn't set when you attempt to apply your patch.
Also I ask, you will never support a major upgrade? I wish I had that kind
of confidence in th
Always add " OR Installed" to all of your LaunchConditions. If the product
is already installed, you want to allow repairs and removals, including
upgrades.
-Original Message-
From: spsingam [mailto:siva.poobalasin...@gmail.com]
Sent: Tuesday, November 17, 2009 8:13 PM
To: wix-users@lists
If your MSI was installed via group policy, and you succeeded in launching
your application, it is possible that no user would ever see it to know that
it needed upgrading.
You could try adding a custom action in your MSI that runs your
upgrade-check and if there is a newer version you fail the in
Hi,
The problem has been resolved. It is because of the setting. I set it again as:
setting Project, Properties, General, Character set. Select unicode (wchar_t)
or MBCS (char)
Now including has no error. So I can use CStrBufW for setting string.
Regards,
Chunyan
-Ursprüngliche Nachrich
We had a build process that ran from a service account in a "build lab" of
over a thousand machines. We discovered that msimsp.exe/patchwiz.dll will
sometimes pop up a dialog box if we didn't do a good enough job catching all
the possible error conditions and stall waiting for its OK button to be
p
There were schema changes between 2.0 and 3.0 which would make the authoring
look a little different, and tool changes which affect the way we get to our
output files. For WiX, PCP is just another Windows Installer file format.
For Windows SDK, it is a driver file for msimsp/patchwiz. The other inp
"fail to register". Could you please elaborate? How are you registering, and
what exactly is the error message that the user is able to "ignore"?
-Original Message-
From: Selvakumar B [mailto:selvakuma...@realimage.com]
Sent: Tuesday, November 17, 2009 5:04 AM
To: General discussion for W
(wix-user-request is used for adding/removing yourself from the mail list.
It isn't used for sending messages to the list itself).
Open your MSI in Orca, apply your last patch to it (in Orca), read from your
Property table.
-Original Message-
From: BSR PHANI [mailto:bsrphani...@gmail.com]
You have to know the number of instances you will support before-hand and
generate an instance transform for each instance you will ever have. I
understood your requirement to have an open-ended number of "instances",
each of a different build of your product. The multiple instance pattern
allows t
52 matches
Mail list logo
