Which version of TFS are you using?
For 2008, I do the same thing, I actually changed the web service config file
to set the directories, I was able to get it pretty close to our developer
configuration so that I could get WiX working with the same settings for both
environments.
It would be better to restart your application pool, rather than IIS.
-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
Sent: Tuesday, May 11, 2010 1:21 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] FW: Reset IIS
Found
This seems like a good and sound plan. Will 3.5 be moved over to codeplex as
well (or updated so the source build from a version control repository)?
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Wednesday, April 28, 2010 11:07 PM
To: General discussion
I agree with that, if it were on codeplex, I would probably be more apt to dig
through the source myself to work through some of the things that give me fits.
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Saturday, April 24, 2010 5:49 PM
To: General
I googled around, and I understand what the warning means, however, I do not
see where it is coming from in my Wix projects. Could someone point me in the
right direction as to locating what is causing the ICE82 Warning?
Also, has anyone corrected the Office PIA warning? We are using the
I think you need to install the IIS 6 metadatabase support for IIS in order to
get this to work for you.
-Original Message-
From: Houssam Hamdan [mailto:houssam.ham...@netiks.com]
Sent: Friday, April 16, 2010 9:35 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Multiple
In my case, I had to deal with two different locations of the bootstrapper
files. This is what works for us.
Just make sure that you have the bootstrapper files in the correct directory
(C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper for example).
There is a packages directory
Do you want to install it, or just check for it?
-Original Message-
From: pateras [mailto:pate...@gmail.com]
Sent: Friday, April 02, 2010 3:23 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Adding a .Net 3.5 web-install prerequisite
I'd like to add a check in my WiX
Really? You removed that option. Was that done in 3.5 or 3.0?
I was able to specify the user that the service ran as, and it installed
correctly. What I was unable to do was to get the package to uninstall when I
did.
John
-Original Message-
From: Rob Hamflett
I am working through some conditional logic in getting the project, and hence
TFS Build to build our installs. The issue I am coming up against is that the
SDK install locations are different on different computers.
Currently, I detect this using this logic inside the WixProj file:
.
Arun Perregattur
-Original Message-
From: John H. Bergman (XPedient Technologies)
[mailto:john.berg...@xpedienttechnologies.com]
Sent: Tuesday, February 23, 2010 3:21 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] SQL2008 Express Merge Module
Does anyone
Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper\ /
/Target
Arun Perregattur
-Original Message-
From: John H. Bergman (XPedient Technologies)
[mailto:john.berg...@xpedienttechnologies.com]
Sent: Wednesday, February 24, 2010 3:40 PM
To: General discussion for Windows Installer XML toolset
Does anyone know where I can find the SQL2008 Express Merge Module? I have a
requirement to install a local database, and have been unable to locate a way
to include the SQL2008 Express in my installer. I have seen several other
products do this, so I know the capability exists...
Thanks,
As anyone successfully installed the office 2003 (or 2007) Primary Interop
Assemblies depending on which version of office is installed? I am afraid I am
struggling with this, and cannot seem to find how to integrate them both into
the bootstrapper, and have it choose what to install
Yes to the environment variable :-)
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Saturday, January 16, 2010 1:27 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Avoiding hard-coding the path to the WiX SDK when
using
Does anyone have any pointers towards using a setup.ini file for setting
parameters of an install?
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Thursday, January 07, 2010 1:52 PM
To: General discussion for Windows Installer XML toolset.
(Apologize for the previous off-topic email)
We actually did something similar to this using a 2nd build script. The first
build script build everything EXCEPT the installers, and then as the last step
of the build script, we executed the second build script to create the
installers
Are you saying that you are using two checkboxes to change the value of a
single Property?
-Original Message-
From: Igor Lemsky [mailto:igor.lem...@gmail.com]
Sent: Thursday, December 24, 2009 12:36 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users]
How do you detect if IIS6 or IIS7 are installed? Previously I was looking in
the registry, is there a better way?
This is how I was checking for IIS and ASP.NET 2.0, it is, however, broken with
IIS7 even with the IIS6 compatibility installed.
Condition Message=This setup requires the IIS
On a similar, but related note... Sascha, are you saying that you can have
multiple target directories for a merge module? I thought you could only have
the one merge reference path...
-Original Message-
From: Sascha Beaumont [mailto:sascha.beaum...@gmail.com]
Sent: Tuesday, December
I have not seen that problem, however, In our case we build Mixed Platforms
because we have some x86 specific code and some Any CPU code. What kind of
output do you seen in the build window? Is this during a build or a rebuild?
-Original Message-
From: Charles Mcdonald
Add this, maybe it will help in your case...
Condition Message=You must be an administrator to install this
application
Privileged
/Condition
I believe you get the UAC prompt...
-Original Message-
From: Sachin Dubey [mailto:sachin.du...@live.com]
Sent: Tuesday, November
I had had to hunt down how to correct the 'No HomeSite attribute has been
provided' errors when creating a bootstrapper.
(the solution was to add ToolsVersion=3.5 to the project definition line so
you end up with a line like this in the WixProj:
Project DefaultTargets=Build
This will tell you if 3.5 is installed
!-- Installation Conditions --
PropertyRef Id=NETFRAMEWORK35 /
Condition Message=The .NET Framework 3.5 must be installed
([NETFRAMEWORK35])
Installed OR NETFRAMEWORK35
/Condition
Condition Message=You must be an administrator to
discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] ToolsVersion attribute
John H. Bergman (XPedient Technologies) wrote:
I am curious why WiX does not add this attribute by default?
WiX doesn't require MSBuild 3.5.
--
sig://boB
http://joyofsetup.com
Has anyone used Setup.ini to configure the public properties of an install? I
am having some difficulty getting this to work.
I am using a bootstrapper that installs .NET 3.5SP1, and then an MSI that has
public properties deailing with things like Server names, user accounts, etc.
I cannot
the location of the INI file in such a way as to
enable using the IniFileSearch element. Easiest may be to have your
bootstapper supply a property to the MSI with the INI file's location.
-Original Message-
From: John H. Bergman (XPedient Technologies)
[mailto:john.berg
has some elements to deal with ini files. See more in Wix
toturial. There are some examples which include ini file operations.
More At http://www.tramontana.co.hu/wix/lesson1.php#1.5
Good luck.
2009-11-13
salever.lee
发件人： John H. Bergman (XPedient Technologies)
发送时间： 2009-11-13 02
I was just curious if there was an easier way of installing PDBs? What I have
works, but it seems cumbersome.
Component Id='c_AppServer.DTO' Guid='...'
File Id='f.AppServer.DTO'
Name='$(var.Application.ApplicationServer.DTO.TargetFileName)'
Ok, that's much better.
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Monday, November 09, 2009 10:16 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Installing PDBs
John H. Bergman (XPedient Technologies) wrote:
I was just
Do you see the Wix Project types in the Add New Project?
If not, Votive did not install. There was a post a while ago on the list about
manually installing the templates that would take care of it. We had a
similar problem where the 64bit version would not install (3.5.1030) fully on
some
When I add a User element inside my installers component, as such, I receive a
Fatal Error during uninstall, even if I do not use the user within the install.
Component Id='component_Service' Guid=4ADD096A-CF39-454b-AF01-1EA39092C9DB
DiskId='1'
util:User Id ='appServiceAccount'
]'
util:GroupRef Id='IISAppPoolGroup'/
/util:User
/Component
The install works perfectly (as does the one below).
Can someone please point me in the right direction?
-Original Message-
From: John H. Bergman (XPedient Technologies)
[mailto:john.berg...@xpedienttechnologies.com
=$(ApplicationUrl)
BootstrapperItems=@(BootstrapperFile) ComponentsLocation=HomeSite
OutputPath=$(OutputPath) Culture=en-US Path=$(SDKPath)Bootstrapper\ /
-Original Message-
From: John H. Bergman (XPedient Technologies)
[mailto:john.berg...@xpedienttechnologies.com]
Sent: Friday, October 30, 2009
I have looked high and low, I cannot seem to locate what I need to install to
get the bootstrapper files. That would be the files that is present in
C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper.
Anyone know what I need to download? I have VS2008 SP1 installed, I have tried
the
/2008?
-Original Message-
From: John H. Bergman (XPedient Technologies)
[mailto:john.berg...@xpedienttechnologies.com]
Sent: Friday, October 30, 2009 8:46 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Where do you get the Microsoft Bootstrappers?
I have
Does anyone know of a workaround to get the 32bit version working?
Besides applying a couple workarounds to the wxs files, the x64 version is
working quite well; however, we are now faced with only some developers can
move because the 32 bit version does not install completely.
Basically, we
I am finally able to build my installers with VS2010!
There are still a few workaround I have had to employ, but this is a much
better release for us than the last couple!!
One such workaround is that the ProjectDir appears to be mapped to the
TargetDir now, is this intentional, or is this a
VS2010 integration is back (thanks).
However, I still am getting an error 'GetResolveReferencePaths' when an Install
references a MergeModule.
The error is as follows:
error MSB4057: The target GetResolvedReferencePaths does not exist in the
project.
Has anyone been able to successfully
The latest build, and the previous one are missing the VS2010 integration.
Could one of the Wix Developers contact me offline so I can help with this?
--
Let Crystal Reports handle the reporting - Free Crystal Reports
It would appear that the Visual Studio 2010 integration is again missing from
WiX 3.5.0724.
Is there a way to manually install it?
Additionally, Bug #2803058 is not only Libraries but also MergeModules. I was
not able to update it,
nor do I think it should be a separate issue.
Ondrej, How did you validate the 3rd party merge module?
-Original Message-
From: Ondrej Zarevucky [mailto:ondrej.zarevu...@fine.cz]
Sent: Tuesday, July 28, 2009 8:06 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] problem with ICE82 - duplicate sequence
http://sourceforge.net/tracker/?func=detailaid=2803058group_id=105970atid=642714
Anyone have a target as to when this will get fixed; or if someone would point
me to where the problem likely is I am more than happy to have a go at it.
This not only affects Libraries, but also Merge Modules.
...@joyofsetup.com]
Sent: Thursday, July 09, 2009 6:26 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WiX 3.5.0626 missing VS2010 Project Types?
John H. Bergman (XPedient Technologies) wrote:
.Management.Client.wixproj : error MSB4057: The target
GetResolvedReferencePat
, 2009 6:26 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WiX 3.5.0626 missing VS2010 Project Types?
John H. Bergman (XPedient Technologies) wrote:
.Management.Client.wixproj : error MSB4057: The target
GetResolvedReferencePat
hs does not exist
]
Sent: Saturday, July 04, 2009 2:20 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WiX 3.5.0626 missing VS2010 Project Types?
John H. Bergman (XPedient Technologies) wrote:
I can live with using an older version, but I am struggling with the MSM
references
development right now and Votive is
not necessarily stable.
John H. Bergman (XPedient Technologies) wrote:
I just installed WiX 3.5.0626 and do not have the WiX project types with
Visual Studio now. Does anyone know what happened? The 3.5.0605 has them in
place, but every build after
]
Sent: Friday, July 03, 2009 2:49 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WiX 3.5.0626 missing VS2010 Project Types?
Sounds like a bug. WiX v3.5 is under development right now and Votive is
not necessarily stable.
John H. Bergman (XPedient Technologies
I receive this error for each of the MergeModules my install projects
reference. I have been unable to find any information as to what the cause of
this could be. Does anyone have any suggestions as to what this might be?
Error 391 The target GetResolvedReferencePaths does not exist in
You have to convert the project by hand.
Basically what I did was create another project, and then I believe you can
simply copy the other files in. Once you have done one, you can diff the old
and the new, there are only a few minor changes between them.
-Original Message-
From: Erik
I just installed WiX 3.5.0626 and do not have the WiX project types with Visual
Studio now. Does anyone know what happened? The 3.5.0605 has them in place,
but every build after that does not.
John
--
?
--
John H. Bergman (XPedient Technologies) wrote:
util:XmlFile Id=ModifyPluginDir_Client
Action=setValue
File=[WPFClient]app.config
I am getting this error:
Failed to find node:
/configuration/PluginSources/add/@key='Client' in XML File:
C:\Program Files\XPedient\WPFClient\\app.config
System error: -2147467259
The error implies some sort of access issue with the file, am I
for Windows Installer XML toolset.
Subject: Re: [WiX-users] WiX 3.0.4805.0: Internal MSBuild Errors
John H. Bergman (XPedient Technologies) wrote:
After I reproduced it in Visual Studio 2008, I exited and ran msbuild as
suggested.
The command line msbuild builds correctly.
I opened Visual
XML toolset.
Subject: Re: [WiX-users] WiX 3.0.4805.0: Internal MSBuild Errors
John H. Bergman (XPedient Technologies) wrote:
I have already upgraded to the latest release (4917).
OK. Can you build the .wixproj via MSBuild from a command line, not within
Visual Studio?
--
sig://boB
http
MSBuild Errors
John H. Bergman (XPedient Technologies) wrote:
It is not as simple as building an individual wixproj.. I am more than happy
to assist troubleshooting, however, because it appears to be an exception
being thrown, it would seem that attaching to the process and catching all
:52 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WiX 3.0.4805.0: Internal MSBuild Errors
John H. Bergman (XPedient Technologies) wrote:
How would you do that?
From a VS2008 command prompt, run 'msbuild foo.sln' -- should be the same as
build in the IDE
not be a wix/votive problem at all but have no way to prove
this. If I can be of any help to gather additional data please let me know.
--
Edwin
-Original Message-
From: John H. Bergman (XPedient Technologies)
[mailto:john.berg...@xpedienttechnologies.com]
Sent: Thursday, January 22, 2009
of
the source that is infected first.
--
Edwin
-Original Message-
From: John H. Bergman (XPedient Technologies)
[mailto:john.berg...@xpedienttechnologies.com]
Sent: Thursday, January 22, 2009 7:38 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users
-Original Message-
From: John H. Bergman (XPedient Technologies)
[mailto:john.berg...@xpedienttechnologies.com]
Sent: Thursday, January 22, 2009 7:38 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WiX 3.0.4805.0: Internal MSBuild Errors
Edwin
H. Bergman (XPedient Technologies) wrote:
I am having a problem with the 3.0.4805.0 release. On one of my machines, I
am getting build errors that are related to WiX. If I load my solution, with
the series of MergeModules and Installs, I get the output (included below).
Somebody already
61 matches
Mail list logo
