There's an example for an online based installation here:
http://msdn.microsoft.com/en-us/library/aa367817(VS.85).aspx
It might be a good place to start.
Rob
Sean Farrow wrote:
Hi:
Is there currently a way within windows installer/wix to allow a user to
mark a component/feature downloadable
I don't understand... and where are the definitions of this dialogs?
Btw, Kelly, in your original post you wrote:
DefineConstants=$(BuildDefineConstants);WixUIBannerBmp=Setup\bannrbmp.bmp;WixUIDialogBmp=Setup\dlgbmp.bmp;WixUILicenseRtf=Setup\License.rtf
So where were these constants
Hi All,
I have a simple question.
If i make Component`s GUID attribute to (empty string) and Parmanent
attribute to yes. Does this means this perticular component will be
completly unmanaged and there are not going to be any trace of this
component at all in registry.
in other way, this
Hi, Bob.
Custom action Custom Action='BackupFiles'
Before='InstallFiles'![CDATA[F_Online=3]]/Custom will perform whenever
the feature F_Online is selected to install. Try include in your condition
this: (Not Installed). It should look like this:
Custom Action='BackupFiles'
Hi Denis,
I got this from these two links. If you read the rist link its someone
having this issue and second link explains how can we use Feature as a
refrence in condition.
http://osdir.com/ml/windows.devel.wix.user/2005-01/msg00047.html
We have some old wix code that is still built on Wix 1.0. What steps do i
need to go through to upgrade this to Wix 3.0?
Thanks!
-Tina
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the
Hi All,
I am trying some thing similar. What i am trying to do is I have one file
which i have included in my msi and i am copying it in Temp Folder using a
component which is getting called in my main feature element
Directory Id=TempFolder SourceName=Temp
Component
One way would be to use Dark against your built deliverable.
WiXCop is documented to take WiX 2.0 to WiX 3.0...
http://www.wixwiki.com/index.php?title=WixCop
WiX 1.0 was so long ago (for me), I can't remember much about it... :)
From: [EMAIL
Denis,
WixUIExtension is where the WiX builtin UI is provided. I am reusing most
of the 'InstallDir' UI mode from WiX's builtin extensions. The properties
I'm defining are supposed to be the extension points for that library in
order to replace it's builtin stuff with your own. that's the
Hello All,
Small and minor upgrades cannot be run simply by clicking on the .msi
file, Wix Tutorial recommends using a setup.exe to launch it which
includes this command
msiexec /i setup.msi REINSTALL=ALL REINSTALLMODE=vomus
Could anyone give me a good reference about
That's exactly why I don't use WIXUIExtension. Instead I use my own UI. I find
the canned stuff too nauseating to customize for my own use. It's great if you
don't work outside the box, though.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kelly Leahy
The Setup.exe can be written in many languages. The one I've chosen is
Delphi. This allows us to AutoRun the Setup.exe from CD/DVD without
worrying about C# runtime libraries being needed, etc.. This Setup.exe
reads from a Setup.config XML file. The XML file is what holds the
command line that we
I should also point out the [SITE_ID] property comes from a custom
dialog in my installer.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chad
Petersen
Sent: Wednesday, September 17, 2008 9:14 AM
To: General discussion for Windows Installer XML toolset.
I suppose there could be a WiX issue somewhere. I think I've seen some
difficulties people have had with directory search. You could look in the MSI
file to see if the AppSearch and Signature data look correct, and if there's a
difference between the two MSI files generated by the different WiX
You got it correctly Bhavdeep, yes i was thinking the same way that i have to
keep this in a seperate feature.
But how can i define the InstallExecuteSequece to run it before any thing
else kick off.
Thanks,
Vivek
BOB1981 wrote:
HI Vivek,
Let me understand , are you trying to run your
You got it correctly Bhavdeep, yes i was thinking the same way that i have to
keep this in a seperate feature.
But how can i define the InstallExecuteSequece to run it before any thing
else kick off.
Thanks,
Vivek
BOB1981 wrote:
HI Vivek,
Let me understand , are you trying to run your
Hi Vivek,
What actually you are trying to do is to run your custom action After
InstallFiles but only after one feature. The way i have seen until now is
either we can run custom action Before InstallFiles system action is complete
or After InstallFiles system action is complete. You want
Get Orca. That way you can LOOK at the sequence of ALL actions without
having to even run the install and log anything. Huge time saver.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bhavdeep
Singh
Sent: Wednesday, September 17, 2008 10:22 AM
To:
But he doesn't *say* he's trying to get the buffersize, he says he's trying to
get the CustomActionData property, and also seems confused by the more data
error, which tells me he probably isn't trying to get the size. This is why
seeing the rest of the code would help.
Phil Wilson
Thanks for your response, but i am having a hard time fitting this custom
action in between two features.
I checked my Action sequence with Ocra but it doesn't tells me any thing
about sequence of installing a feature. can you please provide me some
example.
Thanks,
Vivek
Chad Petersen wrote:
I have a msp patch and msi minor pgrade processing result where a specific
app.config file setting which has underwent some miner content changes in the
v1.1 release is not getting updated.
If I diff my v1.0 target adminInstall and my v1.1 update adminInstall used to
by the old msimsp patch
I could be wrong, but I don't think there is any support in MSI for what
you are trying to do. What makes you believe this is possible?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Vivek
Sent: Wednesday, September 17, 2008 12:35 PM
To:
I was under the impression that InstallFiles is a single discrete action and
can not be broken down per-file. I don't think what you're trying to do is
possible with your current approach. Instead, I would consider putting your
CA in the Binary table rather than explicitly installing it on the
Hi Francis,
May be my approach is wrong as i am a newbie with Wix with no prior
experience on Install Shield.
What i am trying to do here is we have some users that are using a msi
(created with Install Shield) and we are replacing this old msi with the new
one which we are creating with Wix.
I'm not Francis, but have a thought for you.
Why not have your new MSI remove the older InstallShield MSI using the
Upgrade element? It's built in. I always opt for built in features
before using anything custom if it is available. Don't make things
harder than they are.
-Original
Thanks Chad, but i am running this msi under too many different scenario's
1) If the user is installing by his own i want to preserve some registry
settings (I do not want this cleanup thing to run in this case.
2) If we are pushing the install from the server using:
msiexec /i myapp.msi
Then, it sounds to me like you will want to expand you Custom Action
script itself to not only run the clean up, but also copy the file onto
the system you use for the clean up. That should do it. But, no way to
copy one Feature, do some Custom Action and then copy another Feature,
that I'm aware
Hi,
Can we do install a MSI remotely. Suppose I am running my MSi from Machine A
but this should be install on Machine B( all binaries etc in Machine B
programfile folder).
Can we do this kind of installation.
Regards
Sandeep
Hi,
I'm trying to use the built in wix support (Permission element inside
CreateFolder element) that would set the ACLs for the accounts specified.
Something like below. However, when installing the component, security rights
are not modified for the folder.
Any thoughts on what are some
Administrators is a Group, not a User. Don't you want Administrator
(singular)? I found this feature to be less than reliable so we set all
permissions on a generic level and then have the end user set the
permissions that they really need outside of the installer. Besides,
it's usually some
Here is what I'm now using to accomplish this w/o needing a setup.exe wrapper,
e.g. you can just double click the msp and/or msi. Initial knowledge share
for the double click msp property settings solution this came from John
Nannenga.
!-- for msp small update or minor upgrade processing
That's was it. I had had one test build of my patch where it tested it doing
a v1.0 to v1.1 minor upgrade where the v1.1 wix had introduced a ServiceControl
entry. I used hyper-v snapshot to roll back to prior that msp patch minor
upgrade test pass and removed the v1.1 wix that had
After some additional trial and error investigation what appears to be
happening here is that component files that get modified by util:XmlFile
settings will not get updated by msp small update or minor upgrade processing.
The only way I could get the file to be updated with the new file
I can't see any difference in MSI log built in WiX-3.0.4401.0 and
WiX-3.0.4513.0 (
http://n2.nabble.com/file/n1097284/install_WiX-3.0.4401.0.log
install_WiX-3.0.4401.0.log and
http://n2.nabble.com/file/n1097284/install_WiX-3.0.4513.0.log
install_WiX-3.0.4513.0.log ). Both AppSearch and
Romeo Salayo Jr. wrote:
I can't see any difference in MSI log built in WiX-3.0.4401.0 and
WiX-3.0.4513.0 (
It won't necessarily show in the log. Open both MSI packages in Orca and
check for differences between the two in the AppSearch, DrLocator, and
Signature tables.
--
sig://boB
Ran Didi wrote:
MsiGetProperty(hInstall, szName, TEXT(), nSizeCount); (gets nSizeCount ==
0 return ERROR_MORE_DATA), while i was trying to get the CustomActionData
property from the msi package.
The most likely cause is that the CA data wasn't set correctly in the
immediate CA.
--
Sandeep Gautam (HCL Technologies Ltd) wrote:
Can we do install a MSI remotely. Suppose I am running my MSi from Machine
A but this should be install on Machine B( all binaries etc in Machine B
programfile folder).
MSI installs on the local machine. You can use other tools like PsExec
Greg Silin wrote:
I'm trying to use the built in wix support (Permission element inside
CreateFolder element) that would set the ACLs for the accounts specified.
Something like below. However, when installing the component, security
rights are not modified for the folder.
Check a
It works now... I removed the Depth parameter. Now it looks like:
Property Id=WSH_VERSION
DirectorySearch Id=AppFile1 Path=[SystemFolder]
FileSearch Id=AppFile1 Name=wshom.ocx MinVersion=5.0.0.0
MaxVersion=9.9.9.9 /
/DirectorySearch
/Property
Before it works even it
39 matches
Mail list logo
