Scott Hernandez wrote: >So I did this (sent the email), then realized that if actually use the >existing file (meaning you add an xmlns=" to the project element) it >will cause problems with xpath queries. > >Before you actually build (use the build file) you need to remove the >default namespace def from the build file. If you leave it, all xpath >queries will fail. > I think I see the problem. In the build file we map the dafault namespace to the nant namespace but when we come to execute an xpath the default namspace isn't the nant one so the xpath queries will return nothing. Does this mean we will need to specify the namespace in our xpath queries - using a custom context ? Even if we use prefixes our xpath queries will still need to be aware of the namespace mapping.
Ian > > >>the more normalized format I started with was giving no help in the >>vs.net xml editor. So I had to start over. This version is much >>larger, and deeper, with little to no references to complex types. In >>short, it probably about 80% repeated text. >> > >Great work Scott. I notice Project is expected as uppercase and "arg" >tags aren't handled in the csc task. target should have a depends >attribute not a default attr. >This is really cool. the intellisense makes to so much quicker - no more > >looking up the nant task reference every time I code a build file. > >Ian > > > > > >_______________________________________________ >Nant-developers mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/nant-developers > > _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
