[nant-dev] task bug in nested build

2003-11-03 Thread Eddie Tse
Hi All,

I have a large multi-solution project and the solution task does not build
properly if it is called within a nested  task because the full path
to the solution file is not used.  Patch attached.


Cheers,

Eddie


Index: src/NAnt.VSNet/Solution.cs
===
RCS file: /cvsroot/nant/nant/src/NAnt.VSNet/Solution.cs,v
retrieving revision 1.19
diff -u -r1.19 Solution.cs
--- src/NAnt.VSNet/Solution.cs  3 Nov 2003 09:46:04 -   1.19
+++ src/NAnt.VSNet/Solution.cs  3 Nov 2003 22:03:50 -
@@ -51,13 +51,13 @@
 
 string fileContents;
 
-using (StreamReader sr = new StreamReader(solutionFileName)) {
+using (StreamReader sr = new
StreamReader(_solutionTask.SolutionFile)) {
 fileContents = sr.ReadToEnd();
 }
 
 Regex re = new
Regex(@"Project\(\""(?\{.*?\})\"".*?\""(?.*?)\"".*?\""(?.*?)\"".*?\""(?.*?)\""");
 MatchCollection mc = re.Matches(fileContents);
-FileInfo fiSolution = new FileInfo(solutionFileName);
+FileInfo fiSolution = new FileInfo(_solutionTask.SolutionFile);
 
 foreach (Match m in mc) {
 string project = m.Groups["project"].Value;



---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers


[nant-dev] FxCop task

2003-11-03 Thread Nicklas Norling
Hi all.

Now that the solution task have pre/post events and my builds at work
are running smothly I was thinking I wanted to do a  tag for easy
usage of of the FxCop program.
I could see there where activity in this direction earlier on the list and
wanteded to know the current position. Is someone doing something
like that? If not, can I contribute it? Maybe NAntContributions is a better
place for it?

/Nicke


---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers


RE: [nant-dev] FYI

2003-11-03 Thread Alex Kipman
Let me be the first to say welcome.
>>> Thank you!  I'm glad to hear it!

Do you know if microsoft has any submitted or ourstanding patends on the
technologies included in the MSBuild stuff? We will want to make sure we
are
not accepting code from people who have access to or copies of the
MSBuild
source if there are license restrictions or patent issues.
>>> This is a tricky question but I'll do my best to answer it openly
and honestly :).  

1) Microsoft has submitted and has some outstanding patents on
technologies included in the MSBuild engine (core platform stuff).  

2) MSBuild is written 100% in managed code and will not be obfuscated by
us.  With this said, as of today there are no plans to release sources
for MSBuild Engine stuff.  Not even as shared source. We are currently
debating releasing sources for our tasks and loggers, but we haven't
discussed license issues yet.

Let me know if you have any other questions,
Alex Kipman ([EMAIL PROTECTED]
Program Manager
Visual Studio Core Team

-- This posting is provided "AS IS" with no warranties, and confers no
rights.


-Original Message-
From: Scott Hernandez [mailto:[EMAIL PROTECTED] 
Sent: Sunday, November 02, 2003 2:28 PM
To: Alex Kipman
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [nant-dev] FYI

RE: [nant-dev] FYILet me be the first to say welcome.

Our archives are open and monitoring the list is great. From what I
understand of MSBuild, and the difference from NAnt, it sounds like they
will always have slightly different goals and features. There is also
the
issue of open vs. shared source which will divide and seperate our users
at
a philosophical level.

Do you know if microsoft has any submitted or ourstanding patends on the
technologies included in the MSBuild stuff? We will want to make sure we
are
not accepting code from people who have access to or copies of the
MSBuild
source if there are license restrictions or patent issues.

Thank you for following up on the information about NAnt. If you, or if
any
other MSPress writers, need any information about NAnt we would be more
than
willing to help out. This list is a great way to get information about
the
state of NAnt, and its features.

- Original Message - 
From: Alex Kipman
To: [EMAIL PROTECTED] ; [EMAIL PROTECTED]
Sent: Sunday, November 02, 2003 12:11 PM
Subject: RE: [nant-dev] FYI


The book they handed out with the PDC alpha bits, "Introducing Longhorn
for
Developers", Brent Rector, Microsoft Press, has a fairly unflattering
description of NAnt in it.
>>> I have to agree with this and for that I must apologize.  I saw that
book and the chapter on MSBuild for the first time at PDC.  The content
of
that chapter is inaccurate in some parts, and in particular in the final
section of MSBuild vs NAnt.  Upon returning to Microsoft on Monday I
will be
having a serious conversation with the publisher at MSPress and Brent to
find out where they got their information from since no one in the
MSBuild
team was aware of the content of that chapter.
Again my apologies for the description of MSBuild vs NAnt since that is
the
polar opposite of how I think we should interact.  It is not about us vs
NAnt and we shouldn't let it become that way.  As I have told Gert
Driesen
before we love the NAnt community!!  You guys are a thriving .NET
community
and are enabling people to build .NET applications TODAY.  The more
successful NAnt becomes, the more successful .NET becomes. It's really a
win/win situation for everyone: Microsoft, the NAnt community, and our
customers.
I have just subscribed to both nant-dev and nant-user so that I can
answer
questions about MSBuild if/when you guys have them.  My objective is to
give
you facts rather than leave things up to speculation.  Please let me
know if
my lurking upsets you and I will respect that and unsubscribe from the
mailing lists.
Alex Kipman ([EMAIL PROTECTED])
Program Manager
Visual Studio Core Team



---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] Expansion of properties in target descriptions

2003-11-03 Thread Philip Nelson

--- Scott Hernandez <[EMAIL PROTECTED]> wrote:
> The projecthelp uses xsl templates to transform the source document (build
> file) without doing any includes  (or actually running any tasks; like
> ). This makes it pretty useless in many cases.
> 
> At this point I think we need to re-write the projecthelp stuff to load the
> document, run (the  tasks only?) global tasks, and then provide
> help about the build file.

I've already done this for my command line replacement gui, except for the
include target descriptions.  What I have observed is that the need for the
xslt is removed, as you are generally interested in a list of targets, and then
of those, the descriptions of just some of them.  Quite often on larger builds
with lots of targets, you may be interested in only those targets with
descriptions, or targets that don't start with an "_", or some other way of
filtering the list.  In a point and click gui, this is a much easier way to
explore the build file than trying to read a full formatted document.

The expansion of properties is a good question.  In my properties grid, I show
the unexpanded value, and I *think* this is what people would want.  If a
property is in the description, I think the opposite may be true. From the
execution point of view you may want to see all expanded values, but if the gui
is hosting an editor, you may want to leave the expansion off.  

I think the best answer is to expose some non instance code that takes a string
with property "templates", and the property collection and returns the string
with the templates expanded.


---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] asminfo task??

2003-11-03 Thread Gert Driesen
This task was moved into NAnt after the 0.8.3 release.

Its available in the 0.8.4 nightly builds
(http://nant.sourceforge.net/nightly/builds), see
http://nant.sourceforge.net/nightly/help/tasks/asminfo.html for more
information.

Gert

- Original Message - 
From: "Brandon Lonac" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, November 03, 2003 6:38 AM
Subject: [nant-dev] asminfo task??


> I was wondering why the AssemblyInfoTask.cs is in cvs but is not
> included in the 0.8.3 build or src files?  I have added it into my
> build, but I am curious, as there have been updates made to recently.
>
> Thanks.
> -Brandon
>
>
>
>
> ---
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?   SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/
> ___
> nant-developers mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/nant-developers
>
>



---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
___
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers