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-----and let me
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,
know if you are interested in trying out the custom NAnt task.our projects
Szymon Kobalczyk wrote:
Ok, here is the last problem I had to face today. Some of
arethat is located
strongly named and signed. All of them use the same key
inrelative path.
the top folder of the project tree that is referenced by
Somay look like:
the adequate line of AssemblyInfo.cs file in such projects
produce build file[assembly: AssemblyKeyFile("..\\..\\..\\..\\MyProduct.snk")]
But for some reasons SLiNgshoT creators have chosen to
fully qualifiedthat compiles all projects into a single folder and uses
with VS.NET.paths. As a result of this the working folder during compilation is
different then it would be when building the same project
Thuspossible i.e. to
the above line will produce a compile error.compilation
In my opinion the goal of SLiNgshoT should be to reproduce the
procedure that is implemented in VS.NET as closely as
that some ofcompile each project into its own bin folder. I understand
usgoing to be
may dislike the approach chosen by MS but if this stuff is
maintainsworking properly we have to do this their way.
Personally I would be very happy to help whoever currently
encourage others toSLiNgshoT to implement all necessary changes. I also
-------------------------------------------------------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
