Title: Dear Friend
Dear Friend,
We would like to introduce ourselves
Creativeskulls, We are a new media concern having a setup of 11 high end
workstations. We are looking for business partners/clients who are interested in
offloading their work. Our rate is only 5 US$ for an hour of
There is an XSD task. I've found however that it always executes even if
the file has not changed. At least it looks like it. I haven't had a
chance to test that, or notify the author (or try to implement a fix
myself).
xsd schema=whatever.xsd language=CS outputdir=wherever
target=dataset /
I have tested it, and yes, the XSD task always runs even if the file has
not changed.
Patrick
-Original Message-
From: Colin Young [mailto:colin_young;yahoo.com]
Sent: Friday, October 18, 2002 10:27 AM
To: 'Tim Edalatpour'; [EMAIL PROTECTED]
Subject: RE: [nant-dev] User Task to generate
Hi Kevin,
I traced it to PropertyDictionary.cs not checking to see if a property was
already present before adding it.
Here is my fix sorry about the lack of diff. Basically added a check to
not
allow duplicates to the PropertyDictionary.
The fix seems to already have been commited by
IF YOU ARE UNABLE TO VIEW THE GRAPHICS IN THIS EMAIL, PLEASE VISIT HTTP://WWW.BEYONDIGITAL.COM TO ENJOY THE FULL EXPERIENCE.BEYONDIGITAL RESPECTS YOUR PRIVACY. TO UNSUBSCRIBE FROM FUTURE PROMOTIONAL EMAILS BY BEYONDIGITAL, PLEASE VISIT HTTP://WWW.BEYONDIGITAL.COM/OPTOUT.YOUR ADDRESS WILL BE
+1
My proposal for a fix would actually be to leave PropertyDictionary
alone,
and instead modify SysInfo so that it uses indexer access to add it's
properties. That simple change would satisfy both elements I outline
above.
What does anybody else think?
--
Tomas Restrepo
Tomas Restrepo wrote:
The fix seems to already have been commited by someone else.
that was me :)
However, may I argue _against_ this fix?
There are two reasons I don't like it:
a- It changes semantics. PropertyDictionary inherits from DictionatyBase.
Common semantics in all of .NET
It might be uesful to be able to poke values into the
environment from the
build file for various tasks that use them.
When I get around to syncing my version and the public version of nant
I've made a change to the exec task that does something like this:
The task looks for properties
