Re: [nant-dev] last suggestion - Solution task again

[Matthew M. <ma...@ac...>]

The fileset would work fine.  It can handle directories as well as
individual files.  You'll just need to use the correct method when you
get the items from the FileSet.  As well, it can handle the nifty
wildcarding that gives NAnt its real power.  :)

On Sat, 2003-08-30 at 05:52, Martin Aliger wrote:
> > Good find.  I like your assembly-folders idea.  Unfortunately, I'm quite
> > busy at work and don't have any time for <solution> task development.
> > It should be pretty straight-forward to implement if someone has an hour
> > or so to space.
> 
> I could code it - no problem. Does others see any other ideas?
> 
> Also I'm not quite sure about naming. is "assembly-folders" proper name for
> that tag? And how to internally implement it? As list of paths? Fileset is
> not appropriate here. Maybe I could handle it simmilary as <arg> in <csc>?
> (only list tag I'm aware of)
> 
> Martin
> 
> 
> > Martin Aliger wrote:
> >
> > >I did some exploration in this field and found this:
> > >
> > >Visual Studio use HintPath to find reference assemblies. If not found it
> > >uses all paths listed under registry key
> > >HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\7.1\AssemblyFolders
> > >
> > >Maybe we should implement similar mechanism? Use HintPath first and then
> > >some path list which could defaults to this regisry read. And be
> overrided
> > >(extended?) by e.g.
> > >     <solution _verbose="true" configuration="Release"
> > >output="${build.dir}">
> > >        <projects>
> > >           <includes name="**/*.csproj"/>
> > >        </projects>
> > >        <assembly-folders>
> > >            <includes name="c:\temp\build\dll"/>
> > >        </assembly-folders>
> > >     </solution>
> > >
> > >Martin
-- 
Matthew Mastracci <ma...@ac...>