My projects has three options in the "Setup" dialog. "Typical" with
InstallLevel 3, "Admin" with InstallLevel 1, and the "Custom" option
which takes it to the "Custom Setup" dialog with InstallLevel 3 as the
default.
This all works fine, but I've run into trouble trying to modify the
installation
I've got a rather simple question that is probably due to some obvious
in hindsight error, but I'm totally stymied by it and haven't had any
luck searching for a solution.
I just recently switched from an x86 machine to an x64 machine running
XP x64. I suddenly find that some of the installers I'v
> Mike Dimmick
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Geoff Finger
> Sent: 22 May 2007 23:23
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Allowing sources from either x64 or x86
>
> I'
I have two installers for our project, one for 32 bit and one for 64
bit and I'm running into some problems with the x64 version.
My first question, is there a tutorial for how to build x64 installers
with wix 2.0 somewhere? I could have sworn I saw a link to one at some
point, but I can't find an
After poking around a little more I've found something in the logs
that might be related. There are a lot of messages about:
"WIN64DUALFOLDERS: Substitution in 'C:\Program Files
(x86)\InstallDir\File.exe' folder had been blocked by the 1 mask
argument (the folder pair's iSwapAttrib member = 0)."
S
On Oct 24, 2007 7:59 AM, Bob Arnson <[EMAIL PROTECTED]> wrote:
> Geoff Finger wrote:
> > Instead what I found was a post claiming "I don't think you want to
> > reference ProgramFiles64Folder either. Use ProgramFilesFolder and
> > Windows Installer will put
I've run into an issue with Vista where the side by side assemblies
installed to WinSxS do not get removed when the uninstaller is run.
I found the https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=260142";>Microsoft
Connect Issue 260142 which seems to indicate that
On Nov 5, 2007 9:33 PM, Bob Arnson <[EMAIL PROTECTED]> wrote:
> Geoff Finger wrote:
> > I've run into an issue with Vista where the side by side assemblies
> > installed to WinSxS do not get removed when the uninstaller is run.
> >
>
> Known issue and I&#
I hope this email gets through (several earlier emails sent from my gmail
account resulted in "SMTP Error (state 9): 451-Could not complete sender
verify callout")
I've been working on the Wix installer for a project at my company for the
past couple weeks, but the project manager has decided
On Fri, 20 Oct 2006, Mike Dimmick wrote:
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Geoff Finger
> Sent: 20 October 2006 00:54
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Private Assemblies with Wix
>
Thanks Mike for your earlier help with private assemblies. We've dropped
the idea of doing anything special with them but as expected we've moved
on to shared assemblies so I've got some more questions for anyone who can
help.
I've taken one of our old COM dlls and added an AssemblyInfo.cpp wi
On Fri, 27 Oct 2006, Phil Wilson wrote:
> If you have a .NET assembly exposing COM interfaces you don't need an
> interop Dll, but you need it registering in the same general way that
> Regasm does (there's Tallow). Gacutil just puts it in the GAC. What you
> get for a registered .NET assembly are
Thanks for the advice about assemblies earlier. Since everyone seemed to
think we were using assemblies in the wrong way we've once again scaled
back our usage and are no longer trying to use the GAC.
We have some dlls that are used by several different products. Since
different versions of th
I'm not sure what steps you've already completed so here's the entire
process I followed. In my case I was using MS VS 2005, obviously some
steps my have to be addapted depending on the enviroment you're
working under.
First you have to create a key if you don't have one already:
makecert -n "CN=
I can't get the "<>" comparison to work in the CDATA statement for my
Condition elements and trying to set a default value on the property
that is being tested is breaking them as well.
I have a radio button selection during the setup that determines
whether the service that is being installed wil
Swapping in "<>" fixed both issues! Thank you!
Why is it necessary to use that in some cases though when in other
spots I used "<>" without any problem? Shouldn't using the CDATA
wrapper have prevented it from being an issue?
On 1/30/07, Albert van Peppen <[EMAIL PROTECTED]> wrote:
> Did you try
The program I'm working on needs to have either SQL 2005 or the SQL
Server Native Client installed. We've decided that if neither of those
have been installed we should give the user the option of installing
the Native Client after the basic installation is finished in order to
simplify things for
I'm trying to include a merge module from an older project that was
made when we were using InstallShield to create our installations.
When I try including it in my Wix project it compiles fine but when
running it I get the error:
Action start 16:32:36: ResolveSource.
MSI (c) (EC:E0) [16:32:36:12
TED]> wrote:
> That should work. If you have any custom actions in your msm verify
> that the sequencing is after the cost standard actions.
>
> Thanks,
> Tom
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Geoff
> Fing
ink.
>
> Thanks,
> Tom
>
> -Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Geoff
> Finger
> Sent: Wednesday, March 14, 2007 4:21 PM
> To: wix-users@lists.sourceforge.net
> Cc: Thomas Svare
> Subject: Re: [WiX-users] Using I
I have a feature that can only installed if .net 1.1 or higher is also
installed. The description for the feature indicates this requirement
but I don't want to trust to the users' good sense, some of them will
either not read the message or ignore it and get into trouble.
Searching through the ar
I've been trying to figure out how to copy some files located in the
directory the msi file is being run from to the Install directory, the
big problem being that I couldn't find an easy way to fetch the value
of the source directory.
SourceDir leads to the root of the drive and CURRENTDIRECTORY i
hing I have any control over.
On 3/22/07, Rob Mensching <[EMAIL PROTECTED]> wrote:
> Why are you copying files from the original media instead of just using the
> File element?
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Geo
Short version:
Is there any way to override what seems to be the default behavior and
force Wix/msi to install additional file elements in an assembly
Component into the WinSxS folder even though they aren't included in
the main file's manifest? Or alternately are there any kind and
generous souls
us/library/ms682586.aspx
>
> Under no circumstances is the location of the DLL that is loading the other
> DLL used in determining the DLL search path. This is why people have so
> many problems with COM in-process servers that try to load DLL dependencies
> from their "application&
all them.
>
> I still don't understand why your LoadLibrary works when you have the files
> in the same folder though - I'd be curious to see what GetModuleFileName
> returns on those modules.
>
> Kelly
>
>
>
>
>
> "Geoff Finger" <[EMAI
:08 PM, Maletz, Josh <[EMAIL PROTECTED]> wrote:
> Have you tried putting them in separate components or just using the
> CopyFile element?
>
>
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Geoff
> Finger
> S
The program I'm installing has an Interop we'd like to install on
systems using .NET, but we still want to be able to install the
program with reduced functionality on systems without .NET. However
when we tried installing it on such a system we got an error because
it tried to add the interop to a
Whoops, it turns out that it was actually being installed twice in
different spots, once I updated _both_ spots to use the check
everything was fine. That's what i get for trying to debug stuff at
6pm without making sure i've checked all 5000 or so lines of code =P
(And perhaps I ought to pull thos
I've got several services I'm trying to install. If I add
"Start='install'" to the ServiceControl element then it will try to
start them, but it will almost always fail with a 1920 error. I'm
pretty sure this is because some of the services are dependent on
side-by-side assemblies that are being in
u're not taking care of?
>
> You can always check if the dependencies are already installed and skip
> trying to start the service if they are not, but like I said, if your
> product is installing those assemblies anyhow it shouldn't be an issue.
>
>
> Geoff Finger-2
> after InstallFinalize and with ExeCommand set to:
> net start
>
>
> Alex
>
>
>
>
>
> -Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Geoff Finger
> Sent: Friday, February 22, 2008 3:42 PM
> To: wix-use
We just recently added the Upgrade Id value to the installer and the
testers have complained that it deletes the old version of the program
without asking first, so I'm trying to add an ok/cancel popup dialog
at the first step of the installer if a previous version is detected
to warn them about th
Okay, thanks. I added an extra page after the Welcome dialog with the
confirm/cancel message. Just one more page for the users to click
through I guess :)
On Sat, Mar 1, 2008 at 2:47 PM, Bob Arnson <[EMAIL PROTECTED]> wrote:
> Geoff Finger wrote:
> > I hooked up the dialog to th
We have two Projects, A and B. There is a file in ProjectB that needs
to be run by ProjectA. Originally thinking that ProjectB was a "child"
of ProjectA I wrote some code that included the lines:
That worked fine, and to show a "random" example from the install log
right after CostFinalize, res
I'm having some trouble getting a couple of 3rd party msm files to
work correctly. The original instructions said that along with
including the merge module we should also schedule several custom
actions in the msi. After that failed I looked around the archives and
found several threads saying tha
Our installation needs to install SQLExpress under certain conditions,
and unfortunately we don't know what those condtions are until the
user has already gotten through the installation, so we can't run it
ahead of time through the setup.exe. After much experimentation I got
an ExeCommand custom a
That was in fact the problem, thanks!
On Sat, Mar 22, 2008 at 11:42 AM, Bob Arnson <[EMAIL PROTECTED]> wrote:
> Geoff Finger wrote:
> > In the ModuleInstallExecuteSequence table of the msm files we have rows
> such as:
> >
> > Action: RemoveOldDriver.B391C1
If we run our installation and then delete the msi when we're done,
uninstalling the program through add/remove works but selecting the
Change option fails. First it pops up the "The feature you are trying
to use is on a network resource that is unavailable" dialog, and if we
cancel out of that it
We're trying to install a service that is dependent on HTTP SSL in XP,
however that service doesn't exist and isn't needed in Vista. When we
added another ServiceDependency element to the service for HTTP SSL it
stopped the errors we were getting in XP, but now it's impossible to
start the service
40 matches
Mail list logo
