Very nice installer! I have some ideas for 1.0 release and I wonder if they can all be implemented with this tool:
1. Binaries should go to "Program Files\NAnt\bin" and should include *.exe, *.dll but no *.xml (at least not by default) 2. I wonder if we could get rid of the *.pdb since they occupy about 50% of all space used. 3. We should include the documentation. I think that "doc/help/**/*" is enough. The docs should be either plain *.html or *.chm compressed files (which I personally prefer). PDF would be nice as an option, too because it's easy to print as a reference. 4. We should also include the SDK docs as an option. 5. We should register ourselves in the registry in some versioning-aware manner so that various tools (like NAntMenu or editor integrations) can locate NAnt executables or config file. 6. I think that the final executable of the installer should be below 1 MB in size. Having a huge build tool scares many people. If needed, we could make some parts not usually needed (like the SDK docs, PDB symbols, source code) available as separate downloads. 7. Should we register Nant SDK components in AssemblyFolders so that they are easily referenceable in VS.NET ? Unfortunately this would clash with log4net.dll, NUnit.Framework.dll and other components that also register themselves this way. 8. We should somehow detect alternative CLIs (Mono, Rotor, .NETCF, DotGNU) and modify NAnt.config file accordingly to make NAnt find them. Should they be installed in some non-standard place, we'd allow the user to browse for the appropriate paths. 9. Should we include some GUI (shell integration, VS.NET integration) in the 1.0 release? Offtopic: 1. We should do something about the linux installation really soon. I've heard voices that "NAnt is very complicated to install on Linux because you cannot do ./configure --prefix=... && make && make install". Maybe a simple configure script that would setup the mono paths in the config file would do? Awaiting your comments. Jarek ----- Original Message ----- From: "Nicklas Norling" <[EMAIL PROTECTED]> To: "Nant-Developers (E-mail)" <[EMAIL PROTECTED]> Sent: Tuesday, March 23, 2004 4:10 PM Subject: [nant-dev] Windows setup contribution > Hi all. > > I always package up NAnt in a setup for my developers so I thought > I could as well contribute the iss script file I use in case there are more > out there that would like it. > > It uses InnoSetup 4.2.0 http://www.jrsoftware.org/isdl.php which is a totaly > free and awsome setup tool. > > The iss file is designed to be in the root or the release togther with > the NAnt.sln file. From there is will zipp up .\bin\*. > > During install it installs this in a directory, optionally adds a program > group and leaves standard uninstall entry in add/remove programs. > > It does not currently alter the PATH variable, but I hope to find some free > prog that will do that. > > The installer file will be called NAntInstaller.exe and will be placed at > the root of the release. > > I added licence file reference and copyrights as best I could. Hope I got it > right. > > /Nicke > > ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
