Бизнес-робот
Бизнес
робот

Темы:

Архив:

Каталог рекламы и объявлений

Ящик для предложений: sales@blogslov.ru

WiX-devs Digest, Vol 13, Issue 24

Send WiX-devs mailing list submissions to


To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/wix-devs
or, via email, send a message with subject or body 'help' to


You can reach the person managing the list at


When replying, please edit your Subject line so it is more specific
than "Re: Contents of WiX-devs digest..."


Today's Topics:

1. Re: Passing parameters to binary custom action (Adam Langley)
2. questions on procedure for submitting changes (Kevin Fischer)
3. Re: building WIX (Bob Arnson)
4. Re: questions on procedure for submitting changes (Bob Arnson)
5. Re: Passing parameters to binary custom action (Bob Arnson)
6. respirator (Anthony N. Correa)
7. professed (Hester E. Flanagan)
8. [ wix-Bugs-1743150 ] Can't use loc variable for DWORD
RegistryValue elements (SourceForge.net)
9. [ wix-Bugs-1743678 ] x64 compatibility (SourceForge.net)


----------------------------------------------------------------------

Message: 1
Date: Tue, 26 Jun 2007 10:28:10 +1200
From: Adam Langley
Subject: Re: [WiX-devs] Passing parameters to binary custom action
To:
Message-ID:
Content-Type: text/plain; charset=us-ascii

Thanks Bob,

Do you think it would be worthwhile trying to integrate it as an 'extension'
so that I can get XML schema validation, and a custom XML declaration
format?

-----Original Message-----
From: Bob Arnson [mailto:]
Sent: Tuesday, 26 June 2007 2:05 a.m.
To: Adam Langley
Cc:
Subject: Re: [WiX-devs] Passing parameters to binary custom action

Adam Langley wrote:
> I've just finished writing a C++ Custom Action to publish a report
embedded
> in the MSI to Microsoft SQL Server Reporting Services, over Web Services.
> I currently have the name of the report file entry in the Binary table
hard
> coded, but I want to be able to pass this value to my Custom Action from
the
> wix definition, so that I can call the custom action multiple times, to
> upload multiple files.
>

The simplest way is to use a property that the CA reads. The downside to
that is that you then need multiple custom actions to set that property
after each call to the "real" CA.

The best way, though a bit harder, is to store that data in a custom
table. The CA then reads each row in the table to get the data. WiX has
helper methods like WcaOpenExecuteView to run the query, WcaFetchRecord
to read each record, and WcaGetRecordString/Integer to read a field from
each record. Take a look at ReadXmlConfigTable in
src\ca\wixca\dll\XmlConfig.cpp for a sample.

--
sig://boB
http://joyofsetup.com/





------------------------------

Message: 2
Date: Mon, 25 Jun 2007 17:42:25 -0600
From: Kevin Fischer
Subject: [WiX-devs] questions on procedure for submitting changes
To:
Message-ID:
Content-Type: text/plain; charset="iso-8859-1"

I'd like to submit some code for review for the WIX project. I'm new to CVS, SourceForge, etc. so some of these are likely to be basic questions. I was able to get WinCVS working such that I've checked out the "wix" module onto my local machine. I have a few questions relating to this:- This appears to be an older version. I've downloaded the sources separately for v3 (build 3015) and they don't seem to match up with what CVS pulled down. I tried browsing CVS via the web interface, and it matches what I got via WinCVS, but not the source download for 3015. Am I pointing to the wrong server/module or something?- Once I resolve my version issues, how do I submit a set of files for code review? It appears that a Tracker is the preferred method. Is that correct? How do I package up my code changes to attach to a tracker? Thanks for any help. Kevin
_________________________________________________________________
Hotmail to go? Get your Hotmail, news, sports and much more! Check out the New MSN Mobile!
http://mobile.msn.com
-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

Message: 3
Date: Mon, 25 Jun 2007 20:33:36 -0700
From: Bob Arnson
Subject: Re: [WiX-devs] building WIX
To: Adam Langley
Cc:
Message-ID:
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Adam Langley wrote:
> C:\Users\Adam\Downloads\Microsoft\WIX\wix-3.0.2925.0-sources\wix.include(10,
> 4):
> Property evaluation failed.
> Expression: ${file.global.include}
> ^^^^^^^^^^^^^^^^^^^
> Property 'file.global.include' has not been set.
>

There's something funky going on with the sources release at the SF
project site. I'd suggest grabbing the source .zip from
http://wix.sourceforge.net/releases/ instead. Run make.bat to get the
right properties set.

--
sig://boB
http://joyofsetup.com/





------------------------------

Message: 4
Date: Mon, 25 Jun 2007 20:43:41 -0700
From: Bob Arnson
Subject: Re: [WiX-devs] questions on procedure for submitting changes
To: Kevin Fischer
Cc:
Message-ID:
Content-Type: text/plain; charset="iso-8859-1"

Kevin Fischer wrote:
> - This appears to be an older version. I've downloaded the sources
> separately for v3 (build 3015) and they don't seem to match up with
> what CVS pulled down. I tried browsing CVS via the web interface, and
> it matches what I got via WinCVS, but not the source download for
> 3015. Am I pointing to the wrong server/module or something?

No, it looks like it hasn't gotten updated recently. Sorry for the
earlier misdirect -- it looks like using the sources .zip is right approach.

> - Once I resolve my version issues, how do I submit a set of files for
> code review? It appears that a Tracker is the preferred method. Is
> that correct? How do I package up my code changes to attach to a tracker?

First step is to get an assignment agreement. Rob's MSDN blog is down
but I believe the trick is to e-mail to start the
process. Then open a bug or feature request and attach the changes. You
can use a patch-making tool or just attach a .zip file of the changed files.

--
sig://boB
http://joyofsetup.com/

-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

Message: 5
Date: Mon, 25 Jun 2007 19:54:42 -0700
From: Bob Arnson
Subject: Re: [WiX-devs] Passing parameters to binary custom action
To: Adam Langley
Cc:
Message-ID:
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Adam Langley wrote:
> Do you think it would be worthwhile trying to integrate it as an 'extension'
> so that I can get XML schema validation, and a custom XML declaration
> format?
>

Absolutely. That's the easiest way to get well-formed data into custom
tables.

--
sig://boB
http://joyofsetup.com/





------------------------------

Message: 6
Date: Tue, 26 Jun 2007 16:54:21 +0530
From: Anthony N. Correa
Subject: [WiX-devs] respirator
To:
Message-ID:
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

SREA Takes Investors For Second Climb! UP 40%.

Score One Inc. (SREA)
$0.42 UP 40%

SREA continues another huge climb this week after hot news was released
Friday. BusinessNewsNow.us has released SREA as featured StockWatch.
This one is still cooking. Go read the news and get on SREA Tuesday!

While you're researching, you should take a look at calorie restriction
diets as an option.

This research is fundamental to the future of regenerative, life- and
health-extending medicine.

htmlFollowing up on Monday's article on deep divisions between
merchants, doctors and researchers, here's another good one from the
Seattle Times. This is a field that was moribund and near dead up until
very recently.

In brief, it is a prize for producing the world's longest-ever-lived
mouse.




------------------------------

Message: 7
Date: Tue, 26 Jun 2007 16:54:15 +0530
From: Hester E. Flanagan
Subject: [WiX-devs] professed
To:
Message-ID:
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

SREA Takes Investors For Second Climb! UP 40%.

Score One Inc. (SREA)
$0.42 UP 40%

SREA continues another huge climb this week after hot news was released
Friday. BusinessNewsNow.us has released SREA as featured StockWatch.
This one is still cooking. Go read the news and get on SREA Tuesday!

These are exciting times: we are very much at the beginning of the birth
of a new medical industry, one that will benefit all of us enormously.

Researchers are still trying to find a "grand unified theory" of aging,
so the more funded research the merrier.

You voice counts, so make yourself heard! They're vigorous and active.

Yet, people in positions of influence and power devote their time to
blocking research and speaking out openly against extended health and
life.




------------------------------

Message: 8
Date: Mon, 25 Jun 2007 14:23:41 -0700
From: "SourceForge.net"
Subject: [WiX-devs] [ wix-Bugs-1743150 ] Can't use loc variable for
DWORD RegistryValue elements
To:
Message-ID:
Content-Type: text/plain; charset="UTF-8"

Bugs item #1743150, was opened at 2007-06-25 14:23
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1743150&group_id=105970

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: light
Group: v3.0
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: ntgt13 (ntgt13)
Assigned to: Nobody/Anonymous (nobody)
Summary: Can't use loc variable for DWORD RegistryValue elements

Initial Comment:


gives the following error when linking:

C:\works10\setup\wix\StandardMsi\StandardComps.wxi(353) : error LGHT0204 : ICE70: The value '#!(loc.StandardComps-_C18625_AB)' is an invalid numeric value for registry entry Registry1110. If you meant to use a string, then the string value entry must be preceded by ## not #.

I think either this should be fixed or we should have some other way to localize DWORD registry entries.

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1743150&group_id=105970



------------------------------

Message: 9
Date: Tue, 26 Jun 2007 08:27:54 -0700
From: "SourceForge.net"
Subject: [WiX-devs] [ wix-Bugs-1743678 ] x64 compatibility
To:
Message-ID:
Content-Type: text/plain; charset="UTF-8"

Bugs item #1743678, was opened at 2007-06-26 09:27
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1743678&group_id=105970

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: votive
Group: v3.0
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Sean Reilly (sreilly-point2)
Assigned to: Justin Rockwood (justinrockwood)
Summary: x64 compatibility

Initial Comment:
When wix 3.0 is installed on a Windows XP Pro 64 bit, and used with (32 bit) visual studio 2005 sp1, attempting to build a wix project results in the following error:

Error 1 The specified task executable location "C:\Program Files\Windows Installer XML v3\bin\candle.exe" is invalid. C:\Program Files (x86)\MSBuild\Microsoft\WiX\v3.0\Wix.targets 1011 6 Installer

If I copy the contents of the Wix installation folder "C:\Program Files (x86)\Windows Installer XML v3" to "C:\Program Files\Windows Installer XML v3", then compiling a Visual Studio Wix project works as expected and a working msi is created.

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1743678&group_id=105970



------------------------------

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

------------------------------

_______________________________________________
WiX-devs mailing list

https://lists.sourceforge.net/lists/listinfo/wix-devs


End of WiX-devs Digest, Vol 13, Issue 24
****************************************

2007 26 июня