The URL in the original email. At the pinned part, it talked about the
deployment projects going away, and an installsheild edition being given away
for free
On Feb 4, 2012, at 1:22 AM, "Rob Mensching" wrote:
> Where is there?
>
> On Fri, Feb 3, 2012 at 12:12 PM, John Bergman <
> john.berg
How did you mark that your MSIs are per-machine? The best thing to use is
the Package/@InstallScope attribute. Burn should automatically prompt for
elevation if it determines your MSIs are per-machine.
On Fri, Feb 3, 2012 at 12:21 AM, Peter Hull wrote:
>
> I've made an installer for 32- and 64-
Where is there?
On Fri, Feb 3, 2012 at 12:12 PM, John Bergman <
john.berg...@xpedienttechnologies.com> wrote:
> Why isn't WiX mentioned there? Seems odd when we had all heard at some
> point that WiX was going to be included with Visual Studio...
>
> -Original Message-
> From: Wilson, Ph
Nosir, now I do, however. So it might be a case of ill timing we would
consider changing up to WiX anyway. Thanks for the heads up.
On Fri, Feb 3, 2012 at 12:06 PM, Wilson, Phil wrote:
> You know that MSI setup projects in Visual Studio are disappearing anyway,
> right? See retirement note at the
Why isn't WiX mentioned there? Seems odd when we had all heard at some point
that WiX was going to be included with Visual Studio...
-Original Message-
From: Wilson, Phil [mailto:phil.wil...@invensys.com]
Sent: Friday, February 03, 2012 12:06 PM
To: General discussion for Windows Instal
You know that MSI setup projects in Visual Studio are disappearing anyway,
right? See retirement note at the top of these forums:
http://social.msdn.microsoft.com/Forums/en-US/winformssetup/threads
Phil W
-Original Message-
From: Michael Powell [mailto:mwpowel...@gmail.com]
Sent: Th
I can agree that relying on conditions like Not Installed during custom
actions does not scale. Component Action states are a much better
indicator of when to do something.
My only regret is that MSI never implemented a pattern for hooking into the
resilency process. It would have been nice f
Just to confirm, I have finally got my Code-Signing cert and, with everything
signed it still triggers Trend (on Windows XP, seems OK on Windows 7). I'm
going to make a minimal installer and send it off to our IT department,
hopefully they can ask Trend to investigate.
Has anyone else made an
I've made an installer for 32- and 64-bit windows with separate MSIs, bundled
with the standard BA (WixStandardBootstrapperApplication.RtfLicense). Both MSIs
need admin privileges and are marked per-machine. If I run the installer as a
non-admin user, the error message that the setup program gi
9 matches
Mail list logo
