Title: RE: NAnt-users digest, Vol 1 #1714 - 7 msgs
Hi, Gary
>What is the name of the assembly that contains the tests, not the one
>that contains the code being tested? It's the one containing the tests
>that needs the config file, not the one that you're testing. If the
>tests are in t
Title: Differentiating .NET 2003 / 2005 solution
The only way I know of is to open the
solution file and look at the first couple of lines
Visual Studio .NET 2003 has the following:
Microsoft Visual Studio
Solution File, Format Version 8.00
Visual Studio .NET 2005 has the follow
Title: Executing foreach on EITHER a file list, or elements in a list of files.
Ok, here is the problem I try to solve.
I am building a standardized build script for all of our projects. It works on multiple "steps" (targets), and every step can execute multiple elements (build: all solutio
Title: Differentiating .NET 2003 / 2005 solution
Anyone knows an easy and fast way to differentiate betwene a .NET 2003 and a .NET 2005 solution file?
I want to run a switch over our build task to move into a separate build setup based on whether a .sln is for VS.NET 2003 or 2005. Naturally
> how can custom functions from one script task be
> used by custom functions from another script task?
Have a look in NAnt/examples/UserTask.
I use something similar and it works well, the only
difference to the example is I don't compile every time,
rather only if the DLL is missing.
peace
si
While trying to build my project, I get this error
error BC30002: Type 'XYZ.Objects.Common.Cache' is not defined
THe line number this error points to is basically declaring an object of
this class. [This is a class library that I wrote.]
I opened my proj file in notepad (there is a lot useful
Helmut,
Below is some code that demonstrates how to get at project settings from
within a script-task. I wanted the capability to read all of my properties
in from a file (comma separated values). The problem I had was that
properties values aren't evaluated recursively. That is, if the value in
Hi,
has anyone already created a XSLT for a history-log created by the vss
tasks from the conrtibution-package? The XML is almost unreadable, and I
figured if someone already did something, why reinvent the wheel :)
---
This SF.net email is sp
Bob Archer schrieb:
> Ok,
>
>
>
> FYI: I found the problem. IT pushed an upgrade the McAfee Enterprise
> which was blocking port 25. I added nant.exe to the exceptions list and
> viola, back in business.
>
I kinda have the same problem. But in my case I can't add nant to the
white-list :( But
Hello,
sometimes it may be necessary to use the current project
in custom functions defined via script-task, e.g. for the
method GetPropertyValue from class Nant.Core.ExpressionEvaluator.
How can the current project be retrieved?
Using ScriptMain is no solution for nested builds.
Or how can proper
Hello,
how can custom functions from one script task be
used by custom functions from another script task?
Best regards
Helmut Dipper
--
Helmut Dipper | AED-SICAD Aktiengesellschaft
phone: +49 89 45026 320 | Postfach 830754
fax: +49 89 45026 316 | D-817
11 matches
Mail list logo