|
I want to bring this up as a topic of its own. We have discussed what the behavior of loading assemblies and custom tasks before, but I wanted to make sure there was consensus, and a clear understanding of how things work.
Let me start by stating how it works now (as far as I can tell). 1.) The Project ctor loads the executing Assembly and any Assembly named *Tasks.dll. The Assemblies are scans and classes that are derived from Task (not abstract) are added (from the BaseDirectory of the executing Domain). 2.) The TaskDefTask can also add an Assembly during a run.
Note: With my latest changes to TaskFactory, The Project.BaseDirectory is also scanned for *Tasks.dll(s).
Now, I think we have discussed that the TaskDefTask should go away. I also think there was some discussion about the directory names, and locations we should be scanning. It seems to me that some of this stuff should go in a NAnt configuration file.
Any comments? |
- Re: [nant-dev] Task Assembly Loading Scott Hernandez
- Re: [nant-dev] Task Assembly Loading Ian MacLean
- RE: [nant-dev] Task Assembly Loading Scott Hernandez
- Re: [nant-dev] Task Assembly Loading Ian MacLean
- RE: [nant-dev] Task Assembly Loading Scott Hernandez
- Re: [nant-dev] Task Assembly Loading Ian MacLean
- RE: [nant-dev] Task Assembly Loa... Scott Hernandez
- Re: [nant-dev] Task Assembly... Ian MacLean
- RE: [nant-dev] Task Assembly Loading Smith, Eric V.
