The CVS versions of NAnt and the nightly snapshots seem to be out-of-sync, or have some sort of branching happening. I'm not really sure which one I should be using. So far, I'm just working against my local copy of 0.7.9, but I'll need to port it to the latest CVS version whenever possible.

I've got a <resx> and <license> task ready for inclusion in NAnt once I have a chance. I've compiled it into VSProjTasks.dll and zipped up the source alongside.

Note that this is still pretty rough code, but it's working on my testcases so far. Here's some samples for usage:

<resx input="test.resx" output="foo.resources"/>
<license input="test.licx" target="foo.exe" output="test.licenses"/>

Note that <license> needs a licensed component. I'm using a commercial component here, but any one will do.

Szymon Kobalczyk wrote:

Hi,

I can start working on SLingshoT so it will produce the global build file
that would call the vcproj task on each of the projects.
Matthew please send me the latest version of the vcproj task. Also some
sugestions or template for this global project would be handy. Have you been
thinking about supporting additional reference paths (see my earlier
postings)?

Do we drop for now the functionality to produce the NMake makefiles?
In any case I would like to keep SLingshoT as a command line util along with
a NAnt task.

Szymon.

-----Original Message-----
From: Matthew Mastracci
To: Ian MacLean
Cc: Szymon Kobalczyk; '[EMAIL PROTECTED]'; 'Bernard
Vander Beken'
Sent: 2002-11-15 20:48
Subject: Re: [nant-dev] Error on relative path in AssemblyKeyFile

The first thing I'd like to do is add license file generation as a core task to NAnt and set up Slingshot to use the new tasks. I can do this alongside any work to separate the .build files into per-project files. Who would I ask for CVS commit access to the NAnt core? I won't commit

anything without posting a patch for review on the list first.

Ian MacLean wrote:


Szymon,
I'm in agreement with your suggestion. Seperate build files per project seems like the right approach to me. So +1 from me. The slingshot code was originally contributed by Jason Diamond who may still be lurking on this list. However that code has been stagnating a


bit lately and is need of some work to be consistent with some of the newer nant features. I can look at doing this as you guys add new features to SlingShot. Let me know if you or Mathew require commit access to NAntContrib.

Ian




I hope you understand that what we are talking about here is to

change

SLiNgshot the way that instead of generating one huge build file for whole
solution (I have one that has over 200 KB) it will create separate build or
make files for each project and one top level file that will call all
projects in appropriate order. Architecturally that is rather big change and
I would like to have it approved by community before starting to code. Thus
I encourage others to join this discussion.

Szymon Kobalczyk



-----Original Message-----
From: Bernard Vander Beken [mailto:Bernard.VanderBeken@;tectrade.net]
Sent: Friday, November 15, 2002 10:28 AM
To: Szymon Kobalczyk; [EMAIL PROTECTED]
Cc: Matthew Mastracci
Subject: RE: [nant-dev] Error on relative path in AssemblyKeyFile

Hello,

A suggestion:
- Modify SLiNgshot to support project files, too.
- Improve the SLiNgshot task.

This would avoid duplicating the conversion logic in another task.

Best regards,

Bernard



-----Original Message-----
From: Szymon Kobalczyk [mailto:szymon.kobalczyk@;pl.apriso.com]
Sent: Friday, November 15, 2002 10:22 AM
To: '[EMAIL PROTECTED]'
Cc: 'Matthew Mastracci'
Subject: RE: [nant-dev] Error on relative path in AssemblyKeyFile


Hi Matthew,

I've already downloaded your task and I admire the great work
you did. As
you could see from my last postings I have already discovered
that SLiNgshot
is not the best tool to do the conversion. The most annoying
thing is that
it compiles all projects into one single folder. I believe
that project
based builds that closely reflect what VS.NET does are more
appropriate.

Nevertheless SLiNgshoT still has some nice features. First of all

it

generates the build instructions for the whole solution so
you don't have to
manually call builds for each project. This is important for
me because most
of my solutions have more than 30 projects and I don't want
to waste time
coding the build instructions by hand. The second thing is
that it can be
used apart from NAnt because it can also generate NMake files.

I'm impressed by the effort you put to create the task that will

work

directly on .csproj filed, properly handle resource files and other
features. In my opinion now we should join efforts to either
integrate this
routines with existing SLiNgshoT or create new top level task
that will
generate build files that will automatically call the
<vsproj> task for each
project in the solution. In either case I will be happy to help.

Szymon Kobalczyk




-----Original Message-----
From: Matthew Mastracci [mailto:matt@;aclaro.com]
Sent: Friday, November 15, 2002 3:13 AM
To: Szymon Kobalczyk
Cc: '[EMAIL PROTECTED]'
Subject: Re: [nant-dev] Error on relative path in AssemblyKeyFile

I have a task for NAnt that will compile projects exactly as

VS.NET

does. Please see my earlier messages for more information,

and let me


know if you are interested in trying out the custom NAnt task.

Szymon Kobalczyk wrote:



Ok, here is the last problem I had to face today. Some of

our projects


are


strongly named and signed. All of them use the same key

that is located


in


the top folder of the project tree that is referenced by

relative path.


So


the adequate line of AssemblyInfo.cs file in such projects

may look like:


[assembly: AssemblyKeyFile("..\\..\\..\\..\\MyProduct.snk")]

But for some reasons SLiNgshoT creators have chosen to

produce build file


that compiles all projects into a single folder and uses

fully qualified


paths. As a result of this the working folder during compilation

is

different then it would be when building the same project

with VS.NET.


Thus


the above line will produce a compile error.

In my opinion the goal of SLiNgshoT should be to reproduce the

compilation


procedure that is implemented in VS.NET as closely as

possible i.e. to


compile each project into its own bin folder. I understand

that some of


us


may dislike the approach chosen by MS but if this stuff is

going to be


working properly we have to do this their way.

Personally I would be very happy to help whoever currently

maintains


SLiNgshoT to implement all necessary changes. I also

encourage others to


discuss how to properly handle this conversion.

Best Regards,
Szymon Kobalczyk.


-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of

securing

your web site with SSL, click here to get a FREE TRIAL of a

Thawte

Server Certificate: http://www.gothawte.com/rd524.html
_______________________________________________
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

.




-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing
your web site with SSL, click here to get a FREE TRIAL of a Thawte
Server Certificate: http://www.gothawte.com/rd524.html
_______________________________________________
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers


-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html
_______________________________________________
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers






-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html
_______________________________________________
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

.



-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html
_______________________________________________
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers

.


Attachment: VSProjTasks.zip
Description: Zip compressed data

Reply via email to