I think we should first work on refactoring the solution task (actually most classes in the VS.NET namespace), fixing known issues (first of all fixing, replacing or removing the current WebDavClient as its not working all too well), adding localization support, adding framework awareness, ....
Gert ----- Original Message ----- From: "Martin Aliger" <[EMAIL PROTECTED]> To: "!nant" <[EMAIL PROTECTED]> Sent: Tuesday, October 07, 2003 10:50 AM Subject: [nant-dev] solution task > Hi all, > > finally, I should have some spare time to nant project again. Do you still > think, code refactoring for solution task (described below) is good idea? I > want to ensure that if I do it, it will be accepted (alot of work) > > Martin > > ----- Original Message ----- > From: "Martin Aliger" <[EMAIL PROTECTED]> > To: "Jaroslaw Kowalski" <[EMAIL PROTECTED]>; "Matthew Mastracci" > <[EMAIL PROTECTED]> > Cc: "Gert Driesen" <[EMAIL PROTECTED]>; "!nant" > <[EMAIL PROTECTED]> > Sent: Monday, September 15, 2003 10:45 AM > Subject: Re: [nant-dev] solution task addin > > > > Hi, > > > > > OK. I withdraw my negative vote, now I can see the need for such tweaks. > > > > ;-) > > > > > But I think Martin's idea could be extended to all-singing-and-dancing > > > syntax like: > > > > [snip] > > > <solution configuration="Release" outputdir="${output.dir}" > > > includevsfolders="false"> > > > <projects> > > > <includes name="${build.dir}/**/*.csproj"/> > > > </projects> > > [snip] > > > <projectoverrides> > > > <project name="**/*.csproj"> > > > <parameter name="OutputPath" value="some_path" /> > > > </allprojects> > > > > > > <project name="B.csproj"> > > > <parameter name="CompilerCodePage" value="1250" /> > > > </project> > > [snip] > > > > > This way you'd be able to override absolutely all parameters from > *.??proj > > > files both for debug and release builds with quite readable syntax. > > > > > > What do you think? > > > > I like it. I was thinking about something similar as well but it seems too > > complicated. There are number of attributes which overrides something > (like > > outputdir) globally already. This also could be better in managing non-c# > > projects (like c++ with its 1000 options). And /nowarn will be superior on > > project level. > > > > If there are no complaints I'll do it when I spare some time to it. For > now > > I'm happy with mine patch :-) [no need to commit it though] > > > > Martin > > > > > > > > > > ------------------------------------------------------- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > _______________________________________________ > > nant-developers mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/nant-developers > > > > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > nant-developers mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/nant-developers > > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers