bject: RE: [nant-dev] cl task gone???
Well, the XmlDocument object does give you a list of namespaces
associated with the current document so you should be able to do what
you are asking. According to the docs for XmlNode (which XmlDOcument
derives from)
XmlNode.NamespaceURI Property
Get
-dev] cl task gone???
Wow, I guess I should have read more about Xml namespaces. Good thing
there is lots of smart people on this list.
This is really clean Joe/Ian but is there anyway to import a task dll
into the default namespace using this method? Ie, I want to "import" a
numb
Shaw, Gerry wrote:
>Wow, I guess I should have read more about Xml namespaces. Good thing there
>is lots of smart people on this list.
>
>This is really clean Joe/Ian but is there anyway to import a task dll into
>the default namespace using this method? Ie, I want to "import" a number of
>task
Yes, you are correct on the dummy node issue. Good catch and my bad. :-)
Joe
-Original Message-
From: Ian MacLean [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 21, 2002 11:05 AM
To: Joe Jones
Cc: Shaw, Gerry; Jayme Edwards; [EMAIL PROTECTED]
Subject: Re: [nant-dev] cl task gone
Wow, I guess I should have read more about Xml namespaces. Good thing there
is lots of smart people on this list.
This is really clean Joe/Ian but is there anyway to import a task dll into
the default namespace using this method? Ie, I want to "import" a number of
task assemblies into the defau
Joe Jones wrote:
>Anyway to incorporate XML namespaces into this instead of prefix?
>Something like this:
>
>
>
>
> ...
>
>
>Using this would allow us to drop the import tag (possibly) or to use it
>as the dummy tag for laoding the namespace, E.G. xmlns:dotnet="NAnt.DotNetTasks.dll"
:[EMAIL PROTECTED]]
Sent: Tuesday, August 20, 2002 4:27 PM
To: 'Jayme Edwards'; [EMAIL PROTECTED]
Subject: RE: [nant-dev] cl task gone???
> I'm curious as to why these arent considered "DotNetTasks"
Basically I'm trying to cut up the tasks so that people who d
> Another solution is by using an task that replaces the
> task. It would be used like this:
>
>
>
> You would then use the tasks from this assembly as follows:
>
>
> Omitting the prefix attribute just brings the tasks into the default
> namespace. The tasks in NAnt.Core would always be in t
> I'm curious as to why these arent considered "DotNetTasks"
Basically I'm trying to cut up the tasks so that people who don't want them
(ie, me :) can use those task names for their own tasks. I'm using a ,
and tasks that work with four different platforms using a
number of predefined proper
ED]>;
<[EMAIL PROTECTED]>
Sent: Monday, August 19, 2002 7:35 PM
Subject: Re: [nant-dev] cl task gone???
> Gerry Shaw wrote:
>
> >This was intentional and an oversight :) I didn't want those tasks in
> >the core tasks but I didn't want to lose them either.
IL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Monday, August 19, 2002 7:26 PM
Subject: RE: [nant-dev] cl task gone???
> This was intentional and an oversight :) I didn't want those tasks in
> the core tasks but I didn't want to lose them either. There should be a
> NAnt.Vis
ugust 19, 2002 4:38 PM
>To: [EMAIL PROTECTED]
>Subject: [nant-dev] cl task gone???
>
>
>Hello,
>
>I'm currently updating the build script for the VS.NET Addin for NAnt in
>the NAntContrib project. First off, great job on the refactoring guys -
>it looks really nice. Th
the NAntContrib project.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Jayme
Edwards
Sent: August 19, 2002 4:38 PM
To: [EMAIL PROTECTED]
Subject: [nant-dev] cl task gone???
Hello,
I'm currently updating the build script for the VS.NET A
Hello,
I'm currently updating the build script for the VS.NET Addin for NAnt in the
NAntContrib project. First off, great job on the refactoring guys - it looks
really nice. There is one small issue I've ran into however, the cl (class
linker/C++ compiler) task is no longer available. Since I nee
14 matches
Mail list logo
