I went ahead and made the changes to the VB6 task so that it parses the VBP to build its dependency list (both sources and references). It now pulls its output file name from the VBP file as well. I'll submit the change when I submit the others.
--- Ian MacLean <[EMAIL PROTECTED]> wrote: > Kevin Dente wrote: > > > > >7) I'm thinking about making a change to the vb6 > task > >such that if no references or sources are > specified, > >it always rebuilds the project. That way when > >converting a bunch of VB projects to NAnt, you > don't > >need to fill out all that info initially, and it'll > >still build. It's an appealing notion to a guy > looking > >at creating build files for a couple dozen VB > >projects. :) Opinions? > > > > > > > My feeling is that the the way the vb6 task works > now is a bit flawed. > it doesn't make any sense to have to specifiy things > twice. The > dependency checking could be done by parsing the > project file to get the > files and references. The information is all there > and fairly > accessible. That way you would never need to worry > about syncing the > two. Of course it makes it a bit different to other > nant tasks but vb6 > users are used to having everything hang off the > project file. > > Ian > > > > > > > > __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com ------------------------------------------------------- This sf.net email is sponsored by: Jabber Inc. Don't miss the IM event of the season | Special offer for OSDN members! JabberConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
