I actually would like to consider nant as a real third-party product, it's not because the soruce is available that you should adapt your own version of it, so you also should not be building your own version, even if the source code remains unchanged.
I want to be able to tell users that download our software to download version X of nant and put the nant assemblies in directory Y, and now you build our software using the default target in the buildfile. That gives users the assurance that I did not change anything in the nant source code, and it makes sure that I don't have to store the binaries for nant in CVS. NAnt currently uses the runtime in which it's executing to detetermine the path of the compiler and the sdk tools, trhat's why it's important to have : - versions built for the runtime against which you want the buildfile to run or - add the supportedRuntime elements to the nant configuration file, see my other message title "Adding .NET Framework 1.1 as supported runtime". but the second option does not allow you to choose the runtime version, it will use the .NET Framework 1.1 when it is available and use the 1.0 framework when the 1.1 framework is not available. We should also really start thinking about how to allow users to build assemblis for multiple runtimes in one buildfile (and in once run of that build file). For now, I run NAnt on the .NET Framework 1.1 (by adding the supportRuntime elements in the config file), this makes sure I can build he .NET Framework 1.1 runtime version of our assemblies and I set the "doNotFind.dotnet.exes" property to true before we build the .NET Framework 1.0 version, and set it to false after that runtime version is built. But I really think we should consider adding a new base class for tasks that need to be aware of the runtime version they're targeted for. This base task could have an attribute for specifying the runtime name and version (eg. NET-1.0, NET-1.1, NETCF-1.0, MONO-1.0) that the task is targeted for and it would have methods for retrieving the Framework runtime directory for that runtime and for retrieving the SDK tools directory for that runtime version. When this is in place, it's not really that important with which version of the .NET Framework NAnt was built. But it still think we need to consider having both. Gert ----- Original Message ----- From: "Tomas Restrepo" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, February 24, 2003 4:23 AM Subject: Re: [nant-dev] .NET Framework 1.1 version of nant > Actually, what I'd like to see is for us to have a way to use NAnt to build > applications for whatever version of the framework you want without having > to explicitly recompile NAnt itself for said framework. [1] > > I think that, In the long run, this is an strategy that could me much more > useful... > > [1] Actually, this is one of the reasons I prefer nant invoking the .NET > tools themselves, instead of using the internal .NET framework classes to do > the work. > > Then again, this is just my opinion :) > -- > Tomas Restrepo > [EMAIL PROTECTED] > > ----- Original Message ----- > From: "Ian MacLean" <[EMAIL PROTECTED]> > To: "Gert Driesen" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Sunday, February 23, 2003 10:01 PM > Subject: Re: [nant-dev] .NET Framework 1.1 version of nant > > > > Gert, > > > > Do you mean "built on 1.1" ? If so then I would say no - at least untill > > 1.1 becomes the platform most users are running on. If its really needed > > you ca always grab the dource and build it yourself on 1.1 > > > > Ian > > > Hi, > > > > > > Are there plans to release a separate .NET Framework 1.1 version of NAnt > > > (possibly in the same distribution) ? > > > > > > Does anyone knwo if there be .NET Framework 1.1 versions off NDoc, > > > SharpZipLib and NUnit ? > > > > > > Thansk, > > > > > > Gert > > > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. > > The most comprehensive and flexible code editor you can use. > > Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. > > www.slickedit.com/sourceforge > > _______________________________________________ > > Nant-developers mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/nant-developers > > > > ------------------------------------------------------- > This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. > The most comprehensive and flexible code editor you can use. > Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. > www.slickedit.com/sourceforge > _______________________________________________ > Nant-developers mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/nant-developers > ------------------------------------------------------- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
