ges. Any chance you could
> release different MSPs (one for each language) in the same fashion?
>
> The only further insight I could give would probably require digging into
> your actual MSIs.
>
> -Original Message-
> From: Shawn Dwyer [mailto:shawn.o.dw...@gmail.com]
> S
Thanks
On Thu, Nov 12, 2009 at 2:21 AM, Shawn Dwyer wrote:
> I've finally got a solution that works I think. I've basically gone back
> to option 1 - having an admin old and admin new image for each language and
> running torch for each one. However, because the actual file
s other method now.
Thanks again for all your help, I’ve learned a lot about how this works
through your explanations that I just wasn’t picking up from the help files.
Thanks,
Shawn
On Wed, Nov 11, 2009 at 1:26 PM, Shawn Dwyer wrote:
> Hi Blair,
>
>
>
> Thanks again for the pro
ow
>
> * g UpgradeCode must match
> * r Product ID must match
> * u Check major, minor, and upgrade versions
> * x Upgrade version = target version
>
> What we want to eliminate is "-val r". So, the command line we really want
argument to torch to change the validation flags (and don't use the "-t"
> argument). However, any changes to the text in the admin image you use will
> be applied to both languages without regard to the language itself (meaning
> you will bleed those text changes across the
Hello,
I've seen multiple similar posts but none seemed quite what I was looking
for, sorry if this has already been answered.
We have released one MSI for each language we support - each with it's own
ProductCode and CodePage.
Using Wix only patching, I thought it should be possible to sp
didnt
show anything) that was preventing the file from being installed. Now that
the UI isn't being shown on patches, the files are all updated as expected.
On Sat, Jun 6, 2009 at 6:17 PM, Bob Arnson wrote:
> Shawn Dwyer wrote:
>
>> Thanks Bob. I couldn't seem to find a P
e=InstallState.Absent resolved the issue.
On Tue, Jun 16, 2009 at 1:06 AM, Shawn Dwyer wrote:
> Bob Arnson wrote:
>
>> It's all about MSI, not WiX, so you might want to try the MSDN MSI
>> newsgroups.
>
>
> Thanks Bob! Here is the link to my question on MSDN MSI
ult.aspx?dg=microsoft.public.platformsdk.msi&mid=508c26a1-5e90-4686-a1ce-b42eef359d69&sloc=en-us
On Mon, Jun 15, 2009 at 10:38 PM, Bob Arnson wrote:
> Shawn Dwyer wrote:
> > I posted this question on an older thread and haven't heard anything, so
> I'm
> > wondering if it got through
Hi,
I posted this question on an older thread and haven't heard anything, so I'm
wondering if it got through. Sorry if it did. Here is the older thread for
reference:
http://www.nabble.com/Major-upgrade---feature-migration-td23222720.html
During a major upgrade some features that are not alread
Shawn Dwyer wrote:
> I have a few question regarding this:
> 1. Why does it think Feature2 is installed?
> 2. Why does it have Feature2A as Advertise (I would expect Absent)
> 3. Once I get this working I'll need my DTF custom action to check the
> states. Does MigrateF
I am having a similar problem, where during a major upgrade
MigrateFeatureStates is setting features that are not actually already
installed to Local. My product has the option to install any of 4 features,
with two defaulting to Local each with a must have subfeature.
les in the InstallExecuteSequence table either.
What would cause this not to be included? Do I need to explicitly sequence
this in my original or update MSI?
Thanks,
Shawn
On Wed, Jun 3, 2009 at 9:54 PM, Bob Arnson wrote:
> Shawn Dwyer wrote:
>
>> below. In the example, NewFile.exe and NewFile.exe.
Hi,
Using Wix 3.0.5315.0 I'm trying to create my first real (non-sample) MSP
following the instructions here:
http://blogs.msdn.com/pmarcu/archive/2008/05/30/Patching-something-you-didnt-build-with-WiX-using-WiX-.aspx
I created the admin image from version 3.0.37 of my app, copied it, and
replace
ect Target Path outside Merge Module (stephan o'farrill)
> 4. Custom MergeModules (MacDiarmid, James D)
> 5. How to get OnExit status in custom action using DTF (Shawn Dwyer)
> 6. Re: WiX-users Digest, Vol 36, Issue 64 (Neil Sleightholm)
>
>
> -
Pan - They are all blank for me as well
On Thu, May 14, 2009 at 2:15 PM, Hu, Pan wrote:
> I'm trying to access the following URL for a how-to-guide on shortcuts:
> http://wix.sourceforge.net/manual-wix3/create_start_menu_shortcut.htm
>
>
>
> It always gives me blank pages, no matter what link I
If I schedule a custom action for OnExit, is there an easy way from inside
the custom action to determine if it was being called for OnExit="success",
"error", or "cancel"? It seems like this is simple but for some reason it
escapes me.
For example if I wanted one exit dialog that showed the inst
I have a similar problem with our 2.x installer which has already been
released. Now that we are preparing our 3.x, because of all the rules we
are doing a major upgrade and have changed the product code, leaving upgrade
code the same. This works fine for 3.x automatically detecting and
uninstall
Hi,
I've got a scenario where we need to uninstall a product with a different
UpgradeCode than the main product *before* uninstalling previous versions of
the main product. I've tried changing the order around for the Upgrade and
UpgradeVersion elements in my WXS file, however no matter how I ord
I does get remoted. So there might be a bug in that
> method. When I get a chance, I'll try to add a test case to verify
> GetCost().
>
> -Jason-
>
> -Original Message-
> From: Shawn Dwyer [mailto:shawn.o.dw...@gmail.com]
> Sent: Tuesday, March 03, 2009 8:57 AM
> T
Hi,
I'm trying to put together a simple managed custom action using DTF which
will show each of the features, their descriptions, and their cost. It
seemed straight forward enough
string msg = "";
foreach (FeatureInfo fi in session.Features)
{
msg += string.Format
(
"Title: {0}\r\nDescript
act\Foo\File.txt
>
> Then the call to _wsopen__s (line 10) to that file path...well, the
> directory doesn't exist ('C:\Extract\Foo' [however 'c:\Extract' does]) and
> this function doesn't create it, so it returns failure and a -1 for "hf".
>
Has anyone gotten this error when using DTF?SFXCA: Failed to extract to
temporary directory. Cabinet error code 11.
Has anyone managed to pack a directory using another method?
Thanks,
Shawn
On Thu, Feb 26, 2009 at 12:01 AM, Shawn Dwyer wrote:
> I think I'm getting close but I'
On Wed, Feb 25, 2009 at 12:07 PM, Shawn Dwyer wrote:
> Hi,
>
> Is there a way to get MakeSfxCA include everything in my CA project ouput
> directory recursively, maintaining folder structure? It seems to me this
> would be the simplest way of ensuring all nec
Hi,
Is there a way to get MakeSfxCA include everything in my CA project ouput
directory recursively, maintaining folder structure? It seems to me this
would be the simplest way of ensuring all necessary dependencies are there
at runtime.
For a simple example say I have my EULAs for each language
uto
completing the prompt so the user doesn't have to enter anything.
On Tue, Sep 23, 2008 at 1:43 PM, Neil Sleightholm <[EMAIL PROTECTED]>wrote:
> What does the "echo f | xcopy" do? Can't you just use the xcopy?
>
> -Original Message-
> From: Shawn
ist:
>
> When you say that the command works ok from the command line have you
> checked the value of "%errorlevel%" after running it, this is the value
> that windows installer would check to indicate and error. It rings a
> bell that "for" returns a non zero v
Anyone have any ideas why I'm getting an error? Is there a better way to
achieve this?
Thanks,
Shawn
On Fri, Sep 19, 2008 at 1:46 AM, Shawn Dwyer <[EMAIL PROTECTED]>wrote:
> Hi,
> We are preparing to release the next version of our product, which will
> completely remove a
Hi,
We are preparing to release the next version of our product, which will
completely remove all previous versions. However, before uninstalling we
want to back up all the configuration files for the user. To accomplish
this I thought I'd just use cmd.exe and a simple 'for' command to make a
cop
d)
>
> I don't know why 'they' (i.e. secretive installer people who reveal
> pieces of a puzzle slowly and unwillingly, in a blog post or two, now
> and then, maybe never...) have never explained it well enough for
> everybody to understand, but the above works.
>
Hi,
I'm running into what seems to be a common error on the mailing list, but
none of the solutions so far have worked for me.
I have 3 basic test patches:
RTM: installs file1
Patch1: targets rtm, updates launch condition of RTM
Patch2: targets Patch1, updates file1 and installs directory2\file2
I am new to patches and don't know
where to start. How do I go about authoring a patch to remove launch
conditions?
Thanks,
Shawn
On Fri, Aug 8, 2008 at 1:49 PM, Shawn Dwyer <[EMAIL PROTECTED]> wrote:
> Thanks Bob.
>
> Do I need to do anything special so that MSI won't
ginal installer.msi with possibly some new components, or should/can it
just contain the Wix for installing the handful of files I want
replaced/added in the patch?
Thanks again,
Shawn
On Fri, Aug 8, 2008 at 11:48 AM, Bob Arnson <[EMAIL PROTECTED]> wrote:
> Shawn Dwyer wrote:
> > I
Hi,
When we released the RTM of our product (our first experiment with Wix), we
included a launch condition to ensure the program wasn't already installed:
NOT Installed OR REMOVE
I'm now in the process of creating our first patch, but unfortunately when I
uninstall the patch this message is
34 matches
Mail list logo