Fix the bug?
On Tue, Mar 22, 2011 at 3:04 PM, Wang, Miaohsi wrote:
> Hi Rob,
>
> No, I did not find it resolved. I'm just having the same problem. Is there
> an workaround to extract COM data from a 64-bit COM object?
>
> Thanks a lot,
> Miaohsi
>
> -Original Message-
> From: Rob Menschin
Don't think that's supported. You can try ARPPRODUCTICON but I don't think
that'll do it.
On Tue, Mar 22, 2011 at 1:49 PM, Margo Frary wrote:
> Hi there,
>
> I want a "custom" icon to get displayed in the title bar when my msi is
> executed.
>
> (Thus, for example, in the image attached, I want
IIRC, it's not candle, it's MSBuild. That makes it harder.
On Sun, Mar 20, 2011 at 3:40 PM, Rennie Petersen wrote:
> Hi Rob,
>
> Thank you very much for your explanation.
>
> I have an alternative suggestion as to how this "feature" should be
> implemented, as I think it is unfortunate that the
Hi Rob,
No, I did not find it resolved. I'm just having the same problem. Is there an
workaround to extract COM data from a 64-bit COM object?
Thanks a lot,
Miaohsi
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Saturday, March 19, 2011 11:07 AM
To: General
Hi there,
I want a "custom" icon to get displayed in the title bar when my msi is
executed.
(Thus, for example, in the image attached, I want to replace the standard MSI
icon in the top left corner with my company specific icon)
I do not have the option to create an exe, only have the Wix.
Thanks for sharing your experience, Chris! I still learn the things around
Windows Installer, and I really appreciate you point me on the
inconsistencies in my answers!
Then it seems that heat.exe does miss the switch to generate 1:n fragments
(to cover any scenario)...
-- Yan
On Tue, Mar 22, 20
Uninstalling and reinstalling, and doing this a few times, with a reboot
sprinkled in, the MajorUpgrade element parsed and compiled, and the
thing worked. I don't know what my issue was, but I don't have it
anymore. Thanks.
-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Michael, can you provide those errors? I'm thinking it will help diagnose
the issue.
-
Thanks!
~Pat
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/VS2010-Wix-and-MSBUILD-tp6192992p6197557.html
Sent from the wix-users mailing list archive at Nab
Yup, the details do change:
http://msdn.microsoft.com/en-us/library/dd391568(v=vs.85).aspx
On Tue, Mar 22, 2011 at 12:20, Wilson, Phil wrote:
> Not according to Raymond. It's just Windows trying to be helpful. It started
> in XP, but of course details often change.
>
> http://blogs.msdn.com/b/o
Not according to Raymond. It's just Windows trying to be helpful. It started in
XP, but of course details often change.
http://blogs.msdn.com/b/oldnewthing/archive/2005/11/24/496690.aspx
Phil Wilson
-Original Message-
From: Michael Tissington [mailto:michael_tissing...@ciqual.com]
Take a look at the built MSI in Orca and rule out incorrectly authored
table data. Then log the installer and see if it gives you any clues.
---
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
Would the version of the MSI engine you are targeting play a part in what
happens. If you are not targeting the 5.0 version of the engine, this may not
function as expected.
Mat Skildum
-Original Message-
From: Dick Van den Brink [mailto:d_vandenbr...@live.com]
Sent: Tuesday, March 22
That's weird, according to
this: http://kb.flexerasoftware.com/doc/Helpnet/installshield16helplib_sp1/SettingShellShtctProp.htm and http://social.msdn.microsoft.com/Forums/en-US/winformssetup/thread/d8feae89-d5cd-44be-b21c-022a3c9a8a70 it
should work.
> Fr
Well I can confirm it does not cause an error on Windows XP
However it does not appear to work for me on Windows 7
-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com]
Sent: 22 March 2011 14:34
To: Gener
Great, it does indeed seem to work now!
Thanks again.
Fred
Le 22/03/2011 14:04, Pally Sandher a écrit :
> dblock of dotnetinstaller fame created a bunch of standard properties in a
> WiX include which you may find useful for this. See
> http://code.dblock.org/ShowPost.aspx?id=101
>
> Palbinder S
Yes, but the original question applied to Windows 7 which is MSI 5.0.
---
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
- Original Message
From: Michael Tissington
To: General
I don't have a Windows 7 pc where i can test this now, but i just tested this
on Windows XP with Windows ® Installer. V 4.5.6001.22159 and no errors occured.
I hope to test this setup on a Windows 7 pc (with Windows Installer 5) tomorrow
to see if it doesnt create a recent programs shortcut.
--
Where to copy companion files(path of companion files) for File
element's CompanionFiles.
-Original Message-
From: Michael Urman [mailto:mur...@gmail.com]
Sent: Tuesday, March 22, 2011 7:26 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Shortcuts and
Hmm, WiX supports this but isn't this only supported with misexec 5.0 ?
-Original Message-
From: Michael Urman [mailto:mur...@gmail.com]
Sent: 22 March 2011 13:56
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Shortcuts and Recent Programs list
Or add
Or add a ShortcutProperty element with
@Key='System.AppUserModel.ExcludeFromShowInNewInstall' and @Value='1'
to your Shortcut element, assuming you're using a version of WiX that
supports this element.
On Tue, Mar 22, 2011 at 08:02, Pally Sandher wrote:
> Don't install on Windows 7?
>
> Palbinder
Yan,
This comes up from time to time and I want to stress that there is no
universal
best practice that states every file should be the keyfile of it's own
component. 1:1 is the most common situation that you would want to do this but
it is not universally true. The MSI SDK talks about this
dblock of dotnetinstaller fame created a bunch of standard properties in a WiX
include which you may find useful for this. See
http://code.dblock.org/ShowPost.aspx?id=101
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**De
Don't install on Windows 7?
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456
Registered Office - Helix
In my install I'm creating a number of shortcuts. They are also
automatically appearing in the Start Menu list of recently opened programs.
Is there a way to prevent them appearing on this list?
--
Enable your software f
Hi folks,
I'm trying to implement a very (at least, I guess it is...) simple
condition...
I would like a Component to be installed ONLY on an initial installation
(and not on Major Upgrade or Repair)
The code looks like this:
snip
NOT OLDPRODUCT
My problem is that the Co
You can also use WiXEdit (http://sourceforge.net/projects/wixedit/) to do that
but you'll need to use version 0.7.2.3 or older as they changed it to work as
per heat.exe from 0.7.3 onwards.
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://
Thanks Rob!
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Samstag, 19. März 2011 19:23
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Custom Wix 3.5 PreprocessorExtension anddebugmessages
You create a MessageEventArgs an
heat.exe doesn't support this out of the box - it was designed to encourage
the best practice, which is "one file - one component". However, you can
apply an XSL transform to the heat output and change it the way you need.
You can also take a look at the Paraffin tool (
http://www.wintellect.com/CS
28 matches
Mail list logo
