Re: [WiX-users] Problems with copy file

> From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Richard > Sent: Friday, October 19, 2007 11:35 PM > > In article > <[EMAIL PROTECTED]>, > "Jeremy Farrell" <[EMAIL PROTECTED]> writes: > > > Then, assuming the documentation's correct, it needs to be > > set to a property

Re: [WiX-users] Problems with copy file

In article <[EMAIL PROTECTED]>, "Mike Menaker" <[EMAIL PROTECTED]> writes: > How would I do this? > > Path is set by the user like this from the UI: > > > Property="PATH"> > > It seems like I would just keep running into the problem of combining > the property with a string. Add

Re: [WiX-users] Problems with copy file

In article <[EMAIL PROTECTED]>, "Jeremy Farrell" <[EMAIL PROTECTED]> writes: > Then, assuming the documentation's correct, it needs to be set to a property which contains the required path as the doc says. In > > DestinationProperty="PATH" > > which works, you've set it to the name of

Re: [WiX-users] Problems with copy file

How would I do this? Path is set by the user like this from the UI: It seems like I would just keep running into the problem of combining the property with a string. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeremy Farrell Sent: Friday, October 1

Re: [WiX-users] Problems with copy file

Then, assuming the documentation's correct, it needs to be set to a property which contains the required path as the doc says. In DestinationProperty="PATH" which works, you've set it to the name of the property called PATH which contains a pathname. You need to create a property which cont

Re: [WiX-users] Problems with copy file

According to the Wix Documentation DestinationProperty String Set this value to a property that will have a value that resolves to the full path of the destination directory. The property does not have to exist in the installer database at creation time; it could be created at install

Re: [WiX-users] Problems with copy file

In article <[EMAIL PROTECTED]>, "Mike Menaker" <[EMAIL PROTECTED]> writes: > Source=3D"$(var.SOURCEPATH)\ \"> > DestinationLongName=3D"file.txt" DestinationProperty=3D"[PATH]\dir\" /> >=20 > > If I use DestinationProperty=3D"PATH" it works. > > I have also tried Desti

[WiX-users] Problems with copy file

Hi, I can't get copyfile to copy a file. Here is the element I use (PATH is a property set earlier) If I use DestinationProperty="PATH" it works. I have also tried DestinationProperty="PATH\dir\" What am I doing wrong? Thanks, Mike ---

Re: [WiX-users] example Wix project

In article <[EMAIL PROTECTED]>, hina1703 <[EMAIL PROTECTED]> writes: > Yes, I did. It is very helpful. I am trying to find out any bigger WIX > project available for study including bootstrapper & other functions. I am working on converting the installer for the sample code for my book, but

Re: [WiX-users] Shortcut Targets and Shared Components

In article <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> writes: > So I have a component (in a separate fragment) that installs a file and > adds a shortcut on the Program Menu. That component is used in 2 > features. However, when I open the compiled msi file in Orca and look > at the Shortcut

Re: [WiX-users] example Wix project

Yes, I did. It is very helpful. I am trying to find out any bigger WIX project available for study including bootstrapper & other functions. Hina Richard-45 wrote: > > > In article <[EMAIL PROTECTED]>, > hina1703 <[EMAIL PROTECTED]> writes: > >> Is there any example Wix project available

[WiX-users] Shortcut Targets and Shared Components

Hello all, I was just wondering if the was a bug or not: So I have a component (in a separate fragment) that installs a file and adds a shortcut on the Program Menu. That component is used in 2 features. However, when I open the compiled msi file in Orca and look at the Shortcut Table, on

Re: [WiX-users] example Wix project

In article <[EMAIL PROTECTED]>, hina1703 <[EMAIL PROTECTED]> writes: > Is there any example Wix project available which shows the installation of > an executable e.g. adobe reader Did you look at the tutorial? -- "The Direct3D Graphics Pipeline" -- Direc

[WiX-users] example Wix project

Hi, Is there any example Wix project available which shows the installation of an executable e.g. adobe reader if the registry key is missing? I need to investigate WIX to find out if it can be our installation tool. Currently we use InstallShield, & I need to give demo with a sample project to g

Re: [WiX-users] Changing the text in the UI

Sorry this can be ignored. I found the file. In case anyone else has the same question, it is WixUI_en-us.wxl 0x001A4 wrote: > > I can't seem to find the area where I can change the various texts in the > UI. For instance, I would like to change the title on some of the screens. > This what I se

[WiX-users] Changing the text in the UI

I can't seem to find the area where I can change the various texts in the UI. For instance, I would like to change the title on some of the screens. This what I see in the element: Where do I find loc.ExitDialogTitle and edit the text? I know I can change Text="" to whatever I want, but I'd rat

Re: [WiX-users] Adding Bootstrapper code to wxs file. (Somebody, please guide....)

Yep... definitely shouldn't be moving built-in files like msbuild.exe. Lots of bad things can happen as most of those sorts of tools assume they are in a particular location when you're using them. Better to qualify your path to the file or use the windows path to get a reference to it via batc

Re: [WiX-users] Adding Bootstrapper code to wxs file. (Somebody, please guide....)

Yes. I copied MSBuild.exe from C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727 to C:\WIX\Test_Dot_NET for building purpose. Thanks, Hina John Vottero wrote: > > Is that all the diagnostic output? The "Initial Properties" section > seems to be missing. > > Did you move or copy the MSBuild.e

Re: [WiX-users] Path to MSI?

The OriginalDatabase is sometimes a reasonable alternative, but it has its own pitfalls too. The key issue is whether you want it in all circumstances (uninstall, repair, modify) or only at first install. In particular, OriginalDatabase works before any implicit ResolveSource in the first install.

Re: [WiX-users] Detecting processor model

In article <[EMAIL PROTECTED]>, jrcolons <[EMAIL PROTECTED]> writes: > How can I get those variables passed to my wix script? You can access environment variables from a Formatted string using [%envarname] syntax. You can use a type 51 CA to set a property to the value of an environment va

Re: [WiX-users] Path to MSI?

Thanks Richard, SourceDir works perfectly for me; but thanks for pointing out the pitfalls. Regards, R. - Original Message - From: "Richard" <[EMAIL PROTECTED]> To: "WiX Users" Sent: Friday, October 19, 2007 3:08 PM Subject: Re: [WiX-users] Path to MSI? > > In article <[EMAIL PROTE

Re: [WiX-users] Detecting processor model

How can I get those variables passed to my wix script? Tony Hoyle wrote: > > Alexei Boukirev wrote: >> Windows NT 4 and above have several environemnt variables that you can >> check in MSI: >> PROCESSOR_IDENTIFIER, PROCESSOR_LEVEL, and PROCESSOR_REVISION. >> So Pentium II on one of my deskto

Re: [WiX-users] Adding Bootstrapper code to wxs file. (Somebody, please guide....)

Is that all the diagnostic output? The "Initial Properties" section seems to be missing. Did you move or copy the MSBuild.exe executable? If so, don't. It looks for other files (like *.task) in the same location as the executable. > -Original Message- > From: [EMAIL PROTECTED] [mailto:

Re: [WiX-users] Custom Actions.

Did you use dark to reverse engineer the previous MSI? Also, if you are iterating through a directory during the install, you'd have to schedule this custom action to run deferred. Otherwise, the files won't be present at the time it runs. I use the following command to pass a directory to a exe

Re: [WiX-users] Path to MSI?

In article <[EMAIL PROTECTED]>, Sebastian Brand <[EMAIL PROTECTED]> writes: > Using the [SourceDir] property? :-) SourceDir is only correct after you call ResolveSource. Calling ResolveSource can require that the original media be present. This is problematic for upgrades and patching, be

Re: [WiX-users] Path to MSI?

In article <[EMAIL PROTECTED]>, "Rad Ricka" <[EMAIL PROTECTED]> writes: > what's the most effective way to programmatically get the path to where = > my MSI is being run from? What's the goal? What problem are you trying to solve by getting the path of the MSI? -- "The Direct3D Graphics P

Re: [WiX-users] Custom Actions.

Hi Dana, The custom Action i'm calling, actually gets a list of files with an extension of ".DIN" & ".DSE" from the directory where our product has been installed to. These define the Keyboard for our application, and a session file, the user can change these during the install, this is why it is

Re: [WiX-users] Adding Bootstrapper code to wxs file. (Somebody, please guide....)

Here is the diagnostic output: Initial Items: BootstrapperFile Microsoft.JSharp.2.0 Microsoft.Net.Framework.2.0 Microsoft.Sql.Server.Express.1.0 Microsoft.Windows.Installer.3.1 Target "Bootstrapper" in file "C:\WIX\Test_Dot_NET\Bootstrapper.xml": MSBUILD : warning MSB4010: The

Re: [WiX-users] Custom Actions.

What does the msi log say is happening here? That is usually the best way to troubleshoot custom action errors. The other trick I'll use is pop up a message box from my custom action code and then attach to it with the debugger. As a rule, any custom actions that modify the target system should

[WiX-users] Custom Actions.

Hi all. I'm having some trouble with parsing information to a custom action. I have the command: and the lines NOT Installed I don't know about the "[ALLUSERS]" but I know it is not parsing the "[INSTALLDIR]" parameter to the EXE, this EXE sets up all the windows registry settings

[WiX-users] FilePath manipulation in WIX

Hi, I can do a registrysearch and obtain a path like : D:\Program Files\Microsoft Office\OFFICE11\ADDINS\OTKLOADR.DLL Once I have this path I want to split it in directory (D:\Program Files\Microsoft Office\OFFICE11\ADDINS) and file (OTKLOADR.DLL) and then use it in directorysearch and file

Re: [WiX-users] HI WIX 3.0 FileShare question

This is what I was trying but it didn't work. It creates the physical folder named "[BLA]" in the InstalledDIR and creates the file-share on it. It does not create the D:\Share1 folder but creates a folder named "[BLA]". Thanks, -Krishna Krishna Sapkota | Software Design Engineer | Solutions

Re: [WiX-users] Path to MSI?

Using the [SourceDir] property? :-) Best regards, Sebastian Brand Instyler Software - http://www.instyler.com On Oct 19, 2007, at 10:10 AM, Rad Ricka wrote: > Hello, > > what's the most effective way to programmatically get the path to > where my MSI is being run from? > > Cheers, > > R. > -

Re: [WiX-users] HI WIX 3.0 FileShare question

I'm not sure if this works, but give it a try: You can create a new Directory element: .../> and call the msi (using msiexec) with the parameter BLA=D:\Share1 The location of the new Directory may be anywhere as the BLA property is passed with a full path. Best regards, Sebastian Br

[WiX-users] Path to MSI?

Hello, what's the most effective way to programmatically get the path to where my MSI is being run from? Cheers, R.- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. N

Re: [WiX-users] HI WIX 3.0 FileShare question

Hi Sebastian, Thank you very much for the response. I am using following code snippet for creating file-share: .

Re: [WiX-users] HI WIX 3.0 FileShare question

What does your wix file look like? FileShare uses the component's directory. If you want to use different drives for the fileshares your structure must be correct. How do you get those E:\.. and D:\.. folders on the target system? Best regards, Sebastian Brand Instyler Software - http://