Hello nant-developers,
Is anyone currently working on adding support for C++ projects to
the solution task? I'd like to start working on that now, if noone
else is already doing that.
--
Best regards,
Dmitry mailto:[EMAIL PROTECTED]
I don't believe anyone is currently working on it. It would be good if
the implementation deferred to the existing tasks in NAnt.VisualCpp for
the actual compilation stage. I've just moved Midltask and rcTask across
from NAntContrib which should help. I'm going to add fileset support for
them
Dmitry Jemerov wrote:
Hello nant-developers,
The attached patch updates NAntAddin to build and work with the
latest NAnt.
Not quite the latest NAnt. I hit a couple of compile errors where method
signatures have changed. I also had to make several changes to the
.build file where it was
Hi,
I'm using the following statement in my buildscript:
license input=license.licx licensetarget=start.exe /
This is similar to the help file. But: I _always_ gt an
exception about an invalid path. Before I had an fileset
included with the assemblies to be licensed, but this is
just the same
apologies. I didn't see you other patch to project.cs. I've committed it
as well. Thanks
Ian
Not quite the latest NAnt. I hit a couple of compile errors where
method signatures have changed. I also had to make several changes to
the .build file where it was breaking due to some changes in
Dmitry Jemerov wrote:
I have found the add-in to be good enough for running NAnt builds
from Visual Studio, but hardly usable for editing or creating new
.build files, or even for getting an overview of how a build file
works. The add-in uses the standard Properties window for editing
target and
Please consider refactoring the existing project class into separate classes
ie: BaseProject, CSharpProject, VBNetProject and CPlusPlusProject
this will help keep the subtle details of each project file separate. This
was on my list of contributions but I haven't had time to start on it yet.
Don't forget J# project :)
Ian
Please consider refactoring the existing project class into separate classes
ie: BaseProject, CSharpProject, VBNetProject and CPlusPlusProject
this will help keep the subtle details of each project file separate. This
was on my list of contributions but I haven't
Hi,
It seems I found two bugs. One is in the licese task itself.
It can happen (actually it does on one of my systems),
thatasmLoaded.Location is either an empty string or null. If
so, Path.GetFullPath(...) throws an exception. The attached
diff files addesses this issue.
The second thing seems
Yet another bug is that the License task loads assemblies (as far as I
can remember) into the main AppDomain. It needs to have code to load
these assemblies in a separate AppDomain, like the NUnit tasks have.
Matt.
On Sun, 2003-09-14 at 11:46, Sascha Andres wrote:
Hi,
It seems I found two
Hi,
* Matthew Mastracci wrote on 14.09.2003 (12:45):
Yet another bug is that the License task loads assemblies (as far as I
can remember) into the main AppDomain. It needs to have code to load
these assemblies in a separate AppDomain, like the NUnit tasks have.
You're right. It does that way.
11 matches
Mail list logo
