I have used volumecostList control in wix. When the control comes its full of
exclamation marks. The image is attached.
http://n2.nabble.com/file/n2191299/Untitled.jpg Untitled.jpg
--
View this message in context:
http://n2.nabble.com/question-on-volumecostList-control-tp2191299p2191299.html
I am using wix 2.0. I tried building with different wix versions and ended up
with the same problem. Can anyone please help me out?
skarthik_psg wrote:
I have used volumecostList control in wix. When the control comes its full
of exclamation marks. The image is attached.
Thanks for the information.
I have an application with more than 1000 files.
Even though the next version can have changes in several files, I want
to build patches for selected 2 or 3 files.
Since number of files to ignore is more I am not sure we can use the
solution of explicitly list files to
After setting culture for project that is using my library everything
works fine. Maybe anyone know how to build library with default
localization set up.
-Original Message-
From: Rob Mensching [mailto:rob.mensch...@microsoft.com]
Sent: Wednesday, January 21, 2009 1:02 AM
To: General
Wix 2.x is too old for using with VS 2008. In order to do that you
need to use Wix 3
On Wed, Jan 21, 2009 at 12:20 PM, Murtaza Chowdhury
murta...@microsoft.com wrote:
When I try to install Votive 2.0.5805.0 on Visual Studio 2008, I get the
following error message : WIX Toolset Visual Studio
Oh darn, well it seems that I maybe able to use the version number of
one of the files these chaps install, so maybe it won't be so bad after
all, Thanks Rob.
Simon
-
Message: 5
Date: Tue, 20 Jan 2009 10:38:10 -0800
From: Rob Mensching
When I try to install Votive 2.0.5805.0 on Visual Studio 2008, I get the
following error message : WIX Toolset Visual Studio Package requires the
Standard, Professional, or Team editions of Visual Studio; Express editions are
not supported.
I have the Team edition and not the express edition
Hello all,
Can I do anything to clearify the issue. Is it not supposed to work?
I am using WIX 3.0.4805.0, developing using Visual Studio 2008 with Votive
Thank you!
Jesper
jballe wrote:
Hello all,
I am writing my first complex setup using wix and managed custom actions
using c#.
We are currently developing a new product and would like to use WiX to
create our installer, but we still have some doubts about WiX usage. The
version of WiX in question is v3.
The problem is our installer does not make use only of WiX dialog sets
(WixUI_Mondo, WixUI_InstallDir and so on), but it
You can check these links
http://dizzymonkeydesign.com/blog/misc/adding-and-customizing-dlgs-in-wix-3/
http://blog.wharton.com.au/2007/06/windows-installer-xml-wix-30-snippets.html
http://www.wixwiki.com/index.php?title=Main_Page
http://www.tramontana.co.hu/wix/index.php
The last link would
Thanks, that was the problem. CData is case sensitive and i had CData instead
of CDATA after changing, it worked.
Arun Perregattur
-Original Message-
From: Peter Björkman [mailto:peter.bjork...@aptus.se]
Sent: Wednesday, January 21, 2009 1:57 AM
To: General discussion for Windows
From here
http://sourceforge.net/project/showfiles.php?group_id=105970package_id=16
Arun Perregattur
-Original Message-
From: sam desilva [mailto:sam.desilv...@gmail.com]
Sent: Wednesday, January 21, 2009 1:22 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] candle.exe
Hi,
I have created some WiX based installers for some services and a web
application I am working on at work. We use the installers as part of our
test rigs, so we patch our test changes, build the new version and install
it. Since this whole process is automated if the MSI determines it needs to
Hi!
Here's a page demonstrating how to customize the installation flow.
http://www.wixwiki.com/index.php?title=WixUI_Custom
http://www.wixwiki.com/index.php?title=WixUI_Custom
you should choose the UI sequence that fits your installer the most, get
it's stock sequence, copy and paste,
Hi All,
I have an install in which I have written custom actions using C# and
DTF. One of my custom actions that I have written is scheduled to
execute after RemoveFolders during uninstall only. It is not working as
expected, and when I debug into my custom action I find that the Session
Hi everyone
I have been trying to create a database by attaching a pair of mdf/ldf files. I
can't get it to work properly so I hope someone has an easy solution for this.
I have been using a SqlString element with a call to sp_attach_db but I am
getting problems. First I used the mdf
So it looks like I can set logging to verbose in WiX with this property:
Property Id=LOGVERBOSE1/Property
Is there a way in WiX to set the default logfile name, and have it be
created in the same folder as the .msi?
Thanks.
- Phil
That's because your problematic custom action is deferred. If you mark
it as immediate, you'll be able to access the Database property and read
the properties. In deferred actions you are supposed to use special
CustomActionData property to read the data from.
-- Yan
-Original Message-
Hi Yan,
Thanks for the reply. I do actually want the custom action to execute
deferred...that was intentional. However, your information the the
CustomActionData property is helpful.
Thanks,
A
-Original Message-
From: Yan Sklyarenko [mailto:y...@sitecore.net]
Sent: Wednesday,
I have recently managed to implement something similar for my installation. You
can find the whole story here:
http://ysdevlog.blogspot.com/2009/01/attach-detach-database-during.html
Also this mail archive contains a number of relative examples, for instance, in
this thread:
This property enables verbose logging in WiX custom actions. It writes
extra entries to the MSI log. See /src/ca/wcautil/wcalog.cpp in the
WiX sources for more details.
Take a look at MSI logging options running this command: msiexec /help
So, in order to have very verbose log for WiX-based
So I have this working from the command line already. What I want to do
is duplicate the effect of LOGVERBOSE=1 /l*v MyPackage.log without
having to provide it on the command line.
Essentially I want the package to default to verbose logging to file in
the same dir as the MSI with the name I
Trying to be tidy, I pulled out the CustomAction declarations relating
to a particular aspect of my install into its own .wxs file.
I have
Fragment
CustomAction...
CustomAction...
CustomAction...
InstallSequence
[...sequence the custom actions
Hey Jeremy,
In order to include code inside a fragment you must reference something.
From the below snippet you provided you could reference a single
CustomAction using
CustomActionRefhttp://wix.sourceforge.net/manual-wix3/wix_xsd_customactionref.htm/.
This will link in the rest of the fragment.
Sudhakaran, Suraj wrote:
Even though the next version can have changes in several files, I want
to build patches for selected 2 or 3 files.
Since number of files to ignore is more I am not sure we can use the
solution of explicitly list files to ignore in the
UpgradedFilesToIgnore table.
Jeremy Lew wrote:
Problem is, the InstallSequence seems to be ignored. I'm guessing that
this is because it's not referenced in the Product element, which lives
in a different file. How can cause InstallSequences defined in
fragments to be merged into the one in the Product? Is the only way
phillip_sid...@dellteam.com wrote:
So I have this working from the command line already. What I want to do
is duplicate the effect of LOGVERBOSE=1 /l*v MyPackage.log without
having to provide it on the command line.
On MSI 4.0 and later, you can use the MsiLogging and MsiLogFileLocation
Alexandr Naumuk wrote:
After setting culture for project that is using my library everything
works fine. Maybe anyone know how to build library with default
localization set up.
Wixlibs are collections of WiX objects; they don't have the concept of
default localization set.
--
sig://boB
Got it (thanks Brian too). Is that a general rule, if you reference
something in a fragment, the entire fragment is linked?
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Wednesday, January 21, 2009 11:42 AM
To: General discussion for Windows Installer XML
Yes, that is the general rule. It works well if you are building wixlib
files and only want to include what you NEED not everything that is there.
Brian Rogers
Intelligence removes complexity. - Me
http://icumove.spaces.live.com
On Wed, Jan 21, 2009 at 8:58 AM, Jeremy Lew
I also saw this behaviour. It would be nice to know why.
Rob
Improvize1 wrote:
I am setting system environment variable on a Windows Server 2003 system
using the WiX Environment element like so:
Environment Id=SetMyAppDir Action=set Name=MYAPPDIR
Value=[INSTALLLOCATION] System=yes /
I
skarthik_psg wrote:
I am using wix 2.0. I tried building with different wix versions and ended up
with the same problem. Can anyone please help me out?
You're missing rows in the UIText table. See
src\ext\UIExtension\wixlib\Common.wxs for how WixUI does it.
--
sig://boB
1. Looking at the fairly standard set of .Net and VB COM files I would
say these:
{62C8FE65-4EBB-45e7-B440-6E39B2CDBF29} - .NET Category
{40FC6ED5-2438-11CF-A3DB-080036F12502} - Automation Objects
{40FC6ED4-2438-11CF-A3DB-080036F12502} - Controls/Control
These seems to be
There is some information on customising the standard dialogs here:
http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html.
I use WiXEdit to create the dialogs: http://wixedit.sourceforge.net/. It
is a bit clunky but quicker than doing it by hand.
Neil
-Original
I would like to thank you all for the help and links. They will certainly
help us a lot. :)
On Wed, Jan 21, 2009 at 3:35 PM, Neil Sleightholm n...@x2systems.comwrote:
There is some information on customising the standard dialogs here:
Is the CustomAction deferred? If so, there are a lot of restrictions on
deferred CustomActions. The MSI SDK details this.
-Original Message-
From: Amy Rosewater [mailto:arosewa...@spectrumhr.com]
Sent: Wednesday, January 21, 2009 07:28
To: General discussion for Windows Installer XML
MSI verbose log file should point out the file being locked. Then you just
need to figure out how to get the thing to be unlocked. That's how Windows
works. It's perfectly sane, just not always very convenient. smile/
-Original Message-
From: Adam Burton
Sorry, no extra data for you. It seems like it should work.
-Original Message-
From: jballe [mailto:j...@visionpeople.dk]
Sent: Wednesday, January 21, 2009 03:42
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] CustomAction accessing CustomTable
Hello all,
Can I do
Hi,
Can anyone help me know if MsiGetProperty and MsiSetProperty are available to
use in C#? if yes! little guidance on how to use would help.
I have used these in C++ before, just wondering if possible in c#.
In C++:
uRetVal =
Hi,
I am working on adding prerequisite check dialog to the MSI, I have a List
View, where the List Items are all the software need to be checked.
My questions is how to dynamically change add/remove or change the icon of,
List Items on pass or failure of the prerequisite check.
In more easy
1. WiX provides no such dialog built in today.
2. DTF is a C# layer around the MSI APIs.
-Original Message-
From: Sachin Dubey (Tata Consultancy Services) [mailto:v-sad...@microsoft.com]
Sent: Wednesday, January 21, 2009 10:16
To: General discussion for Windows Installer XML toolset.
Hi,
I have a requirement to build an installer the does the following:
1 - the installer should read an appsettings value from a pre existing
web.config on the target machine.
2 - This value should then be used to edit a web.config file before
writing it, as a new file to the target
I posted a bug on this, but I got it classified as invalid, since you can
use CustomActionRef; as Bob wrote.
What I did was to include an empty ComponentGroup in the fragment, and a
reference to the component group from Product.wxs, this way I don't need to
set a CustomActionRef for every custom
Eitan Behar wrote:
What I did was to include an empty ComponentGroup in the fragment, and a
reference to the component group from Product.wxs, this way I don't need to
set a CustomActionRef for every custom action.
You don't need a CustomActionRef for every custom action, just one for
the
Sachin Dubey (Tata Consultancy Services) wrote:
Would be great if you can point me to any web reading on DTF, where I can
found the details of available APIs and there uses that can help be achieve
my gaols.
Every build of WiX includes DTF help file shortcuts on the Start menu.
--
Also, if you write your CustomActions to be data driven, you usually end up
with something else more natural that brings them in.
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Wednesday, January 21, 2009 11:15
To: General discussion for Windows Installer XML
Mmm, I was not aware of that, probably I didn't read the whole response to
the bug resolution 8^)
Well, in any case, when working with several Wixers, I prefer linking to a
dummy element and not to a real custom action, since that way I give 100%
flexibility to the wix fragment owner. But, well,
I don't know about that. I can understand why it gets the locks etc, but its
the releasing that seems to mess up for me, or behave in a manor I would not
except. For example the services I install ... why are files still locked when
the msi stops the service ... the service is the only thing
Rob,
Thanks For your prompt response. The code that you mention having to
write (read data, set properties...) what form does it take? (I can
write it in c#) but what should I be building? An wix extension? Is
there any tutorials on the subject?
Thanks,
Mordecai
-Original Message-
From:
Adam,
I suspect there is something more going on here. We have been following
a test deployment process like yours for several years for a suite of
large web applications, and the only time we have file lock issues is if
someone is actively testing (hitting the pages) when the upgrade occurs.
Michael,
Well yea that will be sorta the case. Some people will probably be in the
middle of using the site (if the poor souls are sad enough or getting close to
dead line to feel the need to work during lunch :-) ), not had chance to tell
it to send out a warning email yet ... although they
Adam,
I agree (and our experience bears it out), IIS reset should kill off any
thing that the web app is doing (actually we rarely even need to do
that. Unless is some of the web application code is in COM+, that can
have a life of its own.
Michael
-Original Message-
From: Adam Burton
It's been a while since I've touched Votive 2 code so my memory may be hazy,
but I don't think Votive 2 is supported under VS 2008. It's designed for VS
2003/2005. If you want to use VS 2008, I recommend upgrading to Votive 3.
Even if Votive 2 works under VS 2008, there has been so much added to
We have a large web site, too. With many services running beside IIS.
Any time we get locks I take a verbose log and search for in use and
it always tells me the process that has the file in use and I can make
some correction to take care of it. Never been a problem that could be
handled so far.
I've asked this before but haven't gotten a solid answer, so I'll try one
more time.
I need to be able to incorporate a modified form of the package version into
the .msi name.
What would be ideal would be the ability to reference the
!(bind.fileVersion.MyPackageEXE) as part of the output name,
::Rolls eyes and bows head:: oh I really hate COM it's always being
difficult with me lol. I hadn't thought about the COM stuff, we run it as a
server process so I bet that's still chilling out somewhere in the processes. I
bet that when I run a verbose log tomorrow it will confirm that.
You need to separate the WiX toolset from MSBuild in your mind. Treat the WiX
toolset the way you would treat csc.exe or vbc.exe or (actually more like)
cl.exe/link.exe. Anything written in the language being compiled is completely
contained within the compilation process. MSBuild (or NAnt
Well another poster pointed out COM which I forgot (/wishfully forgot :-) )
existed. Due to how we develop our COM, and some might say the stubbornness not
to change it (which I can sorta understand, it works so why change it), I am
having to manage the COM via custom actions, so if a COM
If we're building with Visual Studio (or devenv.exe) are we still using
msbuild under the hood?
On Wed, Jan 21, 2009 at 3:57 PM, Rob Mensching
rob.mensch...@microsoft.comwrote:
You need to separate the WiX toolset from MSBuild in your mind. Treat the
WiX toolset the way you would treat
Colin,
When you say setting the 'OutputName' field do you mean through the UI
or through manually editing the project file. Theoretically, you should
be able to edit this in the project file and it will work (using the
'$(xxx)' syntax), but the VS IDE doesn't let you do so through its own UI.
Adam,
Good luck!!
Michael
-Original Message-
From: Adam Burton [mailto:adz...@googlemail.com]
Sent: Thursday, 22 January 2009 9:53 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Prevent reboot.
::Rolls eyes and bows head:: oh I really hate COM it's always being
You'd need to build a CustomAction. A Class 2 CustomAction:
http://robmensching.com/blog/posts/2007/8/10/Zataoca-Classes-of-Custom-Actions.
I personally always recommend building CustomActions with the fewest
dependencies, so C/C++ statically linked to C runtime. That's what all the WiX
VS2008? Yes. VS2005? No, I think that was make.exe... but I'm not an expert
on the VS build systems. I find modifying build systems in VS to be painful
since there are so many tiny boxes to type data in and a weird split between
debug and release. shrug/
-Original Message-
From:
I am using Wix to create an application pool with an identity of a
custom account. When I do a major upgrade the application pool identity
is stuffed up although it should remain unchanged. The result is that
the application pool is stopped and I get Service Unavailable message
when I try to
Joe,
How is the Uninstall of the old product version scheduled in the
upgrade. My guess is that your update is uninstalling and then
installing the web pool and when it reinstalls it, it no longer has the
identity to use.
Michael
-Original Message-
From: Joe Osman
What version of the WiX toolset are you using?
-Original Message-
From: Joe Osman [mailto:joe.os...@tait.co.nz]
Sent: Wednesday, January 21, 2009 17:27
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Application pool identity is stuffed up on product upgrade
Has anyone seen this symtom before? Here is the scenario:
I am trouble shooting a failing install. In the debug process, I run the
install with DISABLEROLLBACK=1. When the failure happens, it is suppose
to NOT rollback. That way, I can figure out what isn't right. This has
worked before. For
I am using WIX 3.0.4617.0
The upgrade doesn't remove the identity. The application pool uses a
logon which cannot be removed by uninstalling the application. I
specifically set the logon to be RemoveOnUninstall=no, hence I am sure
that the logon (identity) exists when reinstalling the
Sachin Dubey (Tata Consultancy Services) wrote:
I am trying to update the listview table-
Can you please point me what's wrong with this:
Microsoft.Deployment.WindowsInstaller.View view = null;
view = session.Database.OpenView(UPDATE `ListView` SET `Binary` = 'Success'
WHERE `Property`
On Thu, Jan 22, 2009 at 2:56 AM, Rob Mensching
rob.mensch...@microsoft.com wrote:
VS2008? Yes. VS2005? No, I think that was make.exe... but I'm not an
expert on the VS build systems. I find modifying build systems in VS to be
painful since there are so many tiny boxes to type data in and a
John 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
skarthik_psg wrote:
Thanks for the reply but i am not using WixUI
I wasn't suggesting you use it, I was suggesting you could get the
UIText strings you need from it.
--
sig://boB
http://joyofsetup.com/
--
This
I have already upgraded to the latest release (4917).
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Thursday, January 22, 2009 12:26 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WiX 3.0.4805.0: Internal MSBuild Errors
John
73 matches
Mail list logo
