> I appreciate if anyone can tell me why some times some files are not
> installed during Major Upgrade.
Perhaps you could try isolating the problem, by taking each version of the
product that you've released so far and installing, then uninstalling on a
"clean" machine? I like to use virtual
Can someone help me determine if this is a bug or not? I have a .wxs that I
authored, and when I link the .wixobj with light.exe, it emits a warning when I
have my Compressed attribute on the Package element set to "no". If I set it
to "yes" (only thing I'm changing), it goes away. Here's the
Sorry, I just pasted my response into the wrong window :)
On Fri, Apr 24, 2009 at 7:25 PM, Karthik Krishnan wrote:
> It is buried/implied in the documentation, but there is a simpler way. Just
> change the sequencing of the windows. I haven't done this for Mondo, but
> here it is for FeatureTree
It is buried/implied in the documentation, but there is a simpler way. Just
change the sequencing of the windows. I haven't done this for Mondo, but
here it is for FeatureTree :
1
NOT Installed
You'll still need to peek at the source. You are essentially overriding the
existing Dialog orders.
I'd like to post my code in the Upgrade part. This is our "Major Upgrade" code:
Basically:
1. We need "Major Upgrade" because some times we may include one dll is the
build, but decide remove it in the later build. So we'd like to ma
Wow! So the only way how to get rid off that damned FileInUse dialog is
to create complete own version of WixUI template like
"WixUI_MondoNoLicense"? Jesus, it's like hunting mice with an a-bomb!
Seriously, isn't there any other easier way how to accomplish this
simple task? Is there any way ho
Hey James,
Have you looked into the WiX COM+ public custom actions at all?
Thanks,
Brian Rogers
"Intelligence removes complexity." - Me
http://icumove.spaces.live.com
On Fri, Apr 24, 2009 at 12:41 PM, MacDiarmid, James D <
james.macdiar...@eds.com> wrote:
>
> Right now I have to go through DC
Hey Sudripta,
A wxl file doesn't get "processed" for localization. You need to make a wxl
file per language you want to localize and pass that into light to output
the MSI with the correct localization. This means that any text you put
there for fonts will be what gets put in the MSI.
en-US.wxl
n
Hi Rob,
It's similar to a mailing list, however one difference is that it would
be forum-based organized by sections and categories. I could also have
an section where "HOW-TO" articles written by various developers that
use Wix could post their contributions to the site. The forum could have
va
In my experience, the more categories there are for discussion, the less
vibrant a community is. Fewer questions are be answered because not everyone
follows all of the forums and because, in many cases, developers prefer mailing
lists to web interaction. On a couple of the forums I've been in
Jan this is a good starting point:
http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html
Dizzy Monkey design has a little ok guid.
http://www.dizzymonkeydesign.com/blog/misc/adding-and-customizing-dlgs-in-wix-3/
You can also use the guide here by Gábor DEÁK JAHN :
http://www.tram
That sounds like something missing in ServiceControl - that's where you
explicitly say you want the service deleted with the Remove attribute.
Phil Wilson
-Original Message-
From: Mark Sinnathamby [mailto:mr...@eurocenter.lk]
Sent: Friday, April 24, 2009 1:01 AM
To: wix-users@lists.so
Thanks for the link. But i've got one more question. I,ve never needed
to customize UI of my installer, so i'd like to know how to change
attributes (hidden, modeless) of already defined from my
installer code?... Or do i have to browse original Wix sources and make
these changes where the Fil
I think I like the idea of forums.
Categories like
Announcements
Bootstrappers
HOW-TO Articles
Wix 2.0 Issues
Wix 3.0 Issues
Heat Issues
Votive Issues
And many more..
This will make it easier for users to go to specific forum to find their
problem related answers rather than one main list for ev
Any of those "merge tools that are available from independent software vendors"
are actually just wrappers around mergemod.dll. WiX itself uses mergemod.dll to
merge MSMs.
Sure in theory it should be possible to duplicate the logic of mergemod.dll,
because everything it does can be done with MS
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
Right now I have to go through DCOMCNFG to set service parameters. How
would do this using Wix?
Thanks,
Jim
--
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensign option that enable
I'm trying to get feature state migration working on a major upgrade that I
invoke by running the MSI.
I think I have the appropriate entries in my WiX project.
The MSI that is generated seems to have the appropriate entries for;
InstallUISequence
1000
Hey Ron,
Have you tried setting the custom action to immediate. It will not be able
to launch the window as deferred. You might also want to look at using
ShellExecute as well.
http://msdn.microsoft.com/en-us/library/bb774148(VS.85).aspx
Thanks,
Brian Rogers
"Intelligence removes complexity." -
Hey Henk,
Although not specifically stated, yes Component GUIDs need to remain stable.
A patch is a difference between two MSIs, so that would mean most everything
that is unique to a component must stay the same. Someone else on the forum
might be able to give you a more detailed answer.
http://
I am not sure I understand what you are asking, could you explain?
Neil
-Original Message-
From: Roy Abou Assaly [mailto:royass...@gmail.com]
Sent: 24 April 2009 16:02
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Heat 3.0.4923 vs 3.0.5217 vb6 dll output
Can anyone run l
And apparently no attachments. I'll paste the contents :)
Content of original post with attachments:
Sure thing. It was a long day so sorry for the lack of detail. Attached you'll
find the wxs for the installs and the patches, and the batch files I use. I
pass the version numbers into the bat
Sure thing. It was a long day so sorry for the lack of detail. Attached you'll
find the wxs for the installs and the patches, and the batch files I use. I
pass the version numbers into the batch files which in turn pass them along to
WiX. I create the installs with buildInstall 0.3.0.0 for exa
Can anyone run light 3.0.5217 on this to confirm this? The merge module
simple won't build and that Interface element is indeed needed.
Thanks again.
Roy Abou Assaly wrote:
>
> Oh, and one more:
>
> 00020420---C000-0046
>
> After that, I was able to build my merge module and
I've been struggling with this issue for some weeks now, and I've continued
to back burner it, but can't do that anymore.
I've built a WixExtension, and use it in several installers. But I keep
running into problems with Votive / MSBuild loading the extension I've
built. I'm guessing I'm having
Yes, Edwin you are the man. This works perferct, now. Thanks for your help
I need to read up on msbuild. I just started working with it when I began
with automating our installer with wix. Good stuff when you know what you
are doing.
Brian
2009/4/23 Castro, Edwin (Hillsboro)
> Correction:
>
If Mergemod is such a irreplaceable black box, why does the MSDN topics state
that the best practice is:
"Merge modules must be merged into an installation package by using a merge
tool. The best practice is to obtain a freely distributed merge tool, or
purchase one of the merge tools that ar
I've created patches which do exactly what you're trying to do but from
your description I can't pinpoint where you're going wrong.
If you could post the .wxs file you're using to create your .pcp file, I
or someone else on the list should be able to help point you in the
right direction.
Cheers,
I suggest you use a more 'unique' name than "help.chm" though.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integr
Hi,
I checked the log file as to why the database and the windows service were not
getting uninstalled and found these two lines in the log file:
MSI (s) (2C:B4) [14:39:46:741]: Disallowing uninstallation of component:
{F8A6AD08-15F7-4BEC-AC9E-A1091F2B0D41} since another client exists
MSI (s) (
No, something else is probably wrong. A verbose log file will probably
show a Component not going to Absent (and why).
Mark Sinnathamby wrote:
> Hi,
> I have created an msi installation pack with Wix, using my own custom UI
> library. I have added the maintenance dialogs in this library as well.
Hi,
I have created an msi installation pack with Wix, using my own custom UI
library. I have added the maintenance dialogs in this library as well.
When I install the product, Which consists of a database a windows service and
some executables, everything gets installed without any problems.
When
I followed your suggestions and used "MergeMod.dll" via COM interop in my
little repackaging tool. This works perfectly.
After the successful merge I still have to do a couple of steps to patch the
resulting msi:
1. Extract the merge module's cab file
2. Insert the cab file into the "_Streams"
Hi dkijc,
I think you can do this, but a little unclear about the storing of icons
somewhere else? Are you actually installing a program also or just icons?
For storing the icons part you have a question in the installer I assume and
it asks to download latest icons or choose a directory? If user
34 matches
Mail list logo
