RE: [nant-dev] 0.8.0.0 Release
Good to hear Tomas. I would agree with you but I expect that we will have more NAntContrib releases than NAnt releases. Once we get to a 1.0 NAnt release we may not have another NAnt release for a long time. At that point I would expect that most changes will come from new tasks, not changes to the core. I'm happy to word it anyway you want. From the users point (the devs using NAnt) of view all they should have to do is download NAnt/NAntContrib bundles. We will distribute them so there is no confusion or installation problem. > -Original Message- > From: Tomas Restrepo > Subject: Re: [nant-dev] 0.8.0.0 Release > > Hi Scott, > > > I've done a release build for testing purposes. Please try this out > > tonight if you have any time, > > http://nant.sourceforge.net/nant-src-0.8.zip > > Looks good to me. Seems to work just fine here I just used it to > recompile several of my projects with no problems at all (including the > one that has about 10 different buildfiles) > > > After this release goes out we will do a NAntContrib release too. Unless > > anyone has any objections NAntContrib releases will include, and depend > > on a specific, NAnt release. > > I'm all for that. The only question is: shouldn't it be the other way > around? That is, shouldn't a NAnt release include a corresponding > NAntContrib release? --- This sf.net email is sponsored by:ThinkGeek Two, two, TWO treats in one. http://thinkgeek.com/sf ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
Re: [nant-dev] 0.8.0.0 Release
Hi Scott, > I've done a release build for testing purposes. Please try this out > tonight if you have any time, > http://nant.sourceforge.net/nant-src-0.8.zip Looks good to me. Seems to work just fine here I just used it to recompile several of my projects with no problems at all (including the one that has about 10 different buildfiles) > After this release goes out we will do a NAntContrib release too. Unless > anyone has any objections NAntContrib releases will include, and depend > on a specific, NAnt release. I'm all for that. The only question is: shouldn't it be the other way around? That is, shouldn't a NAnt release include a corresponding NAntContrib release? -- Tomas Restrepo [EMAIL PROTECTED] --- This sf.net email is sponsored by:ThinkGeek Two, two, TWO treats in one. http://thinkgeek.com/sf ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] 0.8.0.0 Release
Hi all, I’ve done a release build for testing purposes. Please try this out tonight if you have any time, http://nant.sourceforge.net/nant-src-0.8.zip I’ve check in all these changes and will put down the tag once we are happy. Thanks you for all your efforts! After this release goes out we will do a NAntContrib release too. Unless anyone has any objections NAntContrib releases will include, and depend on a specific, NAnt release. Thank you, Scott PS. And again, if you have suggestions or comments please let us know. :)
[nant-dev] NAnt Installer
I've just put together an installer for NAnt. It wraps up the nant binaries and the extra tasks from NAntContrib into a single installer. Right now you can download it from http://www26.brinkster.com/ianm74/. Let me know what you think - any problems, improvements, ideas. It uses nullsofts NSIS installer http://www.nullsoft.com/free/nsis/ which is nice and easy to use and is distributed under an open source licence ( not sure which one ). Ideally I'd like to have a nightly build so that the latest binaries are alway available without having to compile from source. Ian --- This sf.net email is sponsored by:ThinkGeek Two, two, TWO treats in one. http://thinkgeek.com/sf ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
RE: [nant-dev] References and the Framework path
If the framework dir is in the path, you can specify that the 'include' should look there. In my environment with VS.Net the %vscomntools%\vsvars32.bat sets this correctly for me. >where system.dll \WINDOWS\Microsoft.NET\Framework\v1.0.3705\system.dll Does that work for you? Side Note: This is probably a user list question. Most of us read both, and if it isn't appropriate, we will just repost on dev and discuss... Later, Scott > -Original Message- > From: [EMAIL PROTECTED] [mailto:nant-developers- > [EMAIL PROTECTED]] On Behalf Of Kevin Miller > Sent: Wednesday, July 10, 2002 7:04 AM > To: '[EMAIL PROTECTED]' > Subject: [nant-dev] References and the Framework path > > I apologize if this is a know or just plain a user issue. > > In playing with the vbc task I attempted to add a reference to System.dll. > > optionstrict="true"> > > > > Turning verbose on I saw that the reference was never made unless I added > the full path to the framework dlls > > > value="C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705"/> > > optionstrict="true"> > > > > Have I missed something. Is there an easier way to tell the task where a > framework Dlls are? The main problem is that on different machines this > directory is in different paths (c:\win nt\..., or c:\win\...) In theory I > could possibly derive the path using environment variables but the sysinfo > task only exposes a few. > > > > > > --- > > test: > [sysinfo] Setting system information properties under sys.* > [sysinfo] nant.version = 0.7.9.0 > [sysinfo] sys.os.folder.temp = C:\DOCUME~1\Foo\LOCALS~1\Temp\ > [sysinfo] sys.clr.version = 1.0.3705.209 > [sysinfo] sys.os.platform = Win32NT > [sysinfo] sys.os = Microsoft Windows NT 5.1.2600.0 > [sysinfo] sys.os.version = 5.1.2600.0 > [sysinfo] sys.os.folder.system = C:\WINDOWS\System32 > > Kevin Miller --- This sf.net email is sponsored by:ThinkGeek Two, two, TWO treats in one. http://thinkgeek.com/sf ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
[nant-dev] References and the Framework path
I apologize if this is a know or just plain a user issue. In playing with the vbc task I attempted to add a reference to System.dll. Turning verbose on I saw that the reference was never made unless I added the full path to the framework dlls Have I missed something. Is there an easier way to tell the task where a framework Dlls are? The main problem is that on different machines this directory is in different paths (c:\win nt\..., or c:\win\...) In theory I could possibly derive the path using environment variables but the sysinfo task only exposes a few. --- test: [sysinfo] Setting system information properties under sys.* [sysinfo] nant.version = 0.7.9.0 [sysinfo] sys.os.folder.temp = C:\DOCUME~1\Foo\LOCALS~1\Temp\ [sysinfo] sys.clr.version = 1.0.3705.209 [sysinfo] sys.os.platform = Win32NT [sysinfo] sys.os = Microsoft Windows NT 5.1.2600.0 [sysinfo] sys.os.version = 5.1.2600.0 [sysinfo] sys.os.folder.system = C:\WINDOWS\System32 Kevin Miller --- This sf.net email is sponsored by:ThinkGeek Two, two, TWO treats in one. http://thinkgeek.com/sf ___ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
