There was a request some time back to allow multiple resource filesets
against a cscTask to enable adding resources to multiple namespaces. To
get this working I finally implemented support for the
BuildElementArrayAttribute. This enables you do do the following :
[BuildElementArray( "resources
Title: GET PAID STUFFING ENVELOPES FROM HOME
GET
PAID STUFFING ENVELOPES FROM HOME
Right
now our mail order company is hiring homeworker like yourself, to help
us stuff our sales circulars into envelopes, helping us get ready for
upcoming busy season.
+1, Let's split and trim on the property attribute.
- Original Message -
From: "Matthew Mastracci" <[EMAIL PROTECTED]>
> It looks like a lot of places in the NAnt code use commas to separate
> multiple values. Perhaps:
>
>
---
Th
It looks like a lot of places in the NAnt code use commas to separate
multiple values. Perhaps:
?
Scott Hernandez wrote:
+1 on delim.
I don't think xml lets you have multiple attributes of the same name in the
same element. I'm fine with the idea of multiple properties per line, but
what wo
+1 on delim.
I don't think xml lets you have multiple attributes of the same name in the
same element. I'm fine with the idea of multiple properties per line, but
what would be a natural way to express this in valid xml?
- Original Message -
From: "Matthew Mastracci" <[EMAIL PROTECTED]>
T
While I'm at it, I wonder if we should put a "pattern" attribute on the
element of a FileSet. I'm using these to separate some
lists of files from the build scripts themselves, but it's nice to have
some documentation in the file list:
---
# This is the list of projects to build
folder/x/
Should we change the following lines in the LoopTask? Currently, the
string is split based on a single delimiter. Since String.Split()
supports a character array, we can remove the char array [0] indexer and
have it split on any character in the "delim" property. I can fix this
and check it
PICTURE THIS !!
AS SEEN ON NATIONAL TV:
Making over half million dollars every 4 to 5 months from your home? A
one time
investment of only $25 U.S. Dollars let's get you on the road to
financial success.
ALL THANKS TO THE COMPUTER AGE AND THE INTERNET !
===
--- Brian Deacon <[EMAIL PROTECTED]> wrote:
> Just wanted to pipe up and say that I personally am really interested in
> hearing any gotchas and resolutions in getting nant and mono to play
> nice with each other. So thanks, Philip.
Yeah, I had pretty much set aside my interest in Mono until NAn
Just wanted to pipe up and say that I personally am really interested in
hearing any gotchas and resolutions in getting nant and mono to play
nice with each other. So thanks, Philip.
Brian
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Philip
Nelson
Sen
Hey all, quick user question:
I'm using SLiNgshoT to generate the build off of the solution, then I'm running
through my own custom XSLT to add / remove / modify things that I want to
change. One issue that just cropped up was that we have ASP pages with the same
name, but are kept in separate di
A few people wrote about a bug that happens if you load a project without first
selecting a build file. Thanks! This version just dims the load button until a
file is selected. Amazing I never did that in over 8 months of use ;-)
I included only the .exe and source. To use, you will have to cop
WOULD YOU LIKE TO HAVE YOUR MESSAGE SEEN BY
OVER 15.4 MILLION OPT-IN, TARGETED PROSPECTS WEEKLY?
Below contains all the information you will ever need to market
your product or service on the Internet.
If you have a product, service, or message that you would like to get
out to Thousands, Hu
> hmm - well that registry code will be removed shortly. Its just to get
> the SDKFramework path I think.
exactly.
>
> >Can I assume that the registry won't be supported under
> > Mono?
> >
> I would have thought not. Considering its in the Microsoft.Win32
> namespace. And it definately won
Philip,
Trying to compile nant under mono. What I originally thought was an xml short
fall is actually a reflection shortfall:
has more than one match for
Anyway, the problem occurs trying to compile McsTask (and other times using
Mono with .net compiled assemblies). McsTask inherits from Compi
Trying to compile nant under mono. What I originally thought was an xml short
fall is actually a reflection shortfall:
has more than one match for
Anyway, the problem occurs trying to compile McsTask (and other times using
Mono with .net compiled assemblies). McsTask inherits from CompilerBase
16 matches
Mail list logo
