Conveniently timed blog post announcing a tool that sounds like it
might show the dependencies as MSBuild sees them:
http://blogs.msdn.com/b/vcblog/archive/2014/05/29/solution-dependency-viewer-extension.aspx
On Thu, May 29, 2014 at 8:20 AM, John Cooper wrote:
> Yes, but it's very messy and you
On Tue, Sep 18, 2012 at 8:17 PM, Bob Arnson wrote:
> On 18-Sep-12 16:24, Benjamin Kaduk wrote:
>> I'm really confused by this behavior, and don't know where to look
>> further.
> The verbose upgrade log. It will tell you why MSI decided to leave a
> file behind.
If it decided to do so. It could a
Hi Simon,
You can get halfway there; you can request for a shortcut not to be
highlighted by specifying the following shortcut property.
System.AppUserModel.ExcludeFromShowInNewInstall
http://msdn.microsoft.com/en-us/library/windows/desktop/dd391568.aspx
http://helpnet.installshield.com/installsh
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
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
ooks like redefining
> MyApp.Binaries to be the INSTALLDIR value. Am I assuming correct?
>
>
> Thanks,
> MeCoco
>
> On 3/8/2011 3:07 PM, Michael Urman wrote:
>> Directories are only automatically preserved when there is a component
>> that installs to it. So make sure at
Directories are only automatically preserved when there is a component
that installs to it. So make sure at least one component installs to
INSTALLDIR.
On Tue, Mar 8, 2011 at 03:31, MeCoco wrote:
> Hi all,
>
> I tried to create a small sample to reproduce the problem I'm having,
> and after a lot
s they
> need to also be in InstallExecuteSequence.
>
> I've currently got them in both sequences, and am using the UILevel
> property to prevent them from running twice. Is there a cleaner or more
> standard way to do this?
Perhaps set CustomAction
Per the documenation for DoAction
http://msdn.microsoft.com/en-us/library/aa368322(VS.85).aspx as well
as a comment on the MsiProcessMessage MSDN page, this won't work. I
think the recommended way would be to create and show a dialog with a
SpawnDialog control event instead.
On Tue, Jan 25, 2011 a
Only deferred, rollback, and commit actions use CustomActionData set
from the matching property's value. Immediate actions (all UI actions
are immediate) have full access to properties so this is unnecessary
and unused.
On Mon, Jan 24, 2011 at 13:49, Castro, Edwin G. (Hillsboro)
wrote:
> I'm tryi
Just make sure you install a component to that directory - it doesn't
even need to contain any files. Then Windows Installer will remember
it for you, loading it back into the DirProperty.
On Fri, Jan 21, 2011 at 06:32, Umeshj wrote:
>
> How do we access it?
>
> Specifically, I would like to show
It would be nice if the documentation stated that outright. I
understand the normal UAC case made Privileged hard to set as
documented, but as written this behavior smells more like a Windows
Installer bug.
On Thu, Jan 20, 2011 at 22:43, Rob Mensching wrote:
> Windows Installer always sets Privil
The underlying storage for the .msi database cannot handle sizes over
2GB, so your assessment seems correct. Unfortunately the only
workaround I'm aware of is to move the large data outside the .msi,
necessitating external files (either .cab or raw source files).
On Wed, Jan 12, 2011 at 15:47, Tim
For what little it's worth, InstallShield 11 did not support for
Vista, much less the version of IIS included with Vista, because its
predates Vista. If that's the only blocking factor, you may want to
consider a version of InstallShield that shipped after 2005. If the
other factors are more releva
asier than getting
> rollback correct in all the cases it is required. The RemoveFoldersEx custom
> action does the same sort of work in the
> http://wix-contrib.codeplex.comproject.
>
> On Mon, Nov 29, 2010 at 7:02 AM, Michael Urman wrote:
>
>> The trick here is that i
x27;t consider this being a so weird task: just deleting, when
> uninstalling, some files your app created and needs. I would have
> expected a standard way of doing this, and not through batch or other
> external custom actions as they can't be controlled during rollbacks.
>
Good job isolating it, but it's a problem understanding how component
conditions work. They only serve to gate when a component is
installed. With the transitive bit set, their going false can also
cause them to be uninstalled in a minor upgrade or other maintenance
scenario. However their being fa
While extracting it from the temp folder, or the cached location
mentioned in a log file will work, why not just perform an
administrative install? This way you can drop the .msi file wherever
you'd like.
http://helpnet.flexerasoftware.com/robo/projects/installshield12helplib/IHelpSetup_EXECmdLine
t a command-line argument that is passed in by the custom
action. Fixing either will likely resolve your behavior, but fixing
both feels cleaner to me.
--
Michael Urman
On Thu, Jul 15, 2010 at 04:45, Chirag Goradia wrote:
> Hi everyone,
>
> We are running custom EXEs ( .NET 2.0 cons
If you target MSI 4.0 or later, you might see this reflected in the
MsiSystemRebootPending property. The MSDN page for this property
suggests authoring it into a launch condition.
On Thu, Jul 8, 2010 at 10:08, Samuel Larsen wrote:
> Hmmm. That was a good idea, but no, it looks like the
> Pendi
nding is MSIINSTALLPERUSER support
relies on capabilities of Windows 7, so a backport of MSI 5.0 or later
would not expose MSIINSTALLPERUSER's behavior on earlier operating
systems.
Michael
--
Michael Urman
--
Do
On Wed, Mar 10, 2010 at 10:34, Rob Hamflett wrote:
> On 10/03/2010 16:05, Kristoffer Danielsson wrote:
>> If a computer installation is selected, the "Install" button gets the shield
>> icon. Otherwise, the icon goes away. (Important!)
>
> You could possibly have 2 buttons, one with the shield an
These sound like odd requirements to me. But that said, I'd use the
action states of the components to figure this out. If you want to
consider it from the first-installed product perspective, it will have
to poke in and know at least one of the merge module's components (or
perhaps create a config
The biggest problem with installing dependencies from your UI sequence
is that they do not get called if your MSI is run with silent or basic
UI. And then, since your MSI can't show any UI, it's harder for it to
explain the failure. One hopes that if a person runs the MSI silently,
they know how to
endedType column
was added (instead of a widened Type column) to allow for its use in a
patch.
--
Michael Urman
--
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and A
If you want the ability to easily force an installation later, I would
suggest either transforms, or adding a clause like "or
SKIPNETFRAMEWORKCHECK" and documenting how your enterprise customers
can create a transform or use the property to continue the install
when the checks fail. Heck, put a sim
documentation on MsiFormatRecord) at
http://msdn.microsoft.com/en-us/library/aa368609(VS.85).aspx
--
Michael Urman
--
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option tha
uctCode]
>
> is written on Windows Server 2003 machines, but not on Windows Server
> 2008 machines. :S
>
> Amy
--
Michael Urman
--
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to
og could launch custom actions that exceed
these limitations, but that would require a user to click on them
first.
--
Michael Urman
--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanni
On Wed, May 6, 2009 at 19:39, Bob Arnson wrote:
>
> It's the shell that runs uninstalls with basic UI. Even less likely to
> change.
>
Truly. However Windows Installer could theoretically add support for
customizing the basic UI experience without requiring the shell to
cha
On Sun, Mar 29, 2009 at 23:32, wrote:
> Is there a primary on how to author conditions. I've seen some examples
> of conditions, but don't understand the syntax and overall concepts.
Please see the MSDN or SDK documentation for "Conditional Statement Syntax
>
> What's the difference between writing a value and leave it alone? The
> end result is still the same, no?
If you end after install. After uninstall the two sound rather
different to me. Handling the leave-it-untouched approach could get
messy onc
e expected to
see a compilation error if this is the source of your problem. Are you
compiling UNICODE or MBCS?
--
Michael Urman
--
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of
hp?banner_id=100&url=/
> ___________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
Michael Urman
-
This SF.Net
> if the setup is run under any other OS. How can I do that?
--
Michael Urman
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin
that, perhaps someone else
has a better idea. I suspect it's not possible.
--
Michael Urman
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based application
, and are a fine practice when you need that additional control in
order to avoid confusing your users.
No bazookas here; perhaps hand drill vs. drill press? Now, if you
implement a coded custom action, which sets a property to result in a
Type 19 triggering, that could b
are still logged. It may be a hack, but calling MsiSetProperty(hMSI,
_T("LOGME"), _T("...")) is effective.
--
Michael Urman
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challe
38 matches
Mail list logo
