ackages.
Thanks,
Mike
--
Meet PCI DSS 3.0 Compliance Requirement
in
our managed BootStrapper. I'm not clear what happens during Uninstall if the
*.execpkg files no longer reside in the Application Folder.
Could someone recommend the best approach along with some code samples?
ions and I end up with two installations.
Any suggestions would be appreciated.
Thanks,
Mike
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Prevent-old-InstallShield-version-from-installing-over-WiX-tp7596218.html
Sent from the wix-users ma
, ErrorEventArgs e){
MessageBox.Show(Application.Current.MainWindow, e.ErrorMessage, "WiX
Toolset", MessageBoxButton.OK, MessageBoxImage.Error);}}
Th
--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Rea
I was able to add the version number via the binding variable, but I am
unable to find variables for the GUIDS or URL. Is it possible to pass those
variables to the bundle?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-read-an-MSI-s-Produc
o the main .exe's auto-update mechanism?
Thanks,
Mike
--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph da
http://www.bbc.co.uk/
This e-mail (and any attachments) is confidential and may contain personal
views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor
thout having to "run as
administrator"? Do I need to make a call to Engine.Elevate? If so, where is
the correct place to make this call at? I've tried a number of places in my
code. I see the UAC warning dialog but it doesn't change how the MSI is
installed.
Thanks
XML toolset.
Subject: Re: [WiX-users] prompt for administrator account during major upgrade
[P]
Classification: Public
How are you asking the user to give the administrator account then?
-Original Message-
From: Mike Myers [mailto:mike.my...@naucountry.com]
Sent: July-24-13 11:43 AM
To
administrator account during major upgrade
[P]
Classification: Public
Is this a custom action you are using?
Anyway you could use something like:
NOT
WIX_UPGRADE_DETECTED
-Original Message-
From: Mike Myers [mailto:mike.my...@naucountry.com]
Sent: July-24-13 11:02 AM
To: wix-users
from being
prompted during the upgrade?
Thanks
-Mike
This electronic message from NAU Country Insurance Company and any attachment
to it is intended exclusively for the individual or entity to which it is
addressed. It may contain information that is privileged, confidential
ne’
> and ‘Administrators’ may be entered in English and are mapped to
> well-known SIDs.” Or there will be localization problems when
> installed in other languages?
>
> Do you have some recommendations?
>
> Thanks a lot for your time.
>
>
>
> 2013/5/22 BGINFO4X :
>
I agree with John - please avoid setting the arpsystemcomponent. It's
extremely annoying to install something and be unable to uninstall it from
the UI, and is really only meant for system components that make no sense
to uninstall.
I suggest you author a burn bundle to hide all the individual MSI
When you say "another package", I assume you mean another MSI?
Make sure the component GUIDs in your MSI match the component GUIDs in the
other MSI so you don't break the component rules, and then for any of the
files that have file versions (such as .exe or .dll files), make sure your
version num
Chain all the MSI files you want to install with a burn bundle. It will by
default not show each MSI it installs in add/remove programs (ARP), instead
you will still see a single entry in ARP for the bundle itself.
Note if you do want some of your MSI's to show up individually in ARP, you
can make
d version to be uninstalled as part of installing the
new version.
Or you might want to explore "Minor Upgrades" which are slightly lighter
weight:
http://msdn.microsoft.com/en-us/library/windows/desktop/aa370037(v=vs.85).aspx
.
On Tue, May 21, 2013 at 9:34 AM, BGINFO4X wrote:
You should be able to. Create the shortcut in your own authoring file. To
point to the file in the generated authoring, see the "Target" attribute of
the shortcut element in wix.chm.
On Tue, May 21, 2013 at 4:37 AM, BGINFO4X wrote:
> > You should change it to this:
> >
> >
> >
I don't know the direct answer to your question, but taking a step back,
have you considered any alternatives instead of adding a custom action?
Custom actions are notoriously difficult to write correctly, and very, very
easy to get wrong. A custom action that invokes an external process (such
as j
Your problem is that "basedir" isn't a child of "INSTALLDIR", it's a child
of "ProgramFilesFolder". Here is your current code:
You should change it to this:
Also, you should pass in "-srd" on the heat commandline (suggestion #3
above), or e
The problem you're running into is that the generated components are by
default generated under a directory under "TARGETDIR", not "INSTALLDIR". To
override this:
1) Add (for example) "-dr foo" to your heat commandline to generate them
under a directory of ID "foo"
2) In your main authoring file,
on to make this work correct and I have no idea what it
is. I'm sure someone out there has solved this issue and I would really
appreciate the help.
Thanks
-Mike
This electronic message from NAU Country Insurance Company and any attachment
to it is intended exclusively for the indi
uld I be better off using something
else? It feels like I really should be using Burn to provide the install UI,
not my MSI. Alternatively, maybe I'm thinking about how my install should work
incorrectly.
Thanks in advance
-Mike
This electronic message from NAU Country I
x27;.F:\Users\mtod\My
Documents\My Development Projects\FMIWinService\FMIWIXSetup\Product.wxs
27 1FMIWIXSetup
Thanks
Mike
http://schemas.microsoft.com/wix/2006/wi";
xmlns:VSExtension="http://sc
d. I tried using the
log option when I run my installer, but I don't see anything in the log
relating to running "devenv /setup".
My installer installs for in each of the Visual Studio versions that are on the
machine, e.g., both VS2010 and VS2012.
Any advice would be grea
It sounds like you're missing the VS 2010 redistributables on the XP
system.
Mike Schlueter
Software Engineer
Phoenix Contact USA
Ann Arbor, MI
(734)205-5410
mschlue...@phoenixcon.com
From: Jelani Jackson
To: "General discussion for Windows Installer XML toolset."
,
Thanks for the tips. I got it working with the system variable, and I
will look into modifying the .wixproj.
Mike Schlueter
Software Engineer
Phoenix Contact USA
Ann Arbor, MI
(734)205-5410
mschlue...@phoenixcon.com
From: Tobias S
To: "General discussion for Windows Installe
there a variable or a way to access the WiX path from within Visual
Studio?
Regards,
Mike Schlueter
Software Engineer
Phoenix Contact USA
Ann Arbor, MI
(734)205-5410
mschlue...@phoenixcon.com
--
Live Security Vi
As of WiX 3.6.2719.0, the standard MSU exit codes are not being handled
properly by MsuPackage. In particular, the burn bootstrapper does not
notice when an MSU indicates a reboot is required and instead just moves on
to the next package.
--
View this message in context:
http://windows-installe
llation option that
> modifies the product code.
>
> -Original Message-
> From: Mike Rerick [mailto:mrer...@iwsinc.com]
> Sent: 13 January 2012 15:38
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Writing JDK version verification cod
The app being installed is a Java app. Can't run it without Java being
installed. If Java isn't installed, the installer needs to quit with an
error msg to the user.
On Fri, Jan 13, 2012 at 7:28 AM, Peter Shirtcliffe wrote:
> Why not check it when the application starts up ? It'll be easier to c
Here is something I had put together quite a while ago that works for me.
You should be able to modify it to do what you need. You could change the
CustomAction to SetProperty elements.
JAVA_JRE_HOME
SetJavaJdkJreHomeVBS.wxi:
http://schemas.mic
Use a custom action to set the Property.
In the InstallExecuteSequence, call the custom action:
Set the Before or After attribute to wherever you want the value set.
Mike
On Mon, Jan 9, 2012 at 1:07 PM, Bourne, Kevin <
kevin.bou...@chasepaymentech.com> wrote:
> Says "Co
helps
Michael
-Original Message-
From: Mike Menaker [mailto:mi...@voicebox.com]
Sent: Tuesday, 12 April 2011 9:47 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] SqlDatabase install optional and SqlString
execute
The cancel will apply to only the DB creat
install optional and SqlString
execute
Mike,
SqlDatabase has an option ConfirmOverwrite, if set to yes the installer
will prompt if it finds a database already created, and allows you to
cancel or continue. Using this option the installer only needs to deal
with option 1 and you get 2 for free
ld it
be execute after the SqlDatabase is created?
Also is wix smart enough to only run SqlString elements after a
SqlDatabase is created?
Thanks,
Mike
--
Xperia(TM) PLAY
It's a major breakthrough. An authen
Re-looking at your code, I noticed that some of the sql:sqlString statements
don't have a sqlDb attribute on them. Not sure what the consequences are of
leaving it off - I always put one on all of my sqlScript statements.
Mike
*Mike Rerick*
*Sr. Software Engineer*
[image: G
Kim,
I looked at your code. Seems to be OK.
Looking at my sql scripts, I have a GO command after each group of
statements. Have you tried adding GO at the end of each of your SQL
commands?
Mike
*Mike Rerick*
*Sr. Software Engineer*
[image: Google Docs] <http://www.iwsinc.
. . .
Hope this helps.
*Mike Rerick*
*Sr. Software Engineer*
[image: Google Docs] <http://www.iwsinc.com>*ImageWare Systems, Inc.*
9200 S.E. Sunnybrook Blvd., Suite 170
Clackamas, OR 97015
Office: (503) 353-8068 Fax: (
On 3/11/2011 9:27 AM, Kevin Burton wrote:
> Along these same lines I tried building the CA project setting the target as
> x64 just to see if this made a difference. I did get a different error
> message but it still didn't work:
>
> MSI (s) (60:80) [08:07:23:231]: Created Custom Action Server wi
hose components are only included in the Visual Studio bundled SDKs.
Who knows :\
If you have Visual Studio, you'll need to use the components from the
SDK that shipped with that (7.0a, for example).
--Mike
--
The
getting this warning. I'm
assuming that the ICE validation routines run by WiX aren't updated for
Windows Installer 4.5; is there a way to get them updated?
--Mike
--
The ultimate all-in-one performance toolkit
\DevExpress.DLL"?>
> 14.5\Bin\Dotnet\v20"?>
Thank you! This does, indeed, work exactly as we need it to.
--Mike
--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying e
ers
should be used to find these components?
--Mike
--
Centralized Desktop Delivery: Dell and VMware Reference Architecture
Simplifying enterprise desktop deployment and management using
Dell EqualLogic storage and VMwa
Thank you, that confirms my current understanding :)
I hadn't released that cultures were just for fall-backs and couldn't
understand why light accepted multiple wxls of different locales when the
MSI can only hold 1.
On 18 August 2010 14:53, Mike Carlisle wrote:
> Thank you, tha
the original WIXUI_Mondo screen, so that I can modify it into
the layout used by SampleCustomUI7.wxs whilst preserving the existing
localizable strings.
If I'm missing something please shout.
Thanks,
Mike
--
This S
Thank you - the first part of that makes perfect sense.
The second part is still a little ambiguous to me. When you say the cultures
flag decides which .wxl files are processed this implies that the MSI can
contain more than one locale, ( as the cultures flag takes a list of
cultures). I didn't th
olset and the SDK you have all the necessary
> tools to create whatever you engineer.
>
> -Original Message-
> From: Mike Carlisle [mailto:moik...@hotmail.com]
> Sent: Tuesday, August 17, 2010 4:09 AM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users
What is the purpose if not
to produce a single MSI with multi-language support? Am I missing something?
Thanks,
Mike
--
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry
If it works using "/qb" compare the InstallUISequence table versus the
InstallExecuteSequence table. There may be a CA that runs in the
InstallUISequence that needs to the InstallExecuteSequence.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Unabl
xist when something needed
it.
That solution probably doesn't fit your situation, so another solution is if
you don't want the app pool to be removed on uninstall, put it in its own
component and make the component "Permanent".
Thanks,
Mike Carlson
-Original Message
figuration file. The two Web.config files are both for IIS7. I'll check.
--
John M. Cooper
Volt at Microsoft
-Original Message-
From: Mike Carlson (DEV DIV) [mailto:mica...@microsoft.com]
Sent: Thursday, May 06, 2010 2:15 PM
To: General discussion for Windows Installer XML toolse
what error code.
Another possibility - is it possible the permissions on a parent directory of
this file are extremely restrictive?
Thanks,
Mike Carlson
-Original Message-
From: John Cooper (Volt) [mailto:a-jc...@microsoft.com]
Sent: Thursday, May 06, 2010 12:02 PM
To: General discuss
Yes, we still use nant/wix.build, and "make.bat" should work.
I don't have direct experience with the wix CVS repository, but I would think
it's best to begin building from cvs. If there is a problem, certainly it's
something we will want to fix.
-Original Message-
From: Neil Sleighthol
Just saw your later reply with the solution to your own problem; sorry for the
spam everyone.
Threads on this alias aren't well-organized in my mail viewer, and I often
forget to manually check if there is a later reply to a thread, before replying
myself...
Thanks,
Mike Ca
The VerQueryValueW() call has been there since WiX 3.5 forked from WiX 3.0, so
I don't think this problem is necessarily Unicode-related. Perhaps you only
recently started using FileUtil's FileVersion() function (which requires
"version.lib" to be linked in)?
Try adding "version.lib" to the lis
Please file a bug for this, if you haven't already.
Thanks,
Mike Carlson
-Original Message-
From: Navid Azimi-Garakani [mailto:naz...@microsoft.com]
Sent: Monday, April 19, 2010 4:14 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] 64-bit WiX
T
Thanks Dave. I don't know why I didn't see that. I looked at it several
times.
On Mon, Apr 19, 2010 at 1:28 PM, Dave Brotherstone wrote:
> On Mon, Apr 19, 2010 at 9:48 PM, Mike Rerick wrote:
>
> >
> > Is there a work-around I can do to get this installer to build?
compile and link from an Ant script.
Is there a work-around I can do to get this installer to build?
Thanks
Mike
Ant script fragment
ignia, and it will update your MSI
appropriately, according to the way you signed your cabs.
If you use MSBuild, this integrates well with MSBuild as well - see the WiX 3.5
CHM page on "Insignia" for instructions to use insignia with MSBuild.
Thanks,
Mike Carlson
-Orig
tool called "Insignia" to make this
process easier - see wix.chm for more information about Insignia in WiX 3.5.
Thanks,
Mike Carlson
-Original Message-
From: Christof Schmutz [mailto:christof.schm...@cstsoft.de]
Sent: Tuesday, April 13, 2010 11:07 AM
To: General discussion for Win
nd I made it to
be executed after ConfigureIIs (in Wix 3.5 I changed to be after
ConfigureIIs7), but from log file I can see that website was not created
after ConfigureIIs7 action. Can you please specify name after which IIS
action I should execute mine custom action?
-Original Mess
Also, what version of the tools are you running? Have you tried "3.0 RTM" or a
recent 3.5 weekly release?
-Original Message-
From: s...@pacaccess.com [mailto:s...@pacaccess.com]
Sent: Wednesday, March 31, 2010 10:26 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re
s before about the same thing:
http://sourceforge.net/tracker/?func=detail&aid=2961215&group_id=105970&;
atid=642714
Is it the same as yours?
And Mike already fixed it in the latest Wix build which should be
available today.
-Original Message-
From: Mike Carlson (DEV DIV) [mailto:m
Registry column, where xxx are the same numbers (i.e., 109). None of the
other column data for the "identical" keys are the same in the Registry
table. Is this a bug in dark?
Thanks
Mike
dark -x \_Files
\.msm -o \.wxs
Microsoft (R) Windows Installer Xml Decompiler version 3.5.1519.0
Co
I'd file a bug with the authoring you pasted below, and the answers to these
questions, if possible:
What's the exact error message you get (use a verbose logfile to find out)?
Does it work correctly if you install to an IIS6 machine?
Thanks,
Mike Carlson
-Original Message-
It shouldn't be giving this message, but have you tried building the project? I
ask because it could be a secondary file (like the primary output) that heat is
trying to open (and is causing the exception to occur).
-Original Message-
From: Bill McCormick (LIST) [mailto:wpmccorm...@ace-c
The recommended way now is typically to run heat.exe to "harvest" the com
registration information out of your DLL. This way it won't actually run the
code from the DLL at install-time (which is more likely to fail, won't handle
all of MSI's transactionality appropriately, and is generally a non
I just realized this was already replied to. Apologies for the spam, everyone.
-Original Message-
From: Mike Carlson (DEV DIV)
Sent: Monday, March 22, 2010 11:26 AM
To: wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] (no subject)
The problem you're running into is that i
The problem you're running into is that in the MSI world, "[PropertyName]" is
used to dynamically (at install-time) pull in the value of a property. So, you
need to escape your bracket so it isn't looked at in that way.
To escape "[" replace it with "[\[]"
To escape "]" replace it with "[\]]"
T
DirProperties is part of IIS, etc. Then during both compile and link, you
need to reference the right extension too when compiling, like:
Candle -ext wixutilextension file.wxs
Light -ext wixutilextension file.wixobj
Hopefully you get the idea.
Thanks,
Mike Carlson
-Origin
om: Navid Azimi-Garakani
Sent: Monday, March 15, 2010 8:34 PM
To: General discussion for Windows Installer XML toolset.
Cc: Mike Carlson (DEV DIV)
Subject: RE: WIX 2.0 on IIS 7.5 with IIS 6.0 Compatiblity Mode
I should mention that that errors are primarily trivial with the exception of
the followin
't require the IIS6 compatibility layer (but 3.5 is still under
development, so expect some bugs if you try 3.5).
Thanks,
Mike Carlson
-Original Message-
From: Navid Azimi-Garakani [mailto:naz...@microsoft.com]
Sent: Monday, March 15, 2010 2:29 PM
To: wix-users@lists.sourceforge.ne
I can't help with the CVS issues, but to download the latest official build of
3.5, you want the "weekly releases" page, linked from wix.sf.net.
The direct link to weekly releases page is here:
http://wix.sourceforge.net/releases/
Thanks,
Mike Carlson
-Original Message-
You need to use a bootstrapper (an EXE designed for running one or more
installation packages) that will pass the appropriate language property to the
MSI at install-time.
WiX 3.5 will have a bootstrapper called Burn, but it's still under development
right now.
Thanks,
Mike Ca
I read the example from the wix tutorials on how to do custom actions that are
not a part of Wix.
The tutorial states to use a dll and gives an example in c. Problem is I can't
read c so I do not understand what is going on (vb.net and c# work for me).
I created a simple dll in c# to create
I believe you want to list these properties as the value of the built-in
"SecureCustomProperties" property, so they will be set in the server context as
well.
Try adding something like this to your authoring:
Thanks,
Mike Carlson
-Original Message-
This is what I have done for all of my database installs. I took the
standard FeatureTree and extended it with some additional screens. I use a
third party custom action to get a list of db servers that are available.
Hope this helps.
Also, see http://wix.mindcapers.com/wiki/WiX_and_SQLServer
I
checks
for the cancel between each file.
- Original Message -
From: Mike Carlson (DEV DIV)
To: General discussion for Windows Installer XML toolset.
Sent: Tue Feb 09 17:23:12 2010
Subject: Re: [WiX-users] Interrupting a WiX build
Do the cancel build (etc.) buttons work?
If you'
Do the cancel build (etc.) buttons work?
If you're sure the regular "cancel build" options that work for C++ / C# builds
aren't working for wix (either the options aren't visible, or the options are
visible but don't function as you feel they should), go ahead and file a bug
against WiX 3.5 / V
ow to reproduce the problem
as you can in the bug, and the log excerpts you've already provided in this
e-mail are perfect; make sure to include those in your bug reports too.
Thanks,
Mike Carlson
-Original Message-
From: Matteo Canessa [mailto:matteo.cane...@microarea.it]
Sent: Frida
as much
repro information as you can.
Thanks,
Mike Carlson
-Original Message-
From: Matteo Canessa [mailto:matteo.cane...@microarea.it]
Sent: Thursday, January 28, 2010 6:53 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Creation of an application pool on IIS7 install
that
solves the problem?
If it doesn't solve the problem, file a bug on sourceforge against v3.5, attach
a repro (make sure to exclude any sensitive things from your authoring, if
there are any), and attach a verbose MSI log of the install which didn't seem
to work.
Thanks,
Mi
esign is that users should only write
declarative authoring to represent the things they want installed, and let the
installation engine (and/or the built-in wix custom actions) handle the actual
installation for you.
Thanks,
Mike Carlson
-Original Message-
From: phillip_sid...@delltea
Look closely; some of the link was cut off and placed in the next line, and
this portion was excluded from the hyperlink. If you include the "ine.html"
from the next line in the part that's hyperlinked, the link works for me.
-Original Message-
From: Jahanzeb Khan [mailto:jk...@commondes
I have an application which needs to install new bits for
Interop.FOOBARLib.DLL to the GAC. The problem is that the version
number is the same as the old version and the new bits do not get
written the GAC on an upgrade. We execute the RemoveExistingProducts
action after the InstallFinalize actio
inker...
"%WIX_BIN_PATH%\light.exe" -out "installer.msi" "installer.wixobj" -ext
"%WIX_EXT_PATH%\WixUIExtension.dll" -ext
"%WIX_EXT_PATH%\WixUtilExtension.dll" -ext
"%WIX_EXT_PATH%\WixSqlExtension.dll"
if errorlevel 1 goto linkerr
Mike
It sounds to me like a bug. Please file one - don't forget to copy all the
helpful information (version information, sample authoring + log failure
messages) from your mail into the bug.
Thanks,
Mike Carlson
-Original Message-
From: Duncan Kelbie [mailto:duncan.kel...@neural
en let it be a cab external to the MSI (set
Media/@EmbedCab to no) instead of embedded in the MSI, and wix shouldn't have
to do anything with it if it hasn't changed.
Thanks,
Mike Carlson
-Original Message-
From: Kim Gybels [mailto:kim.gyb...@metris.com]
Sent: Wednesda
-
Von: Blair [mailto:os...@live.com]
Gesendet: Montag, 2. November 2009 23:00
An: 'General discussion for Windows Installer XML toolset.'
Betreff: Re: [WiX-users] Link error for dutil.lib
Are you building 32-bit, or some flavor of 64-bit?
-Original Message-
From: Mike Carlson (DEV DIV
Did you try a clean build? i.e. Delete your build output directory and build
again.
Thanks,
Mike Carlson
-Original Message-
From: Jiang, Chunyan (GE Healthcare) [mailto:chunyan.ji...@ge.com]
Sent: Monday, November 02, 2009 7:20 AM
To: General discussion for Windows Installer XML
you referring to a
repair scenario, or "uninstall" then "install"? Also, if you have a repro
sample (with logs) using a dummy cert, that will help the investigation.
Thanks,
Mike Carlson
-Original Message-
From: phillip_sid...@dellteam.com [mailto:phillip_sid...@dellte
Mike
-Original Message-
From: Stout, Mike [mailto:mike.st
.
Mike
-Original Message-
From: Jiang, Chunyan (GE Healthcare) [mailto:chunyan.ji...@ge.com]
Sent: Friday, October 02, 2009 8:26 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users
erver.
AddMachineCertificate: Error 0x80092004: Could not locate key pair from
PFX file.
AddMachineCertificate: Error 0x80092004: Failed to install certificate.
AddMachineCertificate: Error 0x80092004: Failed to install per-machine
certificate.
- Phil
-Original Message-
From: Mike Carlson (DE
1) What version of WiX are you using?
2) What error message do you see in a verbose logfile in the event of failure?
3) Have you tried making the associated Component Permanent?
Thanks,
Mike Carlson
-Original Message-
From: phillip_sid...@dellteam.com [mailto:phillip_sid...@dellteam.com
e to do things
like this yourself.
Anyway, to answer your original question, try escaping them like this:
"[\[]" (without quotes) for the open square bracket.
"[\]]" (without quotes) for the ending square bracket.
I believe this is the standard MSI way to e
option of removing a specific version or completely
removing all of the installed versions.
Correct. File names and paths for VS support stay the same.
Preference would be to release a single MSI that can be run from
windows.
Mike
-Original Message-
From: Blair [mailto:os...@live.com
behavior without having to change the product ID?
Mike
--
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills
line: msiexec /i msiname.msi
LOGVERBOSE=1 /l*v logname.log
I am using MSI 4.5 and WiX 3.0.5210.0. Everything is running on Windows XP
SP2 or SP3.
I was wondering if anyone else has seen this and if so, how do I prevent
this from happening?
Thanks
*Mike Rerick*
*Sr. Software Engineer
1 - 100 of 764 matches
Mail list logo
