> So people send in your votes on these topics:
> 1. or
property-group
> 2. separator attribute or no separator attribute
no separator
---
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here fo
> So people send in your votes on these topics:
> 1. or
propertygroup
> 2. separator attribute or no separator attribute
no separator
---
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE
Shaw, Gerry wrote:
>>I think its a good idea. Howver the outer tag should probably be
>>
>>
> or somthing like that. I think the . seperator is fine.
>
>Do others feel strongly about this? I have it working with prefix="">. I like it being all in one task so that when the user reads
>
> I think its a good idea. Howver the outer tag should probably be
or somthing like that. I think the . seperator is fine.
Do others feel strongly about this? I have it working with . I like it being all in one task so that when the user reads
the docs for they understand everything about i
Shaw, Gerry wrote:
>What do people think of the following syntax for the task:
>
>
>
>
>
>
>
>To produce the following properties:
>
>win-vc7.cc
>win-vc7.lib
>win-vc7.link
>
>The idea is to reduce duplicate values of the build value.
>
>
This is almost the same as the namespace iss
What do people think of the following syntax for the task:
To produce the following properties:
win-vc7.cc
win-vc7.lib
win-vc7.link
The idea is to reduce duplicate values of the build value.
I've been using this locally for a while and find it really useful. Other
options w
