I was thinking about Reflection too. Have to try it. But - maybe, simlest solution: keep separate assembly (NAnt.MSBuild) and use some reflection stuff from <solution> task to this assembly. To keep current <solution> working even on 1.1/1.0 profile.
For now, I just focus to get it working. It'll certainly need some time to tune it. btw: Do you review mine changes to NAnt.VSNet? Are they ok? I'd like to keep msbuild stuff separate from core for while. Maybe in NAntContrib or elsewhere (becouse of 2.0 dependency). And those patches was needed to enable it. Martin Aliger > Martin, > > I'm just thinking out loud here, but would it be an option to use > Reflection instead of directly using the MSBuild API ? > > I know there's a performance penalty, but it would allow us to include > it in NAnt without needing a separate assembly (and separate task). > > Gert ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ nant-developers mailing list nant-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-developers
