I'd love to help my career path never took me down the Win32 C++ route. I
did ANSI C on Solaris for awhile in the mid 1990's and then moved onto RAD
languages like PowerBuilder, VB, Delphi and then C#.
At my day job in mid-tier engineering (The Home Depot) my "production" is
all server 2
Check out:
http://robmensching.com/blog/posts/2007/1/4/Doing-a-small-update-or-minor-upgrade-in-MSI-Use
.
That usually finds the problem.
On Sat, Jan 7, 2012 at 9:42 AM, wrote:
> Hi!
>
> I want to add files to my installed program with a minor upgrade.
> I’ve got an msi installer, works fine.
>
Didn't know the User element could find groups. That's probably some
accidental side effect.
Creating groups is another thing that would be nice if someone implemented.
Rollback on it is really, really hard, IIRC.
On Sat, Jan 7, 2012 at 1:26 PM, Christopher Painter wrote:
> FWIW, I'd consider a
FWIW, I'd consider a doco note saying that it can find groups to be good
enough. What I've actually needed even more in the past was the ability
to create groups. The Group element has a note saying that it can't create
groups. I've always resorted to custom actions to do this.
---
It seems that despite being called the util:User element that it was
actually able to locate an ActiveDirectory Group. I just left many of the
attributes blank and told it to not create or update the user.
I don't have the C++ chops to extend these but there is another thread
about creating
IMO, in certain situations, merge modules are not quite dead. Here's my
opinion:
http://blog.iswix.com/2010/09/in-defense-of-merge-modules.html
If you are staying in a WiX world, yes, wixlibs and fragments are a better
solution. If you are using a combination of tools such as WiX and
Insta
Hi!
I want to add files to my installed program with a minor upgrade.
I’ve got an msi installer, works fine.
Now I’ve created an upgrade msi, it only contains 1 file i want to add to the
existing installation,
but it doesn’t work, the upgrade runs without error, but the file is missing.
Thanks
On 05-Jan-12 09:05, Bruce Cran wrote:
> From a verbose install log I see that MainEngineThread is returning
> ERROR_SUCCESS_REBOOT_REQUIRED (3010) - I wonder if WI only checks for
> ERROR_SUCCESS when determining if it should refresh the list, or not
> the other ERROR_SUCCESS_* values? If so, wo
On 06-Jan-12 16:58, Daniel Sniderman wrote:
> These are SQL Server related DLL's - so I can't assume they will be on the
> GAC of the target machine - and I'd like to simply continue to include them
> as files in the MSI - i.e. I don't want to GAC them on the target machine.
You probably don't h
On 05-Jan-12 16:33, Hoover, Jacob wrote:
>Is there a way of informing an end user that a patch is not valid (due
> to a newer patch all ready being applied)?
Check patch applicability. That's what Burn does. The 1.0.2 MSP won't be
applicable to a 1.0.3 product.
--
sig://boB
http://joyofsetu
Merge Modules are a build time concept only. The Windows Installer does not
undersstand them at all. This fact is a large part of the reason Merge
Modules are dying. One key issue is that Merge Modules make things very
difficult to patch (because patching was implemented after Merge Modules
but did
MSI SDK.
On Tue, Jan 3, 2012 at 9:41 AM, shanmukha sainath addepalli <
sainath.addepa...@gmail.com> wrote:
> Thanks for the reply Rob.
>
> I never used Burn. Is there any documentation explaining about creating
> external UI handler?
> can you please provide me any documentation related to that.
That's all that is supported today. It would be fantastic if you wanted to
contribute the code to do more.
On Tue, Jan 3, 2012 at 2:18 PM, Christopher Painter wrote:
> I work in an enterprise environment and I have a request to add an Active
> Directory Group to a Local Group. Problem is I see t
The wixstdba will automatically search for a .wxl file of the system
language (i.e. look in 1033 directory for english and 1041 for german and
1044 for japanese, or are those last two switched?).
Failing to find a matching .wxl file will cause wixstdba to fall back to a
.wxl in the root.
There ar
1. If a package cannot be found, you will get a source resolution callback.
2. At the very least Burn does a SHA1 hash of the files to verify they are
correct before installing them for security reasons. If you digitally sign
your payloads, Burn will verify the signatures instead of hashing (which
I think there is a bug about Cancel during progress in the wixstdba failing
already. Yes, it needs to be fixed.
On Fri, Jan 6, 2012 at 8:59 AM, Michael_A wrote:
> I'm re-posting this as I never got an answer.
>
> Canceling Installing burn generated install results in the following. If
> additio
Burn supports that. WiX v3.6 does this exact thing for NETFX 4.
On Thu, Jan 5, 2012 at 6:22 PM, Bruce Gombrelli (Experis) <
v-bru...@microsoft.com> wrote:
> I'd like to check and install Framework 4.0 from a **LINK** rather than
> having to include the entire framework 4.1 (and Windows installer
17 matches
Mail list logo
