subject:"\[nant\-dev\] \?"

Hi,

Thanks for your comments, see below.

On Wed, Oct 26, 2011 at 10:57 AM, Leszek Ciesielski skol...@gmail.com wrote:
 On Wed, Oct 26, 2011 at 6:33 PM, Ryan Boggs rmbo...@gmail.com wrote:
 Hi,

 On Wed, Oct 26, 2011 at 8:53 AM, Stefan Bodewig
 stefan.bode...@freenet.de wrote:
 On 2011-10-26, Ryan Boggs wrote:

 Now that 0.91 final is out the door, I would like to start discussing
 what items to work on in both NAnt/NAntContrib.  Attached is an html
 file of an outline I put together with thoughts about next steps I
 have had for months (I put it in an attachment just in case your email
 viewers don't handle html emails).

 Jumping in at some random point and as somebody who has a strong Ant
 background but doesn't really know NAnt as good as I should.

 I can't say much about your choice of SCM.  Why do you feel
 Sourceforge's git offering was insufficient - this is an honest question
 as I may be thinking about moving XMLUnit to a different SCM myself
 (currently using svn at Sourceforge).
 It just doesn't feel like there is alot of effort on the repo side in
 terms of code reviews and other tools that sites like github have.
 That being said, I've been toying with the idea about using of setting
 up a git repo on SF to use as a mirror of source.  I am also thinking
 about keeping the CVS repo at SF live but readonly for historic
 reasons.

 One thing I noticed from experience I have with github.com is that it
 is much easier to share/review code from others than it currently is
 on SF.

 I'm giving a +1 to choosing git and github, in a large part because
 those two are popular and well known. And github's pull management is
 an awesome feature.
:) yup, I concur.


 We'll be polling log4net's users about platform support soon.  I also
 feel you are safe to require 2.0 at runtime as long as you keep 1.x as
 targets.
 I hope so.

 Agree here as well. Although this might (in future) mean quite a large
 rewrite of the NAnt API to make use of the generics.
Eh, it would but I am thinking that the first step of this part is
removing all of the preprocessing statements that separate between
.net 1.0 and .net 2.0. Converting the existing code to use features
from .net/mono 2.0 = would probably only be worked on if the gains
were significant enough.


 When I worked on the log4net release I cursed NAnt's lack of a mapper
 so a big +1 for this.  I also miss macrodef.  Badly.
 I should add macrodef too, eh?

 Have you seen the 1.2.11 release of log4net of about two weeks ago? ;-)
 I have not.  I'll have to check that out.

 If activity has restarted for log4net like you say, I should take that
 item off my list I just sent out.  It was something I have had in mind
 for months prior when log4net activity seemed non-existent.

 It took me awhile to get NAnt to use log4net 1.2.10 because of
 sharpcvslib's dependency on log4net 1.2.9.  Since I was recently
 granted commit access to that project, I could see if I could upgrade
 the dependency in both projects.

 Updating nunit2 task will be tricky, especially if you want to keep
 it working on Mono as well. Any NAnt deployment that I'm aware of has
 resorted to using exec instead, because of compatibility problems
 between nunit dlls NAnt bundled and those that the project itself
 used.
Yeah, I am aware of this as I looked into this during 0.91
development.  The NUnit API changed drastically between the current
version NAnt is using today (2.2 I believe) and the latest release
(2.10). Thus, this task was pushed out to avoid further delays of 0.91
final.  From what I gathered from NUnit's docs, 2.5.10 should work on
both mono and .net now so it shouldn't be a problem from that end
(hopefully).

 From the low priority list:
 I'm quite fond of the NAnt website layout :-) And migrating to another
 license requires written permission from every past contributor - this
 would be a hard task to perform. Also, it might not provide any gain
 to end users - development tools don't usually need a permissive
 license, as they are not linked into the end product.
The reasons you just specified are the reasons why they are considered
low priority.  Yeah, the site's current layout still works but it
could use a face lift to bring it to this decade.  Again, low
priority.

As for the license change, it would be a considerable undertaking and
the end payout may not be worth it, on top of the fact that there are
higher priorities I would like to address first before sizing up this
task.  I am in no rush to pursue this at this time but I wanted to
keep it up there for future review.

Thanks,
Ryan

 Regards,

 Leszek 'skolima' Ciesielski

 --
 The demand for IT networking professionals continues to grow, and the
 demand for specialized networking skills is growing even more rapidly.
 Take a complimentary Learning@Cisco Self-Assessment and learn
 about Cisco certifications, training, and career opportunities.

Re: [nant-dev] Next NAnt/NAntContrib TODO Tasks

2011-10-26 Thread Rob Richardson

I'll avoid the athon and just reply at the top.
 
+1 on git and github.  That's more-or-less the lingua franca of 
open-source now-a-days.  Being able to accept pull
requests would be awesome!  Once it's
there, I've got a heap ton of pull requests I'd love to hand off.  To that end, 
we should consider a git
task in NAnt, and consider moving cvs to NAntContrib.
 
I'd like to see nunit2
either get to 2.5.10 or spun off as a separate project.  I had to resort to 
exec to get 2.5.10
working as well.  Many SF patches / posts
have upgraded the task throughout the years, but it's never gotten pulled into 
the trunk.  If NAnt's cadence is going to be anywhere
near previous precedent, nunit2 has to move separately to remain relevant.
 
I'd like to also throw in my
vote to get msbuild moved from NAntContrib to NAnt.  The solution task 
hasn't worked for
me in 5 years, and thus msbuild has really become an essential part of
NAnt.  (Towards the goals of NAnt 2.5, we could shim solution to use 
msbuild for VS 2005+ projects/solutions.)  Tangentially related, if we used 
the
msbuild task to build NAnt, we could easily get Any CPU
mode -- a result not currently available in the NAnt release package.
 
+1 on moving to .net 2 and
generics, and a standard #define net_4 release would also be awesome.

How can I help?
 
Rob

--
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Next NAnt/NAntContrib TODO Tasks

2011-10-26 Thread Rob Richardson

Ryan,

Towards #net_4, I'd like to see an official download package for each runtime 
we target.  E.g. one download for .net 1 (the one we have now ... until we kill 
it off), .net 2, .net 4, mono vX, mono vY, etc -- e.g. a download per #define 
tag.  Right now the only way to get a #net_4 runtime version is to download 
source and compile.  That isn't too bad except I have to dig up a VM that still 
has / I don't mind installing CVS onto.  (Referencing the previous git / github 
+1.  :D)

With git / github, check 
out http://sourceforge.net/mailarchive/message.php?msg_id=27967861 and https://github.com/skolima/NAnt.
  It'd be very, very nice if it was official. rather than cron-cloned.

What is still needed with the msbuild task?  I'd like to see more built-in 
parameters instead of resulting to arg / but at the end of the day, it gets 
it done.

I'd love to help in any way I can.  I've got a nice library I'd love to share 
that implements Ant's parallel and restrict tasks.  I've also got tasks 
that list projects given a solution, list project content given a project (to 
facilitate deploying a website), runs a sql command given a connection string 
or an app/web.config and (optionally) connection name using SqlClient instead 
of ODBC, and a few other goodies and tricks.  +1 for xmllist as well, though 
I didn't write it.  If any of these can get into the official trunk for NAnt or 
Contrib, all the better.

I grant in the near-term you probably need more help in existing tasks than in 
new ones, and I'm ok with that too.  What're the open issues / tasks?  Which 
would you like me to take on first?

Rob



- Original Message -
From: Ryan Boggs rmbo...@gmail.com
To: Rob Richardson erobr...@yahoo.com
Cc: nant-developers@lists.sourceforge.net 
nant-developers@lists.sourceforge.net
Sent: Wednesday, October 26, 2011 12:35 PM
Subject: Re: [nant-dev] Next NAnt/NAntContrib TODO Tasks

Hi,

On Wed, Oct 26, 2011 at 12:21 PM, Rob Richardson erobr...@yahoo.com wrote:
 I'll avoid the athon and just reply at the top.

 +1 on git and github.  That's more-or-less the lingua franca of 
 open-source now-a-days.  Being able to accept pull
 requests would be awesome!  Once it's
 there, I've got a heap ton of pull requests I'd love to hand off.  To that 
 end, we should consider a git
 task in NAnt, and consider moving cvs to NAntContrib.
Nice, another plus 1.
My thinking was to move both NAnt/NAntContrib to a non-CVS repo at the
same time.  Hopefully, this process will bring the projects closer
together in scope so we don't have a lag on one side or another.

 I'd like to see nunit2
 either get to 2.5.10 or spun off as a separate project.  I had to resort to 
 exec to get 2.5.10
 working as well.  Many SF patches / posts
 have upgraded the task throughout the years, but it's never gotten pulled 
 into the trunk.  If NAnt's cadence is going to be anywhere
 near previous precedent, nunit2 has to move separately to remain relevant.
My goal is to get it to the latest version, which is 2.5.10 I believe.
Like I stated in a previous email today, I couldn't get to it during
0.91 development because of the amount of effort needed to update NAnt
to use the new NUnit API.

 I'd like to also throw in my
 vote to get msbuild moved from NAntContrib to NAnt.  The solution task 
 hasn't worked for
 me in 5 years, and thus msbuild has really become an essential part of
 NAnt.  (Towards the goals of NAnt 2.5, we could shim solution to use 
 msbuild for VS 2005+ projects/solutions.)  Tangentially related, if we used 
 the
 msbuild task to build NAnt, we could easily get Any CPU
 mode -- a result not currently available in the NAnt release package.
IIRC, the msbuild task needs some more effort before being ported
over.  I know there was work done around VS.NET/msbuild during the
0.91 release cycle but I am not sure how much of that effort related
to the NAntContrib msbuild task.

I was planning on approaching this now anyway.  One of the things I
would like to work on is some kind of sandcastle task for doc building
but it would probably have to rely on that msbuild task.

 +1 on moving to .net 2 and
 generics, and a standard #define net_4 release would also be awesome.
I thought we had the net_4.0 preprocessing tag in NAnt already, unless
I am misunderstanding you here.

 How can I help?
Love the enthusiasm! :) Speak up and be heard.  I try to read these
messages as much as I can so any input/advice/suggestions you or
anyone else may have, please chime in.  We welcome it. :)

I'm hoping to get a more up-to-date contribution guide going once we
make a decision on the cvs repo situation.  I'll post it once we get
there. :)

Thanks,
Ryan

 Rob

 --
 The demand for IT networking professionals continues to grow, and the
 demand for specialized networking skills is growing even more rapidly.
 Take a complimentary Learning@Cisco Self-Assessment and learn
 about

Re: [nant-dev] Next NAnt/NAntContrib TODO Tasks

Hi,

On Wed, Oct 26, 2011 at 1:05 PM, Rob Richardson erobr...@yahoo.com wrote:
Ryan,

Towards #net_4, I'd like to see an official download package for each runtime
we target. E.g. one download for .net 1 (the one we have now ... until we
kill it off), .net 2, .net 4, mono vX, mono vY, etc -- e.g. a download per
#define tag. Right now the only way to get a #net_4 runtime version is to
download source and compile. That isn't too bad except I have to dig up a VM
that still has / I don't mind installing CVS onto. (Referencing the previous
git / github +1. :D)

Ahhh, I see. That has been discussed in the past. I personally do
not have a problem with this setup (others might, IIRC) but we would
probably have to figure out a smart approach to this. On top of
figuring out whether or not official installers should be built (using
something like msi or NSIS).

With git / github, check
out http://sourceforge.net/mailarchive/message.php?msg_id=27967861 and https://github.com/skolima/NAnt.
It'd be very, very nice if it was official. rather than cron-cloned.

That would be the plan. I would like to keep the current cvs around
as a readonly history repo while all of the upcoming changes go into
whatever system is decided upon. So no cron-cloned, just straight in.

What is still needed with the msbuild task? I'd like to see more built-in
parameters instead of resulting to arg / but at the end of the day, it gets
it done.

Unfortunately, I need to dive in and see. I am basing my response on
past conversations I have had with other team members.

I'd love to help in any way I can. I've got a nice library I'd love to share
that implements Ant's parallel and restrict tasks. I've also got tasks
that list projects given a solution, list project content given a project (to
facilitate deploying a website), runs a sql command given a connection string
or an app/web.config and (optionally) connection name using SqlClient instead
of ODBC, and a few other goodies and tricks. +1 for xmllist as well,
though I didn't write it. If any of these can get into the official trunk
for NAnt or Contrib, all the better.

Those sound like goodies that would be cool to have.

I grant in the near-term you probably need more help in existing tasks than
in new ones, and I'm ok with that too. What're the open issues / tasks?
Which would you like me to take on first?

Well, that's the beauty of working on an open source project. Work on
what you want to work on. We have items that we wish to work on that
may not reflect what you consider high priorities. Send in what you
have and we can see where they would fit in.

Like I have said before, we probably need to update our contribution
instructions pretty soon after the repo decision is made.

Thanks,
Ryan

Rob

- Original Message -
From: Ryan Boggs rmbo...@gmail.com
To: Rob Richardson erobr...@yahoo.com
Cc: nant-developers@lists.sourceforge.net
nant-developers@lists.sourceforge.net
Sent: Wednesday, October 26, 2011 12:35 PM
Subject: Re: [nant-dev] Next NAnt/NAntContrib TODO Tasks

Hi,

On Wed, Oct 26, 2011 at 12:21 PM, Rob Richardson erobr...@yahoo.com wrote:
I'll avoid the athon and just reply at the top.

+1 on git and github. That's more-or-less the lingua franca of
open-source now-a-days. Being able to accept pull
requests would be awesome! Once it's
there, I've got a heap ton of pull requests I'd love to hand off. To that
end, we should consider a git
task in NAnt, and consider moving cvs to NAntContrib.
Nice, another plus 1.
My thinking was to move both NAnt/NAntContrib to a non-CVS repo at the
same time. Hopefully, this process will bring the projects closer
together in scope so we don't have a lag on one side or another.

I'd like to see nunit2
either get to 2.5.10 or spun off as a separate project. I had to resort to
exec to get 2.5.10
working as well. Many SF patches / posts
have upgraded the task throughout the years, but it's never gotten pulled
into the trunk. If NAnt's cadence is going to be anywhere
near previous precedent, nunit2 has to move separately to remain relevant.
My goal is to get it to the latest version, which is 2.5.10 I believe.
Like I stated in a previous email today, I couldn't get to it during
0.91 development because of the amount of effort needed to update NAnt
to use the new NUnit API.

I'd like to also throw in my
vote to get msbuild moved from NAntContrib to NAnt. The solution task
hasn't worked for
me in 5 years, and thus msbuild has really become an essential part of
NAnt. (Towards the goals of NAnt 2.5, we could shim solution to use
msbuild for VS 2005+ projects/solutions.) Tangentially related, if we
used the
msbuild task to build NAnt, we could easily get Any CPU
mode -- a result not currently available in the NAnt release package.
IIRC, the msbuild task needs some more effort before being ported
over. I know there was work

Re: [nant-dev] Next NAnt/NAntContrib TODO Tasks

Hi all,

Thanks for the feedback so far.  It's really great to hear all your
thoughts on these matters.  Please feel free to tell us your thoughts,
if you haven't already.

I went ahead and converted this list to a page on NAnt's wiki for
easier review and maintenance.  I have also made some updates based on
some of the feedback so far.  Please take a look...

https://sourceforge.net/apps/mediawiki/nant/index.php?title=TODO

Thanks,
Ryan

On Wed, Oct 26, 2011 at 8:28 AM, Ryan Boggs rmbo...@gmail.com wrote:
 Hi guys,

 Now that 0.91 final is out the door, I would like to start discussing
 what items to work on in both NAnt/NAntContrib.  Attached is an html
 file of an outline I put together with thoughts about next steps I
 have had for months (I put it in an attachment just in case your email
 viewers don't handle html emails).  I tried to include items that have
 been discussed in past emails.  All of these items affect both
 NAnt/NAntContrib unless specified otherwise.

 One of the things that has been on my mind for months is moving NAnt
 off of cvs.  When I polled that decision some time ago, the general
 consensus was that any move away from cvs would be a step up.  My
 personal feeling is to move from cvs to git or hg to because it is
 more easy for me to work with than cvs.  The first item in my list
 compares the two more popular repo sites out there.  I am partial to
 github.com because I have been using it alot lately for other things
 (working on the Boo language project for example) but I would like to
 hear other thoughts.  I have been experimenting with converting cvs to
 git with a good degree of success (all history, tags, and branches
 come through) but I am sure further tweeking will be necessary.

 A side note, when 0.91 final was released, I wasn't sure what the next
 version of NAnt we would be targeting so I just set it to 0.92.  This
 can be discussed further if need be.

 Looking forward to hearing your feedback.

 Thanks,
 Ryan


--
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Next NAnt/NAntContrib TODO Tasks

2011-10-26 Thread Dominik Guder

Hi Ryan,

+1 for github.

And we should define/discus a contribution process to ensure that nant
core will stay as stable as it is currently.

Other proposals:
- Color output. Red for errors, yellow for warning and green for
sucessfull build. I added this to my own net_2.0 build and I'm addicted
to this easily identifying Green successfull build message.

- solution task/msbuild polishing since there still issues with our
projects.

SourceControl:
- move CVS to nantcontrib
- integrate git
- polish svn
- add tfs (see ci-factory)

http://ci-factory.googlecode.com/svn/Current/Product/Production/Nant/TF.Tasks/

lower priority:
- review nant.exe.config: maybe separate net-x and mono-x definitions
or one for each target. It is very large and hardly to maintain.

Check other ci-factory tasks to add them to nantcontrib.

Hint: I found macrodef at ci-factory:
http://ci-factory.googlecode.com/svn/Current/Product/Production/Nant/CIFactory.NAnt.Tasks/Tasks/

It was getting longer and longer.
So far Dominik

--
The answer to the great question of life,
the universe and everything is 42 (Douglas Adams)

--
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn
about Cisco certifications, training, and career opportunities.
http://p.sf.net/sfu/cisco-dev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Next NAnt/NAntContrib TODO Tasks

Hey Dominik,

On Wed, Oct 26, 2011 at 2:35 PM, Dominik Guder o...@guder.org wrote:
Hi Ryan,

+1 for github.
How many responses should we collect before we make an official
decision on this? :)

And we should define/discus a contribution process to ensure that nant
core will stay as stable as it is currently.
110% agree. I would like to do this once the repo decision is made.

This would be good for Windows but we should take care in *nix systems
as some terminal emulators do not support color.

- solution task/msbuild polishing since there still issues with our
projects.
Yeah, this is a popular option. We should probably loop back this
task with the one in NAntContrib to see if we can get this stuff
straightened out. I'm for this.

SourceControl:
- move CVS to nantcontrib
- integrate git
- polish svn
- add tfs (see ci-factory)
Yes, yes, yes, and yes. I also threw Mercurial in that list for good measure.

http://ci-factory.googlecode.com/svn/Current/Product/Production/Nant/TF.Tasks/

lower priority:
- review nant.exe.config: maybe separate net-x and mono-x definitions
or one for each target. It is very large and hardly to maintain.
Good one, I agree. Just not sure of the best approach. We can
discuss this further.

- fix/polish commandline handling:
- remove anoying : as separator, this prevents you from using tab
completion in cmd window (even WiX did this with 3.5 release)
- add double dash as parameter prefix (as used at gnu tools) at least
for --help and --version
One thing I would like to investigate is implementing something like
Mono.Options instead of the home grown command args parser. I've used
it in personal projects and it was pretty cool. That may address your
concern here.

Check other ci-factory tasks to add them to nantcontrib.

Hint: I found macrodef at ci-factory:
http://ci-factory.googlecode.com/svn/Current/Product/Production/Nant/CIFactory.NAnt.Tasks/Tasks/
Oh wow, pretty cool.

Thanks,
Ryan

It was getting longer and longer.
So far Dominik

--
The answer to the great question of life,
the universe and everything is 42 (Douglas Adams)

[nant-dev] [ nant-Bugs-3366107 ] xmlpeek behavior broken in 0.91 alpha 1

2011-10-17 Thread SourceForge . net

Bugs item #3366107, was opened at 2011-07-13 07:19
Message generated for change (Comment added) made by rmboggs
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3366107group_id=31650

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: Tasks
Group: 0.91-rc1
Status: Closed
Resolution: Fixed
Priority: 5
Private: No
Submitted By: Dmitry Kostenko (bis0n)
Assigned to: Ryan Boggs (rmboggs)
Summary: xmlpeek behavior broken in 0.91 alpha 1

Initial Comment:
The fix for feature request 1560566 [1] has changed the way xmlpeek returns 
value when XPath refers to an XML node, not text() or attribute.

0.90 and before - XML of the node was returned
0.91 alpha 1 and after - Value of the node is returned, making it impossible 
to use XmlPeek + XmlPoke to copy-paste XML between documents.

[1] 
https://sourceforge.net/tracker/index.php?func=detailaid=1560566group_id=31650atid=402871


--

Comment By: Ryan Boggs (rmboggs)
Date: 2011-10-17 18:48

Message:
10-17-2011 Nightly snapshot contains the fix.

--

Comment By: Ryan Boggs (rmboggs)
Date: 2011-10-16 20:52

Message:
Fix was just committed to cvs and should be in the next nightly/release.

--

Comment By: Dmitry Kostenko (bis0n)
Date: 2011-07-14 00:26

Message:
Please move this into Bugs - it's not a feature request, I took the wrong
tracker.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3366107group_id=31650

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] [ nant-Bugs-3366107 ] xmlpeek behavior broken in 0.91 alpha 1

2011-10-16 Thread SourceForge . net

Bugs item #3366107, was opened at 2011-07-13 07:19
Message generated for change (Comment added) made by rmboggs
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3366107group_id=31650

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: Tasks
Group: 0.91-rc1
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Dmitry Kostenko (bis0n)
Assigned to: Ryan Boggs (rmboggs)
Summary: xmlpeek behavior broken in 0.91 alpha 1

Initial Comment:
The fix for feature request 1560566 [1] has changed the way xmlpeek returns 
value when XPath refers to an XML node, not text() or attribute.

0.90 and before - XML of the node was returned
0.91 alpha 1 and after - Value of the node is returned, making it impossible 
to use XmlPeek + XmlPoke to copy-paste XML between documents.

[1] 
https://sourceforge.net/tracker/index.php?func=detailaid=1560566group_id=31650atid=402871


--

Comment By: Ryan Boggs (rmboggs)
Date: 2011-10-16 20:52

Message:
Fix was just committed to cvs and should be in the next nightly/release.

--

Comment By: Dmitry Kostenko (bis0n)
Date: 2011-07-14 00:26

Message:
Please move this into Bugs - it's not a feature request, I took the wrong
tracker.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3366107group_id=31650

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] [ nant-Bugs-3390653 ] xmlpeek broken in 0.91alpha2

2011-10-16 Thread SourceForge . net

Bugs item #3390653, was opened at 2011-08-12 10:11
Message generated for change (Comment added) made by rmboggs
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3390653group_id=31650

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: Tasks
Group: 0.91-alpha2
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Jiho Han ()
Assigned to: Ryan Boggs (rmboggs)
Summary: xmlpeek broken in 0.91alpha2

Initial Comment:
xmlpeek would return the inner xml of the node found in the property specified. 
 This worked in 0.85 but returns an empty string in 0.91alpha2.
I'm not certain whether this has existed in previous versions or not.

--

Comment By: Ryan Boggs (rmboggs)
Date: 2011-10-16 21:01

Message:
This report is actually a duplicate of 3366107.  I just realized this.

However, I just committed an update to XmlPeek to cvs that should address
this issue.  I was able to successfully test the sample provided by
gntleone.  The expected output is now the actual output when nant is built
from cvs.  If possible, please test by building from cvs.

--

Comment By: Ryan Boggs (rmboggs)
Date: 2011-10-13 18:23

Message:
Hmm, I'll take a look.

--

Comment By: Lee (gntleone)
Date: 2011-10-13 08:51

Message:
The old behavior of retrieving the full collection of nodes has been
broken.  The only thing returned now is the text contents of child nodes,
not the full node.  This has been broken since nant-0.91-alpha1. Example
follows.

test.xml
?xml version=1.0 encoding=utf-8 standalone=yes?
builds
build name=TEST
date10/13/2011 10:13:07/date
buildNum126/buildNum
modules
module name=TESTModule
FileVersion11.0.2002.101/FileVersion
ProductVersion11.0.2002.101/ProductVersion
/module
/modules
/build
/builds

QUERY:
xmlpeek xpath=//builds file=${project.versions} property=xmlnodes/

Expected output:
build name=TEST
date10/13/2011 10:13:07/date
buildNum126/buildNum
modules
module name=TESTModule
FileVersion11.0.2002.101/FileVersion
ProductVersion11.0.2002.101/ProductVersion
/module
/modules
/build

ACTUAL output:
  [xmlpeek] Found '1' nodes with the XPath expression '//builds'.
 [echo] xmlnodes: 10/13/2011 10:13:0712611.0.2002.10111.0.2002.101


--

Comment By: Dominik Guder (dogu)
Date: 2011-09-25 13:22

Message:
Until you provide a sample for this issue, I would suggest that you try to
append /text() to your XPath so you should get the inner xml or value.
Please drop me a note if I'm completely wrong.

--

Comment By: Ryan Boggs (rmboggs)
Date: 2011-08-14 13:06

Message:
Hi, can you please provide a sample that can better illustrate this issue? 
I believe that this task is working fine for me, as far as I can tell.

Thanks,
Ryan

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3390653group_id=31650

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] [ nant-Bugs-3390653 ] xmlpeek broken in 0.91alpha2

2011-10-13 Thread SourceForge . net

Bugs item #3390653, was opened at 2011-08-12 10:11
Message generated for change (Comment added) made by rmboggs
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3390653group_id=31650

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: Tasks
Group: 0.91-alpha2
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Jiho Han ()
Assigned to: Nobody/Anonymous (nobody)
Summary: xmlpeek broken in 0.91alpha2

Initial Comment:
xmlpeek would return the inner xml of the node found in the property specified. 
 This worked in 0.85 but returns an empty string in 0.91alpha2.
I'm not certain whether this has existed in previous versions or not.

--

Comment By: Ryan Boggs (rmboggs)
Date: 2011-10-13 18:23

Message:
Hmm, I'll take a look.

--

Comment By: Lee (gntleone)
Date: 2011-10-13 08:51

Message:
The old behavior of retrieving the full collection of nodes has been
broken.  The only thing returned now is the text contents of child nodes,
not the full node.  This has been broken since nant-0.91-alpha1. Example
follows.

test.xml
?xml version=1.0 encoding=utf-8 standalone=yes?
builds
build name=TEST
date10/13/2011 10:13:07/date
buildNum126/buildNum
modules
module name=TESTModule
FileVersion11.0.2002.101/FileVersion
ProductVersion11.0.2002.101/ProductVersion
/module
/modules
/build
/builds

QUERY:
xmlpeek xpath=//builds file=${project.versions} property=xmlnodes/

Expected output:
build name=TEST
date10/13/2011 10:13:07/date
buildNum126/buildNum
modules
module name=TESTModule
FileVersion11.0.2002.101/FileVersion
ProductVersion11.0.2002.101/ProductVersion
/module
/modules
/build

ACTUAL output:
  [xmlpeek] Found '1' nodes with the XPath expression '//builds'.
 [echo] xmlnodes: 10/13/2011 10:13:0712611.0.2002.10111.0.2002.101


--

Comment By: Dominik Guder (dogu)
Date: 2011-09-25 13:22

Message:
Until you provide a sample for this issue, I would suggest that you try to
append /text() to your XPath so you should get the inner xml or value.
Please drop me a note if I'm completely wrong.

--

Comment By: Ryan Boggs (rmboggs)
Date: 2011-08-14 13:06

Message:
Hi, can you please provide a sample that can better illustrate this issue? 
I believe that this task is working fine for me, as far as I can tell.

Thanks,
Ryan

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3390653group_id=31650

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] [ nant-Bugs-3416986 ] Cannot Compile NAnt CVS Head on Win XP

2011-10-01 Thread SourceForge . net

Bugs item #3416986, was opened at 2011-10-01 15:58
Message generated for change (Comment added) made by tylerk1993
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3416986group_id=31650

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: Core
Group: cvs
Status: Open
Resolution: None
Priority: 8
Private: No
Submitted By: Tyler (tylerk1993)
Assigned to: Nobody/Anonymous (nobody)
Summary: Cannot Compile NAnt CVS Head on Win XP

Initial Comment:
Whenever I try to build NAnt (the CVS head revision) on Windows XP, VS 2010 
Ultimate, .NET Framework 4.0, I get an error when the bootstrapped NAnt is 
trying to build the documentation:

[exec] BUILD FAILED
[exec]
[exec] C:\NAnt\NAnt.build(361,14):
[exec] Error building documentation.
[exec] This method implicitly uses CAS policy, which has been 
obsoleted by the .NET Framework. In order to enable CAS policy for 
compatibility reasons, please use the NetFx40_LegacySecurityPolicy 
configuration switch. Please see http://go.microsoft.com/fwlink/?LinkID=155570 
for more information.
[exec]
[exec] Total time: 1.2 seconds.
[exec]
BUILD FAILED
C:\NAnt\NAnt.build(335,10):
External Program Failed: C:\NAnt/build/nant-0.91-dev/bin/NAnt.exe (return code 
was 1)
Total time: 10.9 seconds.
NMAKE : fatal error U1077: 'bootstrap\NAnt.exe' : return code '0x1'
Stop.
C:\NAnt 

--

Comment By: Tyler (tylerk1993)
Date: 2011-10-01 16:57

Message:
The file I just posted is a log file I generated with the output from the
nmake command.

--

Comment By: Ryan Boggs (rmboggs)
Date: 2011-10-01 16:25

Message:
Ok try this then,
nmake -f Makefile.nmake TARGET=net-4.0 prefix=c:\program files

--

Comment By: Tyler (tylerk1993)
Date: 2011-10-01 16:19

Message:
I am using Microsoft NMake. I first ran vsvars32.bat (from
%VS100COMNTOOLS%).

--

Comment By: Ryan Boggs (rmboggs)
Date: 2011-10-01 16:13

Message:
If you are using make to build, try using the TARGET=net-4.0 argument.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3416986group_id=31650

--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] [ nant-Bugs-3416986 ] Cannot Compile NAnt CVS Head on Win XP

2011-10-01 Thread SourceForge . net

Bugs item #3416986, was opened at 2011-10-01 15:58
Message generated for change (Comment added) made by tylerk1993
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3416986group_id=31650

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: Core
Group: cvs
Status: Open
Resolution: None
Priority: 8
Private: No
Submitted By: Tyler (tylerk1993)
Assigned to: Nobody/Anonymous (nobody)
Summary: Cannot Compile NAnt CVS Head on Win XP

Initial Comment:
Whenever I try to build NAnt (the CVS head revision) on Windows XP, VS 2010 
Ultimate, .NET Framework 4.0, I get an error when the bootstrapped NAnt is 
trying to build the documentation:

[exec] BUILD FAILED
[exec]
[exec] C:\NAnt\NAnt.build(361,14):
[exec] Error building documentation.
[exec] This method implicitly uses CAS policy, which has been 
obsoleted by the .NET Framework. In order to enable CAS policy for 
compatibility reasons, please use the NetFx40_LegacySecurityPolicy 
configuration switch. Please see http://go.microsoft.com/fwlink/?LinkID=155570 
for more information.
[exec]
[exec] Total time: 1.2 seconds.
[exec]
BUILD FAILED
C:\NAnt\NAnt.build(335,10):
External Program Failed: C:\NAnt/build/nant-0.91-dev/bin/NAnt.exe (return code 
was 1)
Total time: 10.9 seconds.
NMAKE : fatal error U1077: 'bootstrap\NAnt.exe' : return code '0x1'
Stop.
C:\NAnt 

--

Comment By: Tyler (tylerk1993)
Date: 2011-10-01 17:40

Message:
And the strange thing is that one can build *without* the install target
and it builds successfully (but might not be the complete NAnt distro
needed to build other apps).

--

Comment By: Ryan Boggs (rmboggs)
Date: 2011-10-01 17:27

Message:
Ah, I was able to replicate.  I believe that the issue may be with the NDoc
libs that are used to generate NAnt's docs.  I am working on this now.

--

Comment By: Tyler (tylerk1993)
Date: 2011-10-01 16:57

Message:
The file I just posted is a log file I generated with the output from the
nmake command.

--

Comment By: Ryan Boggs (rmboggs)
Date: 2011-10-01 16:25

Message:
Ok try this then,
nmake -f Makefile.nmake TARGET=net-4.0 prefix=c:\program files

--

Comment By: Tyler (tylerk1993)
Date: 2011-10-01 16:19

Message:
I am using Microsoft NMake. I first ran vsvars32.bat (from
%VS100COMNTOOLS%).

--

Comment By: Ryan Boggs (rmboggs)
Date: 2011-10-01 16:13

Message:
If you are using make to build, try using the TARGET=net-4.0 argument.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3416986group_id=31650

--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Announcing NAnt 0.91 Beta1

2011-09-25 Thread Ryan Boggs

We are proud to announce the first beta release of NAnt 0.91.

Many thanks to those who were involved with the development of NAnt
this past year.  Especially to Martin Aliger and Dominik Guder without
whom this release would not have been possible without.

The primary goal for this release is to continue to improve support
for .NET 4.0.  Please give this release a test and report any NAnt
core specific bugs back along with examples as soon as you can.

This release focuses on extending our already strong support for
multiple target frameworks, bringing improved flexibility and
performance.  Some show stopping issues have been resolved as well.

A roadmap has been created to help illustrate the current release
plan.  Please note that this roadmap is a work in progress and is
subject to change depending on feature priorities, issues, and
developer's comfort level with the release:
https://sourceforge.net/apps/mediawiki/nant/index.php?title=Roadmap

Binary and source distributions are available for immediate download from:
https://sourceforge.net/projects/nant/files/nant/0.91-beta1/

The CVS tag for NAnt 0.91Beta1 is:
rel-0-91-beta1

Instruction for checking out sources from CVS are available here:
https://sourceforge.net/scm/?type=cvsgroup_id=31650

Discussion of NAnt occurs on the mailing list at
nant-us...@lists.sourceforge.net.

Bugs can be reported using the Bug Tracker at
http://sourceforge.net/projects/nant.

For more detailed progress on the inner workings of NAnt, check out
the NAnt Blog at https://sourceforge.net/apps/wordpress/nant/

About NAnt:
NAnt is a free .NET build tool, allowing applications to be built
targeting both Microsoft .NET and Mono while supporting both Windows
and Linux platforms.

Check the NAnt homepage for additional info at http://nant.sourceforge.net.

Thanks,
Ryan

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Default excludes for hg and git

2011-09-20 Thread Dominik Guder

Hi foks,

I need your input:

As you might know nant fileset has a bunch of default excludes.
I want to name mainly cvs and svn administrative folders **/CVS/** and 
**/.svn/** as well as cvs ignore file **/.cvsignore.

I want to add some more to this list. Especially for Git and Mercurial.
These are:
**/.git and **/.git/** for git admin folder
**/.hg and **/.hg/** for hg admin folder

So what to do with git and hg ignore/config files
There the two ignore files .gitignore and .hgignore should they are 
excluded by default too?

Or the other ones which are starting with .hg* or .git* like 
.hgsvnexternals or .hgeol should they be excluded by default too?

If there are some other files/folders which should be excluded by default?

So far and many thanks in advance.

Dominik

-- 
The answer to the great question of life,
the universe and everything is 42 (Douglas Adams)

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] [NAnt-users] Default excludes for hg and git

2011-09-20 Thread Ryan Boggs

Hi,

On Tue, Sep 20, 2011 at 5:21 PM, Thierry Lach thierry.l...@gmail.com wrote:
 The  .*ignore files only have meaning with source control in effect. Since
 the /cvs/, /.svn/, etc dirs are not included, I'd say exclude the  .*ignore
 files and any others related to source control.
Your right, ignore 'em all...

Thanks,
Ryan

 On Sep 20, 2011 8:03 PM, Ryan Boggs rmbo...@gmail.com wrote:
 Hi,

 On Tue, Sep 20, 2011 at 2:18 PM, Dominik Guder o...@guder.org wrote:
 Hi foks,

 I need your input:

 As you might know nant fileset has a bunch of default excludes.
 I want to name mainly cvs and svn administrative folders **/CVS/** and
 **/.svn/** as well as cvs ignore file **/.cvsignore.

 I want to add some more to this list. Especially for Git and Mercurial.
 These are:
 **/.git and **/.git/** for git admin folder
 **/.hg and **/.hg/** for hg admin folder
 I saw go for it. These should be ignored anyway.

 So what to do with git and hg ignore/config files
 There the two ignore files .gitignore and .hgignore should they are
 excluded by default too?
 I would think that these shouldn't be ignored. But it sounds like it
 is the norm?

 Or the other ones which are starting with .hg* or .git* like
 .hgsvnexternals or .hgeol should they be excluded by default too?
 I am not familiar with these files. I haven't seen them before.

 If there are some other files/folders which should be excluded by
 default?

 So far and many thanks in advance.

 Dominik

 --
 The answer to the great question of life,
 the universe and everything is 42 (Douglas Adams)


 --
 All the data continuously generated in your IT infrastructure contains a
 definitive record of customers, application performance, security
 threats, fraudulent activity and more. Splunk takes this data and makes
 sense of it. Business sense. IT sense. Common sense.
 http://p.sf.net/sfu/splunk-d2dcopy1
 ___
 nant-developers mailing list
 nant-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/nant-developers

 Thanks,
 Ryan


 --
 All the data continuously generated in your IT infrastructure contains a
 definitive record of customers, application performance, security
 threats, fraudulent activity and more. Splunk takes this data and makes
 sense of it. Business sense. IT sense. Common sense.
 http://p.sf.net/sfu/splunk-d2dcopy1
 ___
 NAnt-users mailing list
 nant-us...@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/nant-users


--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] SDK docs in nant zipfile

2011-09-14 Thread Dominik Guder

Hi folks,


I started to setup a teamcity build task to automatically create nightlies.

Everything went ok, but I struggled over ndoc and HtmlHelp generation 
for NAnt-SDK.chm.
Ndoc's MSDN documentor has a readonly property for hhc.exe. It search in 
%PROGRAMFILES% but this is the wrong location on x64 machines where it 
will be %PROGRAMFILES(x86)%.

Now there are some possible solutions:
1) I found a working way to use reflection to set this internal 
property on MSDN documentor.

2) Remove the NAnt-SDK.chm from bin (or nightlies) zip. IMHO 
NAnt-SDK.chm not needed for bin zip. I think a better place could be in 
src zip.

So what do you think? Do someone out there need sdk-doc on a regular basis?

Any other ideas?

So far
Dominik

-- 
The answer to the great question of life,
the universe and everything is 42 (Douglas Adams)

--
BlackBerryreg; DevCon Americas, Oct. 18-20, San Francisco, CA
Learn about the latest advances in developing for the 
BlackBerryreg; mobile platform with sessions, labs  more.
See new tools and technologies. Register for BlackBerryreg; DevCon today!
http://p.sf.net/sfu/rim-devcon-copy1 
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] SDK docs in nant zipfile

2011-09-14 Thread Ryan Boggs

Hi Dominik,

On Wed, Sep 14, 2011 at 2:35 PM, Dominik Guder o...@guder.org wrote:
 Hi folks,


 I started to setup a teamcity build task to automatically create nightlies.
That's wonderful.  I'll take a look at that this weekend.

 Everything went ok, but I struggled over ndoc and HtmlHelp generation
 for NAnt-SDK.chm.
 Ndoc's MSDN documentor has a readonly property for hhc.exe. It search in
 %PROGRAMFILES% but this is the wrong location on x64 machines where it
 will be %PROGRAMFILES(x86)%.

 Now there are some possible solutions:
 1) I found a working way to use reflection to set this internal
 property on MSDN documentor.

 2) Remove the NAnt-SDK.chm from bin (or nightlies) zip. IMHO
 NAnt-SDK.chm not needed for bin zip. I think a better place could be in
 src zip.

 So what do you think? Do someone out there need sdk-doc on a regular basis?
Well, I see a value of having the sdk-doc in the bin file for new
releases as projects that build custom nant tasks are probably not
going want to rebuild nant before building their project.  But this is
a question specific to nightly releases, correct?  If so, I can't
imagine the need for the sdk-doc for nightly releases, especially if
the frequency of nighly releases will be increasing.

Other thoughts?

Thanks,
Ryan

 Any other ideas?

 So far
 Dominik

 --
 The answer to the great question of life,
 the universe and everything is 42 (Douglas Adams)

 --
 BlackBerryreg; DevCon Americas, Oct. 18-20, San Francisco, CA
 Learn about the latest advances in developing for the
 BlackBerryreg; mobile platform with sessions, labs  more.
 See new tools and technologies. Register for BlackBerryreg; DevCon today!
 http://p.sf.net/sfu/rim-devcon-copy1
 ___
 nant-developers mailing list
 nant-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/nant-developers


--
BlackBerryreg; DevCon Americas, Oct. 18-20, San Francisco, CA
Learn about the latest advances in developing for the 
BlackBerryreg; mobile platform with sessions, labs  more.
See new tools and technologies. Register for BlackBerryreg; DevCon today!
http://p.sf.net/sfu/rim-devcon-copy1 
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] [ nant-Bugs-3383872 ] Cannot compile.Net 4.0 on the server with Nant 0.91 Alpha 2

2011-09-02 Thread SourceForge . net

Bugs item #3383872, was opened at 2011-08-01 15:28
Message generated for change (Comment added) made by sainzg
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3383872group_id=31650

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: None
Group: 0.91-alpha2
Status: Closed
Resolution: Works For Me
Priority: 9
Private: No
Submitted By: Gus (sainzg)
Assigned to: Nobody/Anonymous (nobody)
Summary: Cannot compile.Net 4.0 on the server with Nant 0.91 Alpha 2 

Initial Comment:
Recently we updated our build server to .Net 4.0 and installed SDK for Windows 
7 and .NET 4.0 as required, then upgraded to Nant. 091.Alpha2 because with 
Alpha 1 could no longer compile .net 3.5 / .net 4.0. We are also using 
Nantcontrib 0.85

We are still having this same error being reported



BUILD FAILED

INTERNAL ERROR

System.Security.SecurityException: Request for the permission of type 'System.Se
curity.Permissions.EnvironmentPermission, mscorlib, Version=4.0.0.0, Culture=neu
tral, PublicKeyToken=b77a5c561934e089' failed.
   at System.Security.CodeAccessSecurityEngine.Check(Object demand, StackCrawlMa
rk stackMark, Boolean isPermSet)
   at System.Security.CodeAccessSecurityEngine.Check(CodeAccessPermission cap, S
tackCrawlMark stackMark)
   at System.Security.CodeAccessPermission.Demand()
   at System.IO.Path.GetTempPath()
   at System.IO.Path.GetTempFileName()
   at NAnt.Contrib.Tasks.MsbuildTask.ExecuteTask()
   at NAnt.Core.Task.Execute()
   at NAnt.Core.Target.Execute()
   at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies)
   at NAnt.Core.Project.Execute()
   at NAnt.Core.Project.Run()
The action that failed was:
Demand
The type of the first permission that failed was:
System.Security.Permissions.EnvironmentPermission
The first permission that failed was:
IPermission class=System.Security.Permissions.EnvironmentPermission, mscorlib,
 Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
version=1
Unrestricted=true/


--

Comment By: Gus (sainzg)
Date: 2011-09-02 07:00

Message:
Got it resolved, windows security issue.

--

Comment By: Gus (sainzg)
Date: 2011-09-02 06:59

Message:
Select all files in one the folders, in my case was the nant-contrib \ bin
files, I've copied them over from another server and windows blocks them
until you mark them safe again. So select all files, right click go to
properties and there will be a button at the very bottom to mark the safe
or the like, click on it, repeat this process for any other files on
another folders you might have copied over from different location.

--

Comment By: Joseph Remes (jremes)
Date: 2011-09-01 15:25

Message:
I am getting a very similar error. 

Request for the permission of type
'System.Security.Permissions.FileIOPermission...'

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3383872group_id=31650

--
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better 
price-free! And you'll get a free Love Thy Logs t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] [ nant-Bugs-3383872 ] Cannot compile.Net 4.0 on the server with Nant 0.91 Alpha 2

2011-09-01 Thread SourceForge . net

Bugs item #3383872, was opened at 2011-08-01 14:28
Message generated for change (Comment added) made by jremes
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3383872group_id=31650

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: None
Group: 0.91-alpha2
Status: Open
Resolution: None
Priority: 9
Private: No
Submitted By: Gus (sainzg)
Assigned to: Nobody/Anonymous (nobody)
Summary: Cannot compile.Net 4.0 on the server with Nant 0.91 Alpha 2 

Initial Comment:
Recently we updated our build server to .Net 4.0 and installed SDK for Windows 
7 and .NET 4.0 as required, then upgraded to Nant. 091.Alpha2 because with 
Alpha 1 could no longer compile .net 3.5 / .net 4.0. We are also using 
Nantcontrib 0.85

We are still having this same error being reported



BUILD FAILED

INTERNAL ERROR

System.Security.SecurityException: Request for the permission of type 'System.Se
curity.Permissions.EnvironmentPermission, mscorlib, Version=4.0.0.0, Culture=neu
tral, PublicKeyToken=b77a5c561934e089' failed.
   at System.Security.CodeAccessSecurityEngine.Check(Object demand, StackCrawlMa
rk stackMark, Boolean isPermSet)
   at System.Security.CodeAccessSecurityEngine.Check(CodeAccessPermission cap, S
tackCrawlMark stackMark)
   at System.Security.CodeAccessPermission.Demand()
   at System.IO.Path.GetTempPath()
   at System.IO.Path.GetTempFileName()
   at NAnt.Contrib.Tasks.MsbuildTask.ExecuteTask()
   at NAnt.Core.Task.Execute()
   at NAnt.Core.Target.Execute()
   at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies)
   at NAnt.Core.Project.Execute()
   at NAnt.Core.Project.Run()
The action that failed was:
Demand
The type of the first permission that failed was:
System.Security.Permissions.EnvironmentPermission
The first permission that failed was:
IPermission class=System.Security.Permissions.EnvironmentPermission, mscorlib,
 Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
version=1
Unrestricted=true/


--

Comment By: Joseph Remes (jremes)
Date: 2011-09-01 14:25

Message:
I am getting a very similar error. 

Request for the permission of type
'System.Security.Permissions.FileIOPermission...'

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3383872group_id=31650

--
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better 
price-free! And you'll get a free Love Thy Logs t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] [ nant-Bugs-3048200 ] NAnt 0.91 Aplha 2 crashes on startup

2011-08-29 Thread SourceForge . net

Bugs item #3048200, was opened at 2010-08-18 23:13
Message generated for change (Comment added) made by 
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3048200group_id=31650

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: Core
Group: 0.91-alpha2
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Rainer Schuster ()
Assigned to: Nobody/Anonymous (nobody)
Summary: NAnt 0.91 Aplha 2 crashes on startup

Initial Comment:
I'm running nant on windows 7 x64 and getting the following exception (german). 
nant crashes in user mode and with elavated rights in admin mode.

Unbehandelte Ausnahme: System.TypeInitializationException: Der 
Typeninitialisierer für NAnt.Console.ConsoleStub hat ei
ne Ausnahme verursacht. --- System.Security.SecurityException: Fehler bei der 
Anforderung des Berechtigungstyps System
.Security.Permissions.FileIOPermission, mscorlib, Version=4.0.0.0, 
Culture=neutral, PublicKeyToken=b77a5c561934e089.
   bei System.Security.CodeAccessSecurityEngine.Check(Object demand, 
StackCrawlMark stackMark, Boolean isPermSet)
   bei System.Security.CodeAccessSecurityEngine.Check(CodeAccessPermission cap, 
StackCrawlMark stackMark)
   bei System.Security.CodeAccessPermission.Demand()
   bei System.AppDomainSetup.VerifyDir(String dir, Boolean normalize)
   bei System.AppDomain.get_BaseDirectory()
   bei log4net.Config.XmlConfiguratorAttribute.Configure(Assembly 
sourceAssembly, ILoggerRepository targetRepository)
   bei log4net.Core.DefaultRepositorySelector.ConfigureRepository(Assembly 
assembly, ILoggerRepository repository)
   bei log4net.Core.DefaultRepositorySelector.CreateRepository(Assembly 
repositoryAssembly, Type repositoryType, String
repositoryName, Boolean readAssemblyAttributes)
   bei log4net.Core.DefaultRepositorySelector.CreateRepository(Assembly 
repositoryAssembly, Type repositoryType)
   bei log4net.Core.DefaultRepositorySelector.GetRepository(Assembly 
repositoryAssembly)
   bei log4net.Core.LoggerManager.GetLogger(Assembly repositoryAssembly, String 
name)
   bei log4net.LogManager.GetLogger(Assembly repositoryAssembly, String name)
   bei log4net.LogManager.GetLogger(Type type)
   bei NAnt.Console.ConsoleStub..cctor()
   --- Ende der internen Ausnahmestapelüberwachung ---
   bei NAnt.Console.ConsoleStub.Main(String[] args)

--

Comment By: Brian ()
Date: 2011-08-29 19:43

Message:
Brandonarp' suggestion worked for me.   Windows 7 x64.  

--

Comment By: Ryan Boggs (rmboggs)
Date: 2011-01-22 04:22

Message:
I would like to hear from others who are experiencing these kinds of issues
if brandonarp's suggestion works for them.  I can't replicate the issue on
any of my test boxes (xp  7 32bit) but I do see the Unblock button in
the properties for the zip file.  However, it works for me whether the zip
is blocked or not.

--

Comment By: Brandon Arp (brandonarp)
Date: 2011-01-21 23:54

Message:
I had this exact same problem.  It comes from the assembly not being
trusted.  Windows 7 will put a flag on downloaded files that the .Net
runtime uses to lower access.  The fix for this is to open the properties
dialog of the .zip file and next to the Security label, click Unblock. 
Then, when you extract the files, they wont be restricted.  Hopefully this
helps.

--

Comment By: Ryan Boggs (rmboggs)
Date: 2010-09-14 00:21

Message:
Looks like some tests failed concerning the registry.  The user account you
were using may not have access to the registry.

--

Comment By: Tony Langford (tonst)
Date: 2010-09-13 10:50

Message:
Thanks, that did seem to do the job :)
The 0.91alpha2 build script failed at the end but it had produced the
needed binaries so not a big deal for me but in case its of use here's the
end of the log. Used nant 0.9 on 2008r2 to build it:

 [exec]  [nant]
C:\nant-0.91-alpha2\tests\NAnt.Win32\NAnt.Win32.build te
st
 [exec] Buildfile:
file:///C:/nant-0.91-alpha2/tests/NAnt.Win32/
NAnt.Win32.build
 [exec] Target framework: Microsoft .NET Framework 3.5
 [exec] Target(s) specified: test
 [exec]
 [exec]
 [exec] build:
 [exec]
 [exec]
 [exec] test:
 [exec]
 [exec][nunit2] Tests run: 2, Failures: 1, Not run: 0,
Time:
 1.685 seconds
 [exec][nunit2]
 [exec][nunit2] Failures:
 [exec][nunit2] 1)
Tests.NAnt.Win32.Tasks.ReadRegistryTest.T
est_Read_Defaults : Tests.NAnt.Core.TestBuildException :

Re: [nant-dev] Repository maintenance folder deletion

2011-08-19 Thread Dominik Guder

Hi Leszek,

Am 19.08.2011 10:14, schrieb Leszek Ciesielski:
 I am curating https://github.com/skolima/NAnt git mirror and this is
 problematic. Git 'cvsimport' command does not handle file deletions
 (due to the broken way cvs itself records them), so nmake is still
 present in the (automatically updated) mirror. I will push a commit
 deleting the file, but I'm not willing to rewrite history to remove
 it, as this would break any existing clones. Is this an acceptable
 solution?


I see you point. But I'm no sure if removing the file is enough. I think 
that your mirror is out of sync and I have some doubts that updates are 
working.
Maybe you can try to wipe out the last commit (IMHO rebase might can do 
this) or do a fresh 'cvsimport'.

Im really sorry for this trouble and I'm wiling to assist you to get 
your mirror up and running again.

BTW: We are on the way to github too. But we want to get out next nant 
version first.

So far Dominik


-- 
The answer to the great question of life,
the universe and everything is 42 (Douglas Adams)

--
Get a FREE DOWNLOAD! and learn more about uberSVN rich system, 
user administration capabilities and model configuration. Take 
the hassle out of deploying and managing Subversion and the 
tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] Configuration to Target 3.5/4.0 Client Profiles?

2011-08-15 Thread Stefan Bodewig

Hi,

over in log4net land we are seriously ramping up for a new release (who
would have ever thought that 8-) and need to provide assemblies stripped
down to the client profiles.  Has anybody around here got a
configuration that can be used to target the client frameworks?

My first guess, but I haven't really looked into it, is that one mostly
needs to remove some assemblies from the reference-assemblies element of
the corresponding full framework target.

Stefan

--
uberSVN's rich system and user administration capabilities and model 
configuration take the hassle out of deploying and managing Subversion and 
the tools developers use with it. Learn more about uberSVN and get a free 
download at:  http://p.sf.net/sfu/wandisco-dev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] [ nant-Bugs-3390653 ] xmlpeek broken in 0.91alpha2

2011-08-12 Thread SourceForge . net

Bugs item #3390653, was opened at 2011-08-12 13:11
Message generated for change (Tracker Item Submitted) made by 
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3390653group_id=31650

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: Tasks
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Jiho Han ()
Assigned to: Nobody/Anonymous (nobody)
Summary: xmlpeek broken in 0.91alpha2

Initial Comment:
xmlpeek would return the inner xml of the node found in the property specified. 
 This worked in 0.85 but returns an empty string in 0.91alpha2.
I'm not certain whether this has existed in previous versions or not.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3390653group_id=31650

--
FREE DOWNLOAD - uberSVN with Social Coding for Subversion.
Subversion made easy with a complete admin console. Easy 
to use, easy to manage, easy to install, easy to extend. 
Get a Free download of the new open ALM Subversion platform now.
http://p.sf.net/sfu/wandisco-dev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Updates to MSBuild VSNet Tasks

2011-08-07 Thread Dominik Guder

Hi Ryan,

these changes are good rom my point of view.
I have ony one minor thing what I can't test since I have difficulties 
to debug nant at the moment.

MSBuildProject.cs within DetermineProductVersion line 279
 if (_productVerNode != null) {
 Version _ver = new Version(_productVerNode.InnerText);

_productVerNode.InnerText might be empty especially in vb.net projects. 
Which results in an exception since  is not valid vor Version 
constuctor. You might use following:

if (_productVerNode != null  
!StringUtils.IsNullOrEmpty(_productVerNode.InnerText))

Well done

Dominik

Am 06.08.2011 21:12, schrieb Ryan Boggs:
 Hi,

 I'm thinking that at this point, since I believe I fixed the one or two
 things from the comments I received some months ago, I will commit these
 changes by end of day Monday unless I hear any objections before then.
  From there, I will perform some nightlys with these changes for public
 testing.  Sound good?

 Thanks,
 Ryan




-- 
The answer to the great question of life,
the universe and everything is 42 (Douglas Adams)

--
BlackBerryreg; DevCon Americas, Oct. 18-20, San Francisco, CA
The must-attend event for mobile developers. Connect with experts. 
Get tools for creating Super Apps. See the latest technologies.
Sessions, hands-on labs, demos  much more. Register early  save!
http://p.sf.net/sfu/rim-blackberry-1
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Updates to MSBuild VSNet Tasks

2011-08-07 Thread Ryan Boggs

Ah, good catches.  I've made the changes in my tree and they are ready for
committing.

If I don't hear anything else, all of these changes that Dominik, Martin,
and myself have worked hard on will be committed tonight.

Thanks everyone :)
Ryan

On Sun, Aug 7, 2011 at 1:33 PM, Dominik Guder o...@guder.org wrote:

 Am 06.08.2011 21:12, schrieb Ryan Boggs:

 Hi,


 I'm thinking that at this point, since I believe I fixed the one or two
 things from the comments I received some months ago, I will commit these
 changes by end of day Monday unless I hear any objections before then.
  From there, I will perform some nightlys with these changes for public
 testing.  Sound good?

  Another minor fix:
 please add the missing /list entry to xmldoc

 Thanks

 Dominik

 --
 The answer to the great question of life,
 the universe and everything is 42 (Douglas Adams)


 --
 BlackBerryreg; DevCon Americas, Oct. 18-20, San Francisco, CA
 The must-attend event for mobile developers. Connect with experts.
 Get tools for creating Super Apps. See the latest technologies.
 Sessions, hands-on labs, demos  much more. Register early  save!
 http://p.sf.net/sfu/rim-blackberry-1
 ___
 nant-developers mailing list
 nant-developers@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/nant-developers


--
BlackBerryreg; DevCon Americas, Oct. 18-20, San Francisco, CA
The must-attend event for mobile developers. Connect with experts. 
Get tools for creating Super Apps. See the latest technologies.
Sessions, hands-on labs, demos  much more. Register early  save!
http://p.sf.net/sfu/rim-blackberry-1___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Updates to MSBuild VSNet Tasks

2011-08-06 Thread Ryan Boggs

Hi,

I'm thinking that at this point, since I believe I fixed the one or two
things from the comments I received some months ago, I will commit these
changes by end of day Monday unless I hear any objections before then. From
there, I will perform some nightlys with these changes for public testing.
Sound good?

Thanks,
Ryan

On Fri, Jul 29, 2011 at 10:28 PM, Ryan Boggs rmbo...@gmail.com wrote:

Anyone had a change to review this yet? Does it look ok to commit? Please
let me know.

Thanks,
Ryan

On Fri, Jul 22, 2011 at 5:17 PM, Ryan Boggs rmbo...@gmail.com wrote:

Updated diff to include changes to the DetermineProductVersion method.

I decided that rather than relying on one element or attribute tag,
might as well check through them all. This method will now check for
the ProductVersion element first for the msbuild project version. If
that element doesn't exist, it will then check for the
TargetFrameworkVersion element. If neither of those elements exist,
it'll then check the ToolsVersion attribute of the Project for a
version number. If none of these items exist in the msbuild file, the
method will default to 2.0. I figured that this approach would be the
most detailed in getting the propert msbuild project file's version
number.

The diff is located in the patches section in sourceforge:

https://sourceforge.net/tracker/index.php?func=detailaid=3311661group_id=31650atid=402870

I also opened a new review as the old one was getting cluttered. It is
CR-63.
https://fisheye1.atlassian.com/cru/CR-63

Please let me know if this looks good to commit to the tree.

Thanks,
Ryan

On Fri, Jul 22, 2011 at 11:43 AM, Ryan Boggs rmbo...@gmail.com wrote:
Hi,

Thought I put in such a patch but it looks like I didn't yet. I will
see about creating it today.

Thanks,
Ryan

On Fri, Jul 22, 2011 at 2:54 AM, Martin Aliger martin_ali...@gordic.cz
wrote:
Yes, your solution is better. Depending on ProjectVersion was throwing
odd
exceptions when it was not included (which happens even in VS for
whatever
reason):

internalerror
typeSystem.ArgumentException/type
message![CDATA[Version string portion was too short or too
long.]]/message
stacktrace![CDATA[ at
System.Version.VersionResult.SetFailure(ParseFailureKind failure,
String
argument)
at System.Version.TryParseVersion(String version, VersionResult
result)
at System.Version.Parse(String input)
at System.Version..ctor(String version)
at NAnt.MSBuild.MSBuildProject.DetermineProductVersion(XmlElement
docElement)
at NAnt.VSNet.ProjectBase..ctor(XmlElement xmlDefinition,
SolutionTask
solutionTask, TempFileCollection temporaryFiles, GacCache gacCache,
ReferencesResolver referencesResolver, DirectoryInfo outputDir)
at NAnt.MSBuild.MSBuildProject..ctor(SolutionBase solution, String
projectPath, XmlElement xmlDefinition, SolutionTask solutionTask,
TempFileCollection tfc, GacCache gacCache, ReferencesResolver
refResolver,
DirectoryInfo outputDir)
...

ToolsVersion should be more accurate as well. I'd need to test it yet,
though.

Martin Aliger

-Original Message-
From: Ryan Boggs [mailto:rmbo...@gmail.com]
Sent: Wednesday, June 22, 2011 2:36 AM
Subject: Re: [nant-dev] Updates to MSBuild VSNet Tasks

Hey Dominik,

I saw your notes in the atlassian review and I see your point. It
would
probably make more sense to use the ToolsVersion property rather than
relying on the PropertyGroup/ProductVersion xml node. I just took a
look at
some project files created by Sharpdevelop and none of the project
files had
that xml node but they did have the ToolsVersion property. I can give
this
another run through later this week.

Thanks,
Ryan

--
BlackBerryreg; DevCon Americas, Oct. 18-20, San Francisco, CA
The must-attend event for mobile developers. Connect with experts.
Get tools for creating Super Apps. See the latest technologies.
Sessions, hands-on labs, demos much more. Register early save!
http://p.sf.net/sfu/rim-blackberry-1___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] [ nant-Bugs-3383872 ] Cannot compile.Net 4.0 on the server with Nant 0.91 Alpha 2

2011-08-01 Thread SourceForge.net

Bugs item #3383872, was opened at 2011-08-01 15:28
Message generated for change (Settings changed) made by sainzg
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3383872group_id=31650

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: None
Group: 0.91-alpha2
Status: Open
Resolution: None
Priority: 9
Private: No
Submitted By: Gus (sainzg)
Assigned to: Nobody/Anonymous (nobody)
Summary: Cannot compile.Net 4.0 on the server with Nant 0.91 Alpha 2 

Initial Comment:
Recently we updated our build server to .Net 4.0 and installed SDK for Windows 
7 and .NET 4.0 as required, then upgraded to Nant. 091.Alpha2 because with 
Alpha 1 could no longer compile .net 3.5 / .net 4.0. We are also using 
Nantcontrib 0.85

We are still having this same error being reported



BUILD FAILED

INTERNAL ERROR

System.Security.SecurityException: Request for the permission of type 'System.Se
curity.Permissions.EnvironmentPermission, mscorlib, Version=4.0.0.0, Culture=neu
tral, PublicKeyToken=b77a5c561934e089' failed.
   at System.Security.CodeAccessSecurityEngine.Check(Object demand, StackCrawlMa
rk stackMark, Boolean isPermSet)
   at System.Security.CodeAccessSecurityEngine.Check(CodeAccessPermission cap, S
tackCrawlMark stackMark)
   at System.Security.CodeAccessPermission.Demand()
   at System.IO.Path.GetTempPath()
   at System.IO.Path.GetTempFileName()
   at NAnt.Contrib.Tasks.MsbuildTask.ExecuteTask()
   at NAnt.Core.Task.Execute()
   at NAnt.Core.Target.Execute()
   at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies)
   at NAnt.Core.Project.Execute()
   at NAnt.Core.Project.Run()
The action that failed was:
Demand
The type of the first permission that failed was:
System.Security.Permissions.EnvironmentPermission
The first permission that failed was:
IPermission class=System.Security.Permissions.EnvironmentPermission, mscorlib,
 Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
version=1
Unrestricted=true/


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3383872group_id=31650

--
BlackBerryreg; DevCon Americas, Oct. 18-20, San Francisco, CA
The must-attend event for mobile developers. Connect with experts. 
Get tools for creating Super Apps. See the latest technologies.
Sessions, hands-on labs, demos  much more. Register early  save!
http://p.sf.net/sfu/rim-blackberry-1
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Updates to MSBuild VSNet Tasks

2011-07-29 Thread Ryan Boggs

Anyone had a change to review this yet? Does it look ok to commit? Please
let me know.

Thanks,
Ryan

On Fri, Jul 22, 2011 at 5:17 PM, Ryan Boggs rmbo...@gmail.com wrote:

Updated diff to include changes to the DetermineProductVersion method.

The diff is located in the patches section in sourceforge:

https://sourceforge.net/tracker/index.php?func=detailaid=3311661group_id=31650atid=402870

I also opened a new review as the old one was getting cluttered. It is
CR-63.
https://fisheye1.atlassian.com/cru/CR-63

Please let me know if this looks good to commit to the tree.

Thanks,
Ryan

On Fri, Jul 22, 2011 at 11:43 AM, Ryan Boggs rmbo...@gmail.com wrote:
Hi,

Thought I put in such a patch but it looks like I didn't yet. I will
see about creating it today.

Thanks,
Ryan

internalerror
typeSystem.ArgumentException/type
message![CDATA[Version string portion was too short or too
long.]]/message
stacktrace![CDATA[ at
System.Version.VersionResult.SetFailure(ParseFailureKind failure, String
argument)
at System.Version.TryParseVersion(String version, VersionResult
result)
at System.Version.Parse(String input)
at System.Version..ctor(String version)
at NAnt.MSBuild.MSBuildProject.DetermineProductVersion(XmlElement
docElement)
at NAnt.VSNet.ProjectBase..ctor(XmlElement xmlDefinition, SolutionTask
solutionTask, TempFileCollection temporaryFiles, GacCache gacCache,
ReferencesResolver referencesResolver, DirectoryInfo outputDir)
at NAnt.MSBuild.MSBuildProject..ctor(SolutionBase solution, String
projectPath, XmlElement xmlDefinition, SolutionTask solutionTask,
TempFileCollection tfc, GacCache gacCache, ReferencesResolver
refResolver,
DirectoryInfo outputDir)
...

ToolsVersion should be more accurate as well. I'd need to test it yet,
though.

Martin Aliger

-Original Message-
From: Ryan Boggs [mailto:rmbo...@gmail.com]
Sent: Wednesday, June 22, 2011 2:36 AM
Subject: Re: [nant-dev] Updates to MSBuild VSNet Tasks

Hey Dominik,

I saw your notes in the atlassian review and I see your point. It would
probably make more sense to use the ToolsVersion property rather than
relying on the PropertyGroup/ProductVersion xml node. I just took a
look at
some project files created by Sharpdevelop and none of the project files
had
that xml node but they did have the ToolsVersion property. I can give
this
another run through later this week.

Thanks,
Ryan

--
Got Input? Slashdot Needs You.
Take our quick survey online. Come on, we don't ask for help often.
Plus, you'll get a chance to win $100 to spend on ThinkGeek.
http://p.sf.net/sfu/slashdot-survey___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Updates to MSBuild VSNet Tasks

2011-07-22 Thread Martin Aliger

Yes, your solution is better. Depending on ProjectVersion was throwing odd
exceptions when it was not included (which happens even in VS for whatever
reason):


internalerror
  typeSystem.ArgumentException/type
  message![CDATA[Version string portion was too short or too
long.]]/message
  stacktrace![CDATA[   at
System.Version.VersionResult.SetFailure(ParseFailureKind failure, String
argument)
   at System.Version.TryParseVersion(String version, VersionResult result)
   at System.Version.Parse(String input)
   at System.Version..ctor(String version)
   at NAnt.MSBuild.MSBuildProject.DetermineProductVersion(XmlElement
docElement)
   at NAnt.VSNet.ProjectBase..ctor(XmlElement xmlDefinition, SolutionTask
solutionTask, TempFileCollection temporaryFiles, GacCache gacCache,
ReferencesResolver referencesResolver, DirectoryInfo outputDir)
   at NAnt.MSBuild.MSBuildProject..ctor(SolutionBase solution, String
projectPath, XmlElement xmlDefinition, SolutionTask solutionTask,
TempFileCollection tfc, GacCache gacCache, ReferencesResolver refResolver,
DirectoryInfo outputDir)
...

ToolsVersion should be more accurate as well. I'd need to test it yet,
though.

Martin Aliger

-Original Message-
From: Ryan Boggs [mailto:rmbo...@gmail.com] 
Sent: Wednesday, June 22, 2011 2:36 AM
Subject: Re: [nant-dev] Updates to MSBuild  VSNet Tasks

Hey Dominik,

I saw your notes in the atlassian review and I see your point.  It would
probably make more sense to use the ToolsVersion property rather than
relying on the PropertyGroup/ProductVersion xml node.  I just took a look at
some project files created by Sharpdevelop and none of the project files had
that xml node but they did have the ToolsVersion property.  I can give this
another run through later this week.

Thanks,
Ryan


--
10 Tips for Better Web Security
Learn 10 ways to better secure your business today. Topics covered include:
Web security, SSL, hacker attacks  Denial of Service (DoS), private keys,
security Microsoft Exchange, secure Instant Messaging, and much more.
http://www.accelacomm.com/jaw/sfnl/114/51426210/
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Updates to MSBuild VSNet Tasks

2011-07-22 Thread Ryan Boggs

Hi,

Thought I put in such a patch but it looks like I didn't yet.  I will
see about creating it today.

Thanks,
Ryan

On Fri, Jul 22, 2011 at 2:54 AM, Martin Aliger martin_ali...@gordic.cz wrote:
 Yes, your solution is better. Depending on ProjectVersion was throwing odd
 exceptions when it was not included (which happens even in VS for whatever
 reason):


    internalerror
      typeSystem.ArgumentException/type
      message![CDATA[Version string portion was too short or too
 long.]]/message
      stacktrace![CDATA[   at
 System.Version.VersionResult.SetFailure(ParseFailureKind failure, String
 argument)
   at System.Version.TryParseVersion(String version, VersionResult result)
   at System.Version.Parse(String input)
   at System.Version..ctor(String version)
   at NAnt.MSBuild.MSBuildProject.DetermineProductVersion(XmlElement
 docElement)
   at NAnt.VSNet.ProjectBase..ctor(XmlElement xmlDefinition, SolutionTask
 solutionTask, TempFileCollection temporaryFiles, GacCache gacCache,
 ReferencesResolver referencesResolver, DirectoryInfo outputDir)
   at NAnt.MSBuild.MSBuildProject..ctor(SolutionBase solution, String
 projectPath, XmlElement xmlDefinition, SolutionTask solutionTask,
 TempFileCollection tfc, GacCache gacCache, ReferencesResolver refResolver,
 DirectoryInfo outputDir)
 ...

 ToolsVersion should be more accurate as well. I'd need to test it yet,
 though.

 Martin Aliger

 -Original Message-
 From: Ryan Boggs [mailto:rmbo...@gmail.com]
 Sent: Wednesday, June 22, 2011 2:36 AM
 Subject: Re: [nant-dev] Updates to MSBuild  VSNet Tasks

 Hey Dominik,

 I saw your notes in the atlassian review and I see your point.  It would
 probably make more sense to use the ToolsVersion property rather than
 relying on the PropertyGroup/ProductVersion xml node.  I just took a look at
 some project files created by Sharpdevelop and none of the project files had
 that xml node but they did have the ToolsVersion property.  I can give this
 another run through later this week.

 Thanks,
 Ryan



--
10 Tips for Better Web Security
Learn 10 ways to better secure your business today. Topics covered include:
Web security, SSL, hacker attacks  Denial of Service (DoS), private keys,
security Microsoft Exchange, secure Instant Messaging, and much more.
http://www.accelacomm.com/jaw/sfnl/114/51426210/
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Updates to MSBuild VSNet Tasks

2011-07-22 Thread Ryan Boggs

Updated diff to include changes to the DetermineProductVersion method.

I decided that rather than relying on one element or attribute tag,
might as well check through them all.  This method will now check for
the ProductVersion element first for the msbuild project version.  If
that element doesn't exist, it will then check for the
TargetFrameworkVersion element.  If neither of those elements exist,
it'll then check the ToolsVersion attribute of the Project for a
version number.  If none of these items exist in the msbuild file, the
method will default to 2.0.  I figured that this approach would be the
most detailed in getting the propert msbuild project file's version
number.

The diff is located in the patches section in sourceforge:
https://sourceforge.net/tracker/index.php?func=detailaid=3311661group_id=31650atid=402870

I also opened a new review as the old one was getting cluttered.  It is CR-63.
https://fisheye1.atlassian.com/cru/CR-63

Please let me know if this looks good to commit to the tree.

Thanks,
Ryan

On Fri, Jul 22, 2011 at 11:43 AM, Ryan Boggs rmbo...@gmail.com wrote:
 Hi,

 Thought I put in such a patch but it looks like I didn't yet.  I will
 see about creating it today.

 Thanks,
 Ryan

 On Fri, Jul 22, 2011 at 2:54 AM, Martin Aliger martin_ali...@gordic.cz 
 wrote:
 Yes, your solution is better. Depending on ProjectVersion was throwing odd
 exceptions when it was not included (which happens even in VS for whatever
 reason):


    internalerror
      typeSystem.ArgumentException/type
      message![CDATA[Version string portion was too short or too
 long.]]/message
      stacktrace![CDATA[   at
 System.Version.VersionResult.SetFailure(ParseFailureKind failure, String
 argument)
   at System.Version.TryParseVersion(String version, VersionResult result)
   at System.Version.Parse(String input)
   at System.Version..ctor(String version)
   at NAnt.MSBuild.MSBuildProject.DetermineProductVersion(XmlElement
 docElement)
   at NAnt.VSNet.ProjectBase..ctor(XmlElement xmlDefinition, SolutionTask
 solutionTask, TempFileCollection temporaryFiles, GacCache gacCache,
 ReferencesResolver referencesResolver, DirectoryInfo outputDir)
   at NAnt.MSBuild.MSBuildProject..ctor(SolutionBase solution, String
 projectPath, XmlElement xmlDefinition, SolutionTask solutionTask,
 TempFileCollection tfc, GacCache gacCache, ReferencesResolver refResolver,
 DirectoryInfo outputDir)
 ...

 ToolsVersion should be more accurate as well. I'd need to test it yet,
 though.

 Martin Aliger

 -Original Message-
 From: Ryan Boggs [mailto:rmbo...@gmail.com]
 Sent: Wednesday, June 22, 2011 2:36 AM
 Subject: Re: [nant-dev] Updates to MSBuild  VSNet Tasks

 Hey Dominik,

 I saw your notes in the atlassian review and I see your point.  It would
 probably make more sense to use the ToolsVersion property rather than
 relying on the PropertyGroup/ProductVersion xml node.  I just took a look at
 some project files created by Sharpdevelop and none of the project files had
 that xml node but they did have the ToolsVersion property.  I can give this
 another run through later this week.

 Thanks,
 Ryan




--
Storage Efficiency Calculator
This modeling tool is based on patent-pending intellectual property that
has been used successfully in hundreds of IBM storage optimization engage-
ments, worldwide.  Store less, Store more with what you own, Move data to 
the right place. Try It Now! http://www.accelacomm.com/jaw/sfnl/114/51427378/
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] [ nant-Bugs-3058913 ] xml schema for description is invalid


Bugs item #3058913, was opened at 2010-09-03 16:51
Message generated for change (Comment added) made by 
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3058913group_id=31650

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: Framework support
Group: 0.91-alpha2
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: owl128 (owl128)
Assigned to: Nobody/Anonymous (nobody)
Summary: xml schema for description is invalid

Initial Comment:
example for a build file:
  project xmlns=http://nant.sf.net/release/0.91-alpha2/nant.xsd; name=a
descriptionmy description/description
  /project
This will note the text between the description tags as invalid. 

I suggest to fix the content of nant.xsd file by one of the followings:

Replace: xs:complexType name=NAnt.Core.Tasks.DescriptionTask
by  xs:complexType name=NAnt.Core.Tasks.DescriptionTask mixed=true

or

replace the occurrences of xs:element name=description 
type=nant:NAnt.Core.Tasks.DescriptionTask /
by  xs:element name=description type=xs:string /


--

Comment By: Sojourner ()
Date: 2011-07-07 21:27

Message:
rmboggs:

That would indeed shut it up - mixed=true is what you want to get a
complextype to accept text content. However as pointed out by dogu, the
schema is autogenerated. What is really needed is a change to the schema
task to get it to apply a mixed content model when it generates xsd types
for tasks, based on some criterion. Having only just viewed Nant source for
the first time today, I don't have a clear idea how that might be
accomplished.

The Description task doesn't appear to do anything; maybe it would be as
simple as adding a 'text' property to the description task, which should
appear as a 'text' attribute in the build file? NAnt by convention seems
not to use element content to express very much at all.

--

Comment By: Ryan Boggs (rmboggs)
Date: 2010-09-13 04:39

Message:
I'm trying to get familiar with xsd in general.  From what I can see, the
closest I can get to the mixed is with this:

  xs:complexType name=Target mixed=true
xs:choice minOccurs=0 maxOccurs=unbounded
  xs:complexType name=NAnt.Core.Tasks.DescriptionTask

however, I don't know if that will resolve this issue.

Thanks,
Ryan

--

Comment By: Dominik Guder (dogu)
Date: 2010-09-05 20:58

Message:
Hi, 

I stubled about this long time ago. There are some more tasks like the
echo task if I remember correctly. 
Changing this in xsd file itself would be easy. But this xsd file is
created automatically by nantschema task. So we need to find a way to
resolve this there. But this was to much effort for me and I stopped in
validating my build files with other tools than nant itself.


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3058913group_id=31650

--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] [ nant-Bugs-3058913 ] xml schema for description is invalid


Bugs item #3058913, was opened at 2010-09-03 09:51
Message generated for change (Comment added) made by rmboggs
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3058913group_id=31650

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: Framework support
Group: 0.91-alpha2
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: owl128 (owl128)
Assigned to: Nobody/Anonymous (nobody)
Summary: xml schema for description is invalid

Initial Comment:
example for a build file:
  project xmlns=http://nant.sf.net/release/0.91-alpha2/nant.xsd; name=a
descriptionmy description/description
  /project
This will note the text between the description tags as invalid. 

I suggest to fix the content of nant.xsd file by one of the followings:

Replace: xs:complexType name=NAnt.Core.Tasks.DescriptionTask
by  xs:complexType name=NAnt.Core.Tasks.DescriptionTask mixed=true

or

replace the occurrences of xs:element name=description 
type=nant:NAnt.Core.Tasks.DescriptionTask /
by  xs:element name=description type=xs:string /


--

Comment By: Ryan Boggs (rmboggs)
Date: 2011-07-07 19:18

Message:
It's been awhile...

I took a look in the source and I think I got it.  It looks like an easy
fix.  One question, is there any other complex types that need this
modification?

--

Comment By: Sojourner ()
Date: 2011-07-07 14:27

Message:
rmboggs:

That would indeed shut it up - mixed=true is what you want to get a
complextype to accept text content. However as pointed out by dogu, the
schema is autogenerated. What is really needed is a change to the schema
task to get it to apply a mixed content model when it generates xsd types
for tasks, based on some criterion. Having only just viewed Nant source for
the first time today, I don't have a clear idea how that might be
accomplished.

The Description task doesn't appear to do anything; maybe it would be as
simple as adding a 'text' property to the description task, which should
appear as a 'text' attribute in the build file? NAnt by convention seems
not to use element content to express very much at all.

--

Comment By: Ryan Boggs (rmboggs)
Date: 2010-09-12 21:39

Message:
I'm trying to get familiar with xsd in general.  From what I can see, the
closest I can get to the mixed is with this:

  xs:complexType name=Target mixed=true
xs:choice minOccurs=0 maxOccurs=unbounded
  xs:complexType name=NAnt.Core.Tasks.DescriptionTask

however, I don't know if that will resolve this issue.

Thanks,
Ryan

--

Comment By: Dominik Guder (dogu)
Date: 2010-09-05 13:58

Message:
Hi, 

I stubled about this long time ago. There are some more tasks like the
echo task if I remember correctly. 
Changing this in xsd file itself would be easy. But this xsd file is
created automatically by nantschema task. So we need to find a way to
resolve this there. But this was to much effort for me and I stopped in
validating my build files with other tools than nant itself.


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3058913group_id=31650

--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] [ nant-Bugs-3058913 ] xml schema for description is invalid


Bugs item #3058913, was opened at 2010-09-03 09:51
Message generated for change (Comment added) made by rmboggs
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3058913group_id=31650

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: Framework support
Group: 0.91-alpha2
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: owl128 (owl128)
Assigned to: Nobody/Anonymous (nobody)
Summary: xml schema for description is invalid

Initial Comment:
example for a build file:
  project xmlns=http://nant.sf.net/release/0.91-alpha2/nant.xsd; name=a
descriptionmy description/description
  /project
This will note the text between the description tags as invalid. 

I suggest to fix the content of nant.xsd file by one of the followings:

Replace: xs:complexType name=NAnt.Core.Tasks.DescriptionTask
by  xs:complexType name=NAnt.Core.Tasks.DescriptionTask mixed=true

or

replace the occurrences of xs:element name=description 
type=nant:NAnt.Core.Tasks.DescriptionTask /
by  xs:element name=description type=xs:string /


--

Comment By: Ryan Boggs (rmboggs)
Date: 2011-07-07 21:31

Message:
Nevermind, I set it up so setting more tasks with the mixed attribute is
very easy.  Will commit fix shortly.

--

Comment By: Ryan Boggs (rmboggs)
Date: 2011-07-07 19:18

Message:
It's been awhile...

I took a look in the source and I think I got it.  It looks like an easy
fix.  One question, is there any other complex types that need this
modification?

--

Comment By: Sojourner ()
Date: 2011-07-07 14:27

Message:
rmboggs:

That would indeed shut it up - mixed=true is what you want to get a
complextype to accept text content. However as pointed out by dogu, the
schema is autogenerated. What is really needed is a change to the schema
task to get it to apply a mixed content model when it generates xsd types
for tasks, based on some criterion. Having only just viewed Nant source for
the first time today, I don't have a clear idea how that might be
accomplished.

The Description task doesn't appear to do anything; maybe it would be as
simple as adding a 'text' property to the description task, which should
appear as a 'text' attribute in the build file? NAnt by convention seems
not to use element content to express very much at all.

--

Comment By: Ryan Boggs (rmboggs)
Date: 2010-09-12 21:39

Message:
I'm trying to get familiar with xsd in general.  From what I can see, the
closest I can get to the mixed is with this:

  xs:complexType name=Target mixed=true
xs:choice minOccurs=0 maxOccurs=unbounded
  xs:complexType name=NAnt.Core.Tasks.DescriptionTask

however, I don't know if that will resolve this issue.

Thanks,
Ryan

--

Comment By: Dominik Guder (dogu)
Date: 2010-09-05 13:58

Message:
Hi, 

I stubled about this long time ago. There are some more tasks like the
echo task if I remember correctly. 
Changing this in xsd file itself would be easy. But this xsd file is
created automatically by nantschema task. So we need to find a way to
resolve this there. But this was to much effort for me and I stopped in
validating my build files with other tools than nant itself.


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3058913group_id=31650

--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] [ nant-Bugs-3058913 ] xml schema for description is invalid


Bugs item #3058913, was opened at 2010-09-03 09:51
Message generated for change (Comment added) made by rmboggs
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3058913group_id=31650

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: Framework support
Group: 0.91-alpha2
Status: Open
Resolution: Fixed
Priority: 5
Private: No
Submitted By: owl128 (owl128)
Assigned to: Ryan Boggs (rmboggs)
Summary: xml schema for description is invalid

Initial Comment:
example for a build file:
  project xmlns=http://nant.sf.net/release/0.91-alpha2/nant.xsd; name=a
descriptionmy description/description
  /project
This will note the text between the description tags as invalid. 

I suggest to fix the content of nant.xsd file by one of the followings:

Replace: xs:complexType name=NAnt.Core.Tasks.DescriptionTask
by  xs:complexType name=NAnt.Core.Tasks.DescriptionTask mixed=true

or

replace the occurrences of xs:element name=description 
type=nant:NAnt.Core.Tasks.DescriptionTask /
by  xs:element name=description type=xs:string /


--

Comment By: Ryan Boggs (rmboggs)
Date: 2011-07-07 21:59

Message:
Fix committed.

--

Comment By: Ryan Boggs (rmboggs)
Date: 2011-07-07 21:31

Message:
Nevermind, I set it up so setting more tasks with the mixed attribute is
very easy.  Will commit fix shortly.

--

Comment By: Ryan Boggs (rmboggs)
Date: 2011-07-07 19:18

Message:
It's been awhile...

I took a look in the source and I think I got it.  It looks like an easy
fix.  One question, is there any other complex types that need this
modification?

--

Comment By: Sojourner ()
Date: 2011-07-07 14:27

Message:
rmboggs:

That would indeed shut it up - mixed=true is what you want to get a
complextype to accept text content. However as pointed out by dogu, the
schema is autogenerated. What is really needed is a change to the schema
task to get it to apply a mixed content model when it generates xsd types
for tasks, based on some criterion. Having only just viewed Nant source for
the first time today, I don't have a clear idea how that might be
accomplished.

The Description task doesn't appear to do anything; maybe it would be as
simple as adding a 'text' property to the description task, which should
appear as a 'text' attribute in the build file? NAnt by convention seems
not to use element content to express very much at all.

--

Comment By: Ryan Boggs (rmboggs)
Date: 2010-09-12 21:39

Message:
I'm trying to get familiar with xsd in general.  From what I can see, the
closest I can get to the mixed is with this:

  xs:complexType name=Target mixed=true
xs:choice minOccurs=0 maxOccurs=unbounded
  xs:complexType name=NAnt.Core.Tasks.DescriptionTask

however, I don't know if that will resolve this issue.

Thanks,
Ryan

--

Comment By: Dominik Guder (dogu)
Date: 2010-09-05 13:58

Message:
Hi, 

I stubled about this long time ago. There are some more tasks like the
echo task if I remember correctly. 
Changing this in xsd file itself would be easy. But this xsd file is
created automatically by nantschema task. So we need to find a way to
resolve this there. But this was to much effort for me and I stopped in
validating my build files with other tools than nant itself.


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3058913group_id=31650

--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Updates to MSBuild VSNet Tasks

2011-06-16 Thread Ryan Boggs

Hi,

Please see inline.

Thanks,
Ryan

On Jun 16, 2011, at 2:39 AM, Martin Aliger martin_ali...@gordic.cz wrote:

 Hi Ryan, sln file handling is some kind of broken since VS2005. They 
 only work with 2002/2003. I would not spend to much time for now in 
 sln file handling in VS2005 and up.
 Eww, makes sense.  Well, not to let my work go to waste, I think I know why
 it isn't working.  The plugins that contains the schema information for
 VS2005+ solution files (NAnt.MSBuild.dll) doesn't seem to be getting picked
 up during NAnt's plugin discovery phase.
 However, I have been having difficulty trying to locate where the plugin
 discovery phase occurs in NAnt to make sure that they are getting picked up.
 There is also the fact that the VS2005+ solution plugin classes are marked
 as internal but I am not sure how much of an impact that is making overall.
 
 Discovery mechanism was made by me and Gert some time ago. I could look into
 it...
Thanks Martin. I thought your names looked familiar. :)
 
 SolutionFactory.cs is main branching thingy. Providers itself are registred
 though Core's IPluginConsumer and ISolutionBuildProvider interfaces.
I see that and it seems to be working ok with the classes within the NAnt.VSNet 
assembly.  It just won't pickup the classes from the NAnt.MSBuild assembly.  If 
u can point me to where in the code that the solution task begins to search for 
plugins in external assemblies, I can research further as well.
 
 M.
 

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] Updates to MSBuild VSNet Tasks

2011-06-16 Thread Martin Aliger

I just checked and it correctly resolves all the MSBuild providers on my
machine.
Maybe it is becouse I have NAnt.MSBuild.dll in same directory as NAnt.exe?
Maybe plugins do not resolve when in one of those Framework lib which is
default for MSBuild assembly atm (no idea why). Or perhaps the order in
which assemblies are loaded?

The registration is done in PluginScanner class from Core. All loaded types
should be send into that (via TypeFactory).

Btw: I noticed, the solution providers from MSBuild assembly got VSNet
namespace. Maybe it should be changed, for clarity.

Martin Aliger



-Original Message-
From: Ryan Boggs [mailto:rmbo...@gmail.com] 
Sent: Thursday, June 16, 2011 3:37 PM
To: Martin Aliger
Cc: Dominik Guder; nant-developers@lists.sourceforge.net
Subject: ***SPAM***BAR*** Re: [nant-dev] Updates to MSBuild  VSNet Tasks
Importance: Low

Hi,

Please see inline.

Thanks,
Ryan

On Jun 16, 2011, at 2:39 AM, Martin Aliger martin_ali...@gordic.cz
wrote:

 Hi Ryan, sln file handling is some kind of broken since VS2005. They 
 only work with 2002/2003. I would not spend to much time for now in 
 sln file handling in VS2005 and up.
 Eww, makes sense.  Well, not to let my work go to waste, I think I 
 know why
 it isn't working.  The plugins that contains the schema information 
 for
 VS2005+ solution files (NAnt.MSBuild.dll) doesn't seem to be getting 
 VS2005+ picked
 up during NAnt's plugin discovery phase.
 However, I have been having difficulty trying to locate where the 
 plugin
 discovery phase occurs in NAnt to make sure that they are getting picked
up.
 There is also the fact that the VS2005+ solution plugin classes are 
 marked as internal but I am not sure how much of an impact that is making
overall.
 
 Discovery mechanism was made by me and Gert some time ago. I could 
 look into it...
Thanks Martin. I thought your names looked familiar. :)
 
 SolutionFactory.cs is main branching thingy. Providers itself are 
 registred though Core's IPluginConsumer and ISolutionBuildProvider
interfaces.
I see that and it seems to be working ok with the classes within the
NAnt.VSNet assembly.  It just won't pickup the classes from the NAnt.MSBuild
assembly.  If u can point me to where in the code that the solution task
begins to search for plugins in external assemblies, I can research further
as well.
 
 M.
 


--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] SPAMBAR*** Re: Updates to MSBuild VSNet Tasks

2011-06-16 Thread Martin Aliger

Testing this bug, I found another one. Change OutputPath (MSBuildProject
class) implementation in recent patches to this one:

internal string OutputPath
{
get {
if (OutputDir != null) return OutputDir.FullName;
return _msproj.GetEvaluatedProperty(OutputPath);
}
}

Solutions without explicitlly set OutputPath failed. (all mine test cases
got OutputPath set).

Martin 


-Original Message-
From: Ryan Boggs [mailto:rmbo...@gmail.com] 
Sent: Thursday, June 16, 2011 3:37 PM
To: Martin Aliger
Cc: Dominik Guder; nant-developers@lists.sourceforge.net
Subject: ***SPAM***BAR*** Re: [nant-dev] Updates to MSBuild  VSNet Tasks
Importance: Low

Hi,

Please see inline.

Thanks,
Ryan

On Jun 16, 2011, at 2:39 AM, Martin Aliger martin_ali...@gordic.cz
wrote:

 Hi Ryan, sln file handling is some kind of broken since VS2005. They 
 only work with 2002/2003. I would not spend to much time for now in 
 sln file handling in VS2005 and up.
 Eww, makes sense.  Well, not to let my work go to waste, I think I 
 know why
 it isn't working.  The plugins that contains the schema information 
 for
 VS2005+ solution files (NAnt.MSBuild.dll) doesn't seem to be getting 
 VS2005+ picked
 up during NAnt's plugin discovery phase.
 However, I have been having difficulty trying to locate where the 
 plugin
 discovery phase occurs in NAnt to make sure that they are getting picked
up.
 There is also the fact that the VS2005+ solution plugin classes are 
 marked as internal but I am not sure how much of an impact that is making
overall.
 
 Discovery mechanism was made by me and Gert some time ago. I could 
 look into it...
Thanks Martin. I thought your names looked familiar. :)
 
 SolutionFactory.cs is main branching thingy. Providers itself are 
 registred though Core's IPluginConsumer and ISolutionBuildProvider
interfaces.
I see that and it seems to be working ok with the classes within the
NAnt.VSNet assembly.  It just won't pickup the classes from the NAnt.MSBuild
assembly.  If u can point me to where in the code that the solution task
begins to search for plugins in external assemblies, I can research further
as well.
 
 M.
 


--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

Re: [nant-dev] SPAMBAR*** Re: Updates to MSBuild VSNet Tasks

2011-06-16 Thread Ryan Boggs

Noted, I will update the patch after work today.  I need to make a couple of 
tweaks to the patch file anyway so this is good timing.

Thanks,
Ryan

On Jun 16, 2011, at 7:31 AM, Martin Aliger martin_ali...@gordic.cz wrote:

 Testing this bug, I found another one. Change OutputPath (MSBuildProject
 class) implementation in recent patches to this one:
 
internal string OutputPath
{
get {
if (OutputDir != null) return OutputDir.FullName;
return _msproj.GetEvaluatedProperty(OutputPath);
}
}
 
 Solutions without explicitlly set OutputPath failed. (all mine test cases
 got OutputPath set).
 
 Martin 
 
 
 -Original Message-
 From: Ryan Boggs [mailto:rmbo...@gmail.com] 
 Sent: Thursday, June 16, 2011 3:37 PM
 To: Martin Aliger
 Cc: Dominik Guder; nant-developers@lists.sourceforge.net
 Subject: ***SPAM***BAR*** Re: [nant-dev] Updates to MSBuild  VSNet Tasks
 Importance: Low
 
 Hi,
 
 Please see inline.
 
 Thanks,
 Ryan
 
 On Jun 16, 2011, at 2:39 AM, Martin Aliger martin_ali...@gordic.cz
 wrote:
 
 Hi Ryan, sln file handling is some kind of broken since VS2005. They 
 only work with 2002/2003. I would not spend to much time for now in 
 sln file handling in VS2005 and up.
 Eww, makes sense.  Well, not to let my work go to waste, I think I 
 know why
 it isn't working.  The plugins that contains the schema information 
 for
 VS2005+ solution files (NAnt.MSBuild.dll) doesn't seem to be getting 
 VS2005+ picked
 up during NAnt's plugin discovery phase.
 However, I have been having difficulty trying to locate where the 
 plugin
 discovery phase occurs in NAnt to make sure that they are getting picked
 up.
 There is also the fact that the VS2005+ solution plugin classes are 
 marked as internal but I am not sure how much of an impact that is making
 overall.
 
 Discovery mechanism was made by me and Gert some time ago. I could 
 look into it...
 Thanks Martin. I thought your names looked familiar. :)
 
 SolutionFactory.cs is main branching thingy. Providers itself are 
 registred though Core's IPluginConsumer and ISolutionBuildProvider
 interfaces.
 I see that and it seems to be working ok with the classes within the
 NAnt.VSNet assembly.  It just won't pickup the classes from the NAnt.MSBuild
 assembly.  If u can point me to where in the code that the solution task
 begins to search for plugins in external assemblies, I can research further
 as well.
 
 M.
 
 

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] [ nant-Bugs-3317505 ] nunit2 task does not run interal test fixtures

Bugs item #3317505, was opened at 2011-06-16 22:02
Message generated for change (Tracker Item Submitted) made by indr
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3317505group_id=31650

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: Tasks
Group: 0.91-alpha2
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Indr (indr)
Assigned to: Nobody/Anonymous (nobody)
Summary: nunit2 task does not run interal test fixtures

Initial Comment:
I switched from TeamCitys NUnit Launcher back to the nunit2 task and noticed 
after several hours of searching why lesser tests are run that the test 
fixtures must not be internal, they have to be public. Quite annoying because 
NUnit states on their home page: a test fixture class may be public, protected, 
private or internal.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3317505group_id=31650

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] [ nant-Bugs-3317505 ] nunit2 task does not run internal test fixtures

Bugs item #3317505, was opened at 2011-06-16 22:02
Message generated for change (Comment added) made by indr
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3317505group_id=31650

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: Tasks
Group: 0.91-alpha2
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Indr (indr)
Assigned to: Nobody/Anonymous (nobody)
Summary: nunit2 task does not run internal test fixtures

Initial Comment:
I switched from TeamCitys NUnit Launcher back to the nunit2 task and noticed 
after several hours of searching why lesser tests are run that the test 
fixtures must not be internal, they have to be public. Quite annoying because 
NUnit states on their home page: a test fixture class may be public, protected, 
private or internal.

--

Comment By: Indr (indr)
Date: 2011-06-16 22:03

Message:
Fixed typo in summary.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3317505group_id=31650

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] [ nant-Bugs-3317505 ] nunit2 task does not run internal test fixtures

Bugs item #3317505, was opened at 2011-06-16 22:02
Message generated for change (Comment added) made by dogu
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3317505group_id=31650

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: Tasks
Group: 0.91-alpha2
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: indr (indr)
Assigned to: Nobody/Anonymous (nobody)
Summary: nunit2 task does not run internal test fixtures

Initial Comment:
I switched from TeamCitys NUnit Launcher back to the nunit2 task and noticed 
after several hours of searching why lesser tests are run that the test 
fixtures must not be internal, they have to be public. Quite annoying because 
NUnit states on their home page: a test fixture class may be public, protected, 
private or internal.

--

Comment By: Dominik Guder (dogu)
Date: 2011-06-16 22:27

Message:
Nant's nunit2 task uses nunit 2.2.8 and class visibility was opened in
2.5.3 first.
It's on our tasklist to either update nunit or provide some kind of
dynamic loading. But for now my only idea is to use exec task and run
nunit-console. This is also true if you need to test .net 4.0 asseblies.
IMHO this is not possible with 2.2.8.

--

Comment By: indr (indr)
Date: 2011-06-16 22:03

Message:
Fixed typo in summary.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=402868aid=3317505group_id=31650

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers

[nant-dev] [ nant-Bugs-3317505 ] nunit2 task does not run internal test fixtures