sue. And
> otherwise we would be hearing about it all the time.
>
> --
> Nicolas
>
> 2014-01-29 Scott Palmer :
>> if the install was a major upgrade and that file was in-use during the
>> uninstall then it may get deleted on reboot. That happens a lot because MSI
>
if the install was a major upgrade and that file was in-use during the
uninstall then it may get deleted on reboot. That happens a lot because MSI
is too stupid to check if fire that it might install are already scheduled
to be deleted on reboot. So the new file gets installed and then deleted.
Sc
Without running msiexec as an Administrator? If you have any code you can
share I would appreciate it.
Thanks,
Scott
On Tue, Jan 28, 2014 at 3:39 AM, Blair Murri wrote:
> I’ve done it from a deferred DLL CA using the CreateSymbolicLink() API
> before.
>
>
> Blair
>
>
r:\administrator cmd.exe /c mklink /D
> some_link_name some_directory_path
>
>
> C:\>runas /user:\ cmd
>
> ref from: C:\>runas /user:\ cmd
>
> cheers
>
>
>
> On Fri, Jan 24, 2014 at 4:12 PM, Scott Palmer wrote:
>
> > Can someone show me code that
mklink /D
> some_link_name some_directory_path
>
>
> C:\>runas /user:\ cmd
>
> ref from: C:\>runas /user:\ cmd
>
> cheers
>
>
>
>> On Fri, Jan 24, 2014 at 4:12 PM, Scott Palmer wrote:
>>
>> Can someone show me code that can su
md.exe /c sc delete something"
> Return="check"
> Execute="deferred"
> Impersonate="no" />
>
>
> On Fri, Jan 24, 2014 at 4:12 PM, Scott Palmer wrote:
>
> > Can someone show me code that can suc
Can someone show me code that can successfully do it?
I tried:
$needALinkForThisComp=3
I'm running on Windows 7
The cmd window that pops up (titled: "Administrator:
C:\Windows\SysWOW64\cmd.exe") indicates that the System user doesn't have
permission to make a symbolic link (th
Thanks, I found that and fixed a few other VBScript problems and now I
have it working. (Only to discover other problems, however.)
Scott
On Mon, Nov 2, 2009 at 1:15 PM, Wilson, Phil wrote:
> The WScript.Echo won't work - that's supplied by the WSH object, not by MSI.
> Do you see that message?
I'm having trouble getting a VBScript custom action to work. It's
purpose it so backup some files that the major upgrade may otherwise
delete.
My WiX source looks like this:
My script (project_backup.vbs) looks like:
' VBScript source code
Function back
In my UI I have three options represented by radio buttons in the UI
that only are shown the first time the product is ever installed.
Call them A,B,C. The selected feature is installed and remembered in
the registry so I don't ask again if a newer version of the product is
installed.
I wanted to
gt; they may not exist on all platforms.
>
> -Original Message-
> From: Scott Palmer [mailto:swpal...@gmail.com]
> Sent: Wednesday, October 14, 2009 7:21 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] Criteria for Automatically Genera
What are the exact criteria for getting automatically generated GUIDs to
work?
I suspect this is related to my use of WIX_DIR_COMMON_DOCUMENTS (since there
doesn't seem to be another way to get to that "standard" directory).
I'm getting this error:
error LGHT0231: The component 'indexComp' has a
The problem I'm having with this is for the "accept license" checkbox of the
"Minimal" UI. It's really awkward to make that UI not look ugly.
The external UI is interesting. One way that seems reasonable would be for
an external UI in a bootstrapper to come up with values for all sorts of
public
Can the default WiX UIs change to use that trick so we don't have to
customize everything just to get a decent background in the installer?
Scott
On Tue, Oct 6, 2009 at 12:56 AM, Blair wrote:
> This is very often discussed (search the archives, this is the second time
> this week).
>
> This is a
How long has the
problem been known? How many broken installs are out there that would "just
work" if this was fixed?
Thanks for your help!
Scott
> -Original Message-
> From: Scott Palmer [mailto:swpal...@gmail.com]
> Sent: Saturday, October 03, 2009 4:32 AM
>
be able to author our
> file lists once, use stable component guids (and/or auto-generated ones),
> and place RemoveExistingProducts late (which is more efficient in several
> measures).
>
> -Original Message-
> From: Scott Palmer [mailto:swpal...@gmail.com]
> Sent: Friday, Oc
as
> install logs.
>
> With my previous employer we designed and had written much of such a tool
> (integrated into our evolving build system). I have plans to write such a
> tool, if there is interest I could push it up in the list.
>
> -Original Message-----
> From:
: Change ProductCode(s) (make this a major upgrade)
> >2: Force an updated version resource in R1 (sorry)
> >
> >
> >
> >
> > > Action='removeOnInstall'
> > .../>
> >
> > <... Id='R3'/>
> >
> &g
ch of such a tool
> (integrated into our evolving build system). I have plans to write such a
> tool, if there is interest I could push it up in the list.
>
> -Original Message-----
> From: Scott Palmer [mailto:swpal...@gmail.com]
> Sent: Monday, September 21, 2009 6:19 A
t;
>
> Action='removeOnInstall'
> .../>
>
> <... Id='R3'/>
>
>
> I can work on the extra credit latter...
>
> -Original Message-
> From: Scott Palmer [mailto:swpal...@gmail.com]
> Sent: Monday, September 21, 2009
In version 1 of my application I have a component C1 which contains multiple
resources.
C1 = { R1, R2, R3 }
The file R1 is the key path for C1.
The rest of the application requires that the resources are installed with
the same path and names in V1 and V2.
In version 2 of my application I need
Getting back to the original problem. The files that were missing after my
major upgrade install were in a merge module that I created that was the
same in both products and therefore followed the component rules (since
there were no changes to the install path or content of any components).
Woul
ry MSMs use SxS, which is why they require the later
> sequencing
> of RemoveExistingProducts.
>
> Given that you are using the runtime library MSMs, I would recommend
> moving
> to the locations around InstallFinalize and making sure you are
> following
> the Compon
/aa371197.aspx (which is what
> you
> appear to be trying to achieve).
>
> You could try moving that action to After="InstallValidate" to see
> if that
> makes any difference.
>
> -Original Message-
> From: Scott Palmer [mailto:swpal...@gmail.com]
&g
I have made an installer that attempts to remove a previous version of a
product before installing the new version.The installer runs and appears to
remove old files and coy new ones... but it at the end of it all there are
files missing.
I have a merge module that installs a common component into
On Wed, Aug 12, 2009 at 6:15 AM, Peter Shirtcliffe wrote:
> You could also have the application create it on first run. With the
> application being hard to find, you could run it after [first-time]
> installation, if that isnt too irritating to the users.
>
The application isn't hard to find, ju
Our product places some commonly accessed documents in "C:\Documents and
Settings\All Users\Documents\CompanyName\ProductName" using
... blah...
Since on XP (the most common OS for our customers) that path is a royal pain
to navigate to, we install a shortcut on the desktop to our docume
How can I have my WiX installer create an item in the Start menu that is
"pinned" ?
Thanks,
Scott
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with M
On Thu, Jul 10, 2008 at 10:10 AM, Christopher Painter <
[EMAIL PROTECTED]> wrote:
> I know this won't directly answer your question, but any chance you could
> just switch to .NET? You could create a ComVisible(true) class that deals
> with your XML/SOAP issues and exposes it to your unmanaged co
Resending (third time) since this never seems to get to the list...
-- Forwarded message --
I need to include MS SOAP in my installer via three merge modules provided
by Microsoft:
isapi3_files.msm
soap3_core.msm
winhttp51.msm
They in turn depending on MS XML4 SP1.. of which I ha
Resending since the original didn't appear on the list after two days...
-- Forwarded message --
I need to include MS SOAP in my installer via three merge modules provided
by Microsoft:
isapi3_files.msm
soap3_core.msm
winhttp51.msm
They in turn depending on MS XML4 SP1.. of which
I need to include MS SOAP in my installer via three merge modules provided
by Microsoft:
isapi3_files.msm
soap3_core.msm
winhttp51.msm
They in turn depending on MS XML4 SP1.. of which I have two merge modules,
also from Microsoft:
msxml4sxs32.msm
msxml4sys32.msm
As it happened I was missing the X
966&group_id=105970&atid=642714
>
> Actually we're not stumped on this one. If I recall, investigation revealed
> it to be a bug in VS2005 (which is why it's not a problem in VS2008). There
> is a moderately complex workaround possible, but nobody has implemented it
&g
age-
> From: [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] On Behalf Of Scott Palmer
> Sent: Wednesday, July 02, 2008 08:13
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] WiX 3.0.4227.0 still broken with Visual Studio 2005
>
> In the outp
In the output window: error messages are seen only numerically e.g. "Error
CNDL0205" with no descriptive text, and newlines are still missing.
Scott
-
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies ha
d and hit a bug then
> you can get trapped in a difficult position.
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] On Behalf Of Scott Palmer
> Sent: Wednesday, June 25, 2008 06:21
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-
I have a product that can be built two ways. I have two WiX installer
projects in visual studio, sharing many of the same wxs files. One project
defines a variable in the project settings to cause some of the .wxs files
to compile differently, like this:
...
annoying ones that should have higher
priority (along with the other one that you pointed out - same line
output). Thanks for the bug reports!
Justin
From: Scott Palmer
Sent: Wednesday, May 14, 2008 7:14 AM
To: Justin Rockwood
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Did
We all knew this thread was going nowhere from the first post of course...
My only point was that (in my experience) the original posters frustration
is shared by the vast majority of developers trying to do installers on
Windows. (i.e. everyone I know that has ever seen or worked on a WiX
project
On Tue, May 13, 2008 at 7:05 PM, Justin Rockwood <[EMAIL PROTECTED]>
wrote:
> I hate the locking as well. Unfortunately, this is a bug in the MPF (the
> Visual Studio SDK) that they have not fixed yet. We will have to just fix it
> on our own instead of waiting for a fix from them. Note that it's
Yes, I am using VS2005. The 2925 build on SourceForge works properly with
the line endings. That narrows it down to only around 1200 builds :-)
Regards,
Scott
On Tue, May 13, 2008 at 4:12 PM, Rob Mensching <[EMAIL PROTECTED]>
wrote:
> The line endings is a different bug that has been open fo
op-up that says "Visual
Studio is not responding. If this happens frequently contact Microsoft." -
Is always frequently enough?
Scott
On Tue, May 13, 2008 at 3:00 PM, Scott Palmer <[EMAIL PROTECTED]> wrote:
> 4102 works better.. though it still has problems with Light output.
4102 works better.. though it still has problems with Light output. The
text description of errors is missing - you just get a code, and it's all on
one line in visual studio.
Scott
On Tue, May 13, 2008 at 12:02 PM, Scott Palmer <[EMAIL PROTECTED]> wrote:
> Cool thanks.
>
>
On Tue, May 13, 2008 at 1:26 PM, Josh Rowe <[EMAIL PROTECTED]> wrote:
>
>
> The moral of the story is that deployment procedures really are part of
> the source code for an application. They are also risky, so implement them
> first to minimize risk.
>
This is the problem. Deployment SHOULD b
bug. I'll make sure the bug gets fixed by the next build.
>
>
>
> *From:* [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] *On Behalf Of *Scott Palmer
> *Sent:* Tuesday, May 13, 2008 08:31
> *To:* wix-users@lists.sourceforge.net
> *Subject:* [WiX-users] Did WiX V3 project
I just updated WiX from the 2925 build (still the last "beta" posted to SF)
to the May 9 weekly build 4109. Now all of my WiX project don't build.
They don't even get started. I instantly get this error when trying to
build:
3>-- Build started: Project: Stream, Configuration: Release Any CP
Well I dropped by to ask for help (I wonder if I will get it now :-)) but
first I have to chime in and agree with Chris and Mark. I dislike that what
I am about to post is basically a rant, but I think there are a lot more
people on their side than others seem to think, so I want to show my
suppor
Never mind.. got it all sorted.
it is. I gather Directory Ids are properties of sorts and property
expansion in the directory name doesn't happen.
Sorry for the noise.
On Jan 23, 2008 9:35 AM, Scott Palmer <[EMAIL PROTECTED]> wrote:
> Err. of course I meant
>
>
>
Err. of course I meant
On Jan 23, 2008 9:31 AM, Scott Palmer <[EMAIL PROTECTED]> wrote:
> Ah, WiX to the rescue.. thanks for that.
>
> Now, it seems these are just standard properties.. so I don't use them
> like Directory Ids, right?
> The docs don't seem
--
>
> *From:* [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] *On Behalf Of *Scott Palmer
> *Sent:* 22 January 2008 21:32
> *To:* wix-users@lists.sourceforge.net
> *Subject:* [WiX-users] Is there a directory property
> forCSIDL_COMMON_DOCUMENTS ?
>
>
>
>
I'm trying to make some changes to play nice on Vista... Currently our
product has several folders that it places under Program Files, e.g.:
C:\Program Files\Company\Product\Data_A
C:\Program Files\Company\Product\Data_B
C:\Program Files\Company\Product\Data_C
The purpose of these folders was t
On Jan 7, 2008 6:18 PM, Mike Dimmick <[EMAIL PROTECTED]> wrote:
> Right, let's explain UAC.
>
I've replied to Mike off-list as the discussion is not about WiX or MSI
anymore. If anyone has related comments to add, please mail me privately to
keep the list on-topic.
Thanks,
Scott
-
action since this particular custom
action doesn't modify system state it is "less evil" than most.
Thanks for the assistance everyone.
Scott
On Jan 4, 2008 2:07 PM, Scott Palmer <[EMAIL PROTECTED]> wrote:
> > I want
I want to detect if UAC is turned on in Vista and refuse to install if it
is. How can I do this?
Scott
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/
On 10/24/07, Bob Arnson <[EMAIL PROTECTED]> wrote:
>
> Scott Palmer wrote:
> > Is there a way to actually get the license agreement to show on the
> > license agreement screen without having to highlight the text or
> > adjust the scrollbar? I find that my license a
On 1/22/07, Goetz, Russ <[EMAIL PROTECTED]> wrote:
>
> Thanks to help from this group I am now able to specify which UI I wish
> to use by passing the following to light.exe: -ext
> WixUIExtension.dll-cultures:en-us and specifying say
>
>
>
>
>
>
>
> In my .wxs file. The minimal UI shows a lice
If an upgrade isn't supported then what happened when I renamed the file and
it "just worked" ?
I think that the msi files provided with WiX itself should be good examples
to follow... but perhaps they aren't.
Scott
On 7/25/07, Quattro IV <[EMAIL PROTECTED]> wrote:
I got that same error, you
I downloaded the latest 3.0 "release" and when I attempt to install the
project aggregator MSI windows gives me an error message " A network error
occurred while attempting to read from the file C:\ProjectAggregator2.msi"
(resending, since list acknowledged receipt but failed to follow through
wi
I downloaded the latest 3.0 "release" and when I attempt to install the
project aggregator MSI windows gives me an error message "A network error
occurred while attempting to read from the file C:\ProjectAggregator2.msi"
There are a couple odd things about this. For one, access to my local "C"
d
On 7/16/07, Bob Arnson <[EMAIL PROTECTED]> wrote:
Scott Palmer wrote:
> Microsoft certainly doesn't like to make things easy do they? I
> assume though that if someone in the WMF group clued in to using MSI
> that they might also have the foresight to provide a me
Microsoft certainly doesn't like to make things easy do they? I assume
though that if someone in the WMF group clued in to using MSI that they
might also have the foresight to provide a merge module for the
redistributables. Kind of like they should have years ago.
However, assuming that they
I've got a checkbox in my installer that for some reason cannot be changed
by the user and I haven't a clue why. Anyone got some ideas?
Here's some code snippets:
The initial state is set to checked... (most users will want to upgrade ..
some will need to keep old versions because later verson
/en-us/library/aa372389.aspx
Rennie
----------
*From:* Scott Palmer [mailto:[EMAIL PROTECTED]
*Sent:* 6. juni 2007 14:26
*To:* wix-users@lists.sourceforge.net
*Cc:* Rennie Petersen
*Subject:* Re: [WiX-users] Conditionally installing components based on
user'slocale
Thanks, but I need to
the UI is
invoked. (I query the property in the Welcome dialog box.) But it should
also be possible to make use of this property in MSIs irrespective of
whether the UI is invoked or not.
Rennie
--
*From:* [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] *On Behalf Of *Scott
As part of my setup I would like to write certain registry values depending
on the country setting of the OS. E.g. for North American users I might set
a registry value to 1, for European users the value would be set to 2.
Is there an easy way to do this without writing a custom action?
Failing
The problem here is that Microsoft tools are already in the habit of
automatic code generation - and they all are designed to produce code for
SELF REGISTRATION. The process of self registration is effectively
encouraged by the development environment.
Now if the development process has to chang
But it obviously should be. I hope this can be fixed, since we are stuck
with having to deal with all the problems of COM and for some silly reason
(I haven't seen a good argument against it yet) SelfReg is not supported and
officially broken for dynamically linked DLLs on Vista.
Microsoft also
Not exactly. If you use Heat on a COM DLL, Heat inserts "PUT-GUID-HERE" for
the GUID so you can do a search/replace as part of the automated build to
keep the GUID correct and always the same for that component.
Other issues are with the directory structure that Heat uses and the fact
that it's
Ah, but having the built files build to a "Release" folder isn't the
problem. The problem is the WiX code generated by "Heat" wants to install
the files TO a folder named "Release" inside the applications target folder
of the user's machine. In order to install the DLL to the folder I want, I
ne
all time (Tallow, Heat etc).
Phil Wilson
------
*From:* Scott Palmer [mailto:[EMAIL PROTECTED]
*Sent:* Thursday, May 17, 2007 11:58 AM
*To:* Wilson, Phil
*Cc:* wix-users@lists.sourceforge.net
*Subject:* Re: [WiX-users] VC8 runtime merge module and COM registration
on Vista, erro
time.
Phil Wilson
--
*From:* [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] *On Behalf Of *Scott Palmer
*Sent:* Thursday, May 17, 2007 11:42 AM
*To:* wix-users@lists.sourceforge.net
*Subject:* [WiX-users] VC8 runtime merge module and COM registration on
Vista,error 0x
I have a problem on Vista where my COM DLLs don't register (HRESULT =
0x800736B1) .. after Googling it seems this is caused by the C runtime not
being installed. (All other DLLs that are compiled with VC6 or supplied by
others register fine.)
My installer also works fine on Windows XP.
I instal
One of my features has "Will be installed to run from network" and "Entire
feature will be installed to run from network" as possible install options.
What is stupid about that is:
- it's the only feature that shows those options
- the feature has no components of its own, just sub-features, and
o file. I could be off on that but
that was my understanding... FWIW.
- Brett
--
*From:* Scott Palmer [mailto:[EMAIL PROTECTED]
*Sent:* Monday, April 16, 2007 2:58 PM
*To:* Brett Kapilik
*Subject:* Re: [WiX-users] Advertised Shortcuts don't show the correct
Ic
PROTECTED] [mailto:
[EMAIL PROTECTED] *On Behalf Of *Scott Palmer
*Sent:* Monday, April 16, 2007 10:53 AM
*To:* wix-users@lists.sourceforge.net
*Subject:* [WiX-users] Advertised Shortcuts don't show the correct Icon
(Despite receiving a confirmation, I haven't seen this message hit the
list af
(Despite receiving a confirmation, I haven't seen this message hit the list
after 4 days, so I'm resending...)
In my WiX XML I have:
...
The shortcut gets created. On my machine and some others the icons are
correct. But many machines get the wrong icon for ALL of the advertised
shortcut
In my WiX XML I have:
...
The shortcut gets created. On my machine and some others the icons are
correct. But many machines get the wrong icon for ALL advertised
shortcuts.. the icon picked up is that of an entirely different application
from another vendor that was already installed on t
On 4/5/07, Bob Arnson <[EMAIL PROTECTED]> wrote:
Scott Palmer wrote:
> That article indicates that Windows Installer is broken for
> per-machine installs as there is no way to specify that you must have
> a per-machine install that works on both XP and Vista.
ALLUSERS=1 doe
I read this:
http://msdn2.microsoft.com/en-us/library/aa371865.aspx
(It took a while to get over the urge to slaughter those responsible... but
I'm feeling much better now.)
That article indicates that Windows Installer is broken for per-machine
installs as there is no way to specify that you m
On 1/25/07, Mike Dimmick <[EMAIL PROTECTED]> wrote:
...
For best results, you should ensure that any common files are members of
the same component (i.e. have the same component GUID) in all packages
that distribute them. Further, the component should have the same
composition (*exactly* the
I have a COM DLL that I want to place in a common place for all products
installed by my company. E.g. \Program Files\Company Name\Common
For the Component I set SharedDllRefCount="yes".
I'm wondering about the best way to install and how the GUID for the
component is involved. Do I use the sa
On 1/25/07, Bob Arnson <[EMAIL PROTECTED]> wrote:
Scott Palmer wrote:
> The "Company Name" folder is already present in the start menu from
> installation of a different product, but the "My Product" sub-folder
> is not created for this product. (There is a
On 1/25/07, Scott Palmer <[EMAIL PROTECTED]> wrote:
On 1/25/07, Scott Palmer <[EMAIL PROTECTED]> wrote:
>
>
>
> On 1/25/07, Bob Arnson <[EMAIL PROTECTED] > wrote:
> >
> > Scott Palmer wrote:
> > > When I install the component, the fil
On 1/25/07, Scott Palmer <[EMAIL PROTECTED]> wrote:
On 1/25/07, Bob Arnson <[EMAIL PROTECTED]> wrote:
>
> Scott Palmer wrote:
> > When I install the component, the file "mm-configwizard.exe" is
> > installed, but the shortcut is not. How is this po
On 1/25/07, Bob Arnson <[EMAIL PROTECTED]> wrote:
Scott Palmer wrote:
> When I install the component, the file "mm-configwizard.exe" is
> installed, but the shortcut is not. How is this possible?
Verbose logs are your friend. Check the InstallValidate component du
I have the following in my WiX source file:
...
...
When I install the component, the file "mm-configwizard.exe" is installed,
but the shortcut is not. How is this possible?
I'm using WiX
On 1/22/07, Bob Arnson <[EMAIL PROTECTED]> wrote:
Steve Bennett wrote:
Ok, I should have clarified that I have read that bit of the tutorial
many times and it doesn't help a lot. In particular:
- the two systems that are displaying it differently have the
same font size, different
On 1/10/07, André Pönitz <[EMAIL PROTECTED]> wrote:
Hi all.
I have the problem that longer runs of 'light'
make my desktop machine basically unusable for
any other task in that time
I run Wix V3. I've noticed that Light locks up all of Visual Studio at
least, but the rest of the system rem
I do the same "horrible hack". I've never tested on Vista though.. but I
don't care about any logo-program as long as my install works.
There needs to be an easy way to turn of the errors that are reported for
this case, since this same issue has come up a couple times already.
On 1/8/07, Andr
Soon as I saw that Wix V2 required me to enter short file names I
immediately tossed it in the garbage (keeping backwards 8.3 filenames in the
OS was one of Microsoft's stupidest ideas) and moved to Wix V3. The only
issue I've had with Wix V3 is that it didn't work properly for installing
device
I wrote a small program to walk a directory hierarchy and generate the XML
for a fragment that defines a ComponentGroup for the root folder that you
specify. It's an easy program to write and the output can be customized to
the way I like it, i.e. a lot cleaner than the output from the WiX tool,
I'm afraid you generated more questions :) ...
On 12/18/06, Mike Dimmick <[EMAIL PROTECTED]> wrote:
An advertised shortcut goes through the Windows Installer engine rather
than running the program (or document) directly. This enables Windows
Installer to check that all components of the requir
When I made my installer with WiX was the first time I had ever seen the
greyed out target. Everyone in the office that I mentioned it to indicated
that it was new to them I don't use MS Office, and the Office users around
here weren't familiar with them. So they may have used them, but they
di
Creating a shortcut shouldn't be a "complication". Until I did my installer
with WiX nobody in the company had ever seen an "advertised" shortcut...
only a couple of them had even heard of them. Nobody actually wants them,
but I was forced to use them for the same reason, to avoid the complicati
On 12/16/06, Rob Mensching <[EMAIL PROTECTED]> wrote:
>
> 1. It is buried somewhere. I think it may be around the File Versioning
> topic.
Got it.. very limited... makes installers hard to get right. The
"rules" (i.e. "omus" vs "amus") should be per component.
> 2. Shipping someone else's con
I'm using WiX3.
I am trying to make a shortcut as part of installing a component. The
shortcut is to a launcher application that is installed in another component
with a command-line argument that has the path to a file in the component
that contains the shortcut.
If I just use:
...
When I uninstall my product Windows Installer asks me to close completely
unrelated applications that share nothing whatsoever with my application.
How can I prevent this?
Regards,
Scott
-
Take Surveys. Earn Cash. Influence
I have a follow-up question:
Where are the docs that say how Windows Installer sets the dates on files
that it installs?
I ask because it turns out that the version resource is not the culprit in
this case. It's sort of the opposite problem.. the versioned files are OK,
the unversioned files g
I have several files from a third party that I can not control the version
information in. It may be that the version information is set to
1.0.0.0for different versions of the same file, some files have no
version info at
all. I want to be sure that the latest file gets installed even if the
pr
When I uninstall my product I'm being asked to shut down applications that
are totally unrelated to my product. It seems to be Java applications that
I need to close down, but really I just need to close the window they have
open, the application can remain running. (E.g. I have a tool that runs
1 - 100 of 110 matches
Mail list logo
