eason... we all make interesting implementation and design decisions
that look odd from the outside. I look at some of the things I've
done no more than a couple months and weeks ago and wonder what my
reason was :)
On Tue, 07 Dec 2004 03:35:36 +0100, Mateusz Åoskot <[EMAIL PROTECTED]> wr
> have a work-around, since they'll be stuck with the same problem. It's
> probably worth mentioning on whatever list is used for Slingshot
> maintenance about this bug.
>
> - Brad
>
> On Mon, 6 Dec 2004 09:46:06 -0500, Ryan Cromwell
> <[EMAIL PROTECTED]>
Has anyone contacted either the MSDN newsgroups or MS support to
report what very well could be a bug? Then everyone would be happy :)
On Mon, 6 Dec 2004 08:26:06 -0600 (GMT-06:00), Merrill Cornish
<[EMAIL PROTECTED]> wrote:
> >>> XML is a standard and IMHO is specified to be followed.
>
> True
s.
Original Message Follows
From: "Gary Feldman" <[EMAIL PROTECTED]>
To: "Ryan Cromwell" <[EMAIL PROTECTED]>
Subject: Re: [Nant-users] ... 0.85
Date: Wed, 3 Nov 2004 10:45:27 -0500
> I replaced 'asdf' with 'dosomething' in the email to av
Sent: Wednesday, November 03, 2004 10:08 AM
To: Ryan Cromwell; [EMAIL PROTECTED]
Subject: RE: [Nant-users] ... 0.85
You're asking NAnt to execute target asdf, which doesn't exist in any of
your build files.
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
I'm beginning the journey of upgrading our build scripts to 0.85 in
anticipation of a release coming in the near future. I've run into a road
block though... it appears is not working at all. Take a look
at the two build files below and let me know if I'm doing something odd -
these scripts work
I would suggest looking at CruiseControl.Net. It produces just what you are looking for in it's xml log files every build.
Original Message Follows
From: murty dronamraju <[EMAIL PROTECTED]>
Reply-To: murty dronamraju <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: [Nant-users] Rel
Dave - NUnit, or the CLR really, will resolve references just like any other assembly/application. Take a look at the following link. If you need to resolve references outside the basic working directory or GAC options, the codebase element of hte .config file is always an option.
http://msdn.mi
I really like this idea. I know we've toyed with the idea of a .build xslt which could be used to make a more 'natural' published build to our CM website and comments would make it that much better.
Original Message Follows
From: Merrill Cornish <[EMAIL PROTECTED]>
Reply-To: Merrill Cor
Holy crap! Where did you get VS.net for $29?!?! Should you be publishing that fact :)
Original Message Follows
From: Kevin Williams <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED]
Subject: Re: [Nant-users] What is Nantpad worth?
Date: Mon, 23 Aug 2004 20:28:49 -0600
I have to agree. I wr
http://radio.weblogs.com/0106046/VSConvert.xslWe have decided against this in most cases. We instead are tmpimp'ing our tlb's and sticking them in a "ThirdParty" area. Because the interop assemblies don't have to be registered, we don't then have to worry about registering anything on the build
Your first snippet wouldn't compile in C#. You can't define two variables within the same scope or parent/child scope. Maybe i'm missing something, but allowing that via some scope naming/definition mechanism would be thoroughly convoluted in my opinion. Explicitly defining the scope would be c
Try bootstrapping your build scripts. That is call your current build from a new bootstrap.build which then executs a task, followed by a task. I personally would suggest looking into CruiseControl.Net (http://ccnet.thoughtworks.com).
Original Message Follows
From: Lamont Adams <[EMAI
I think this is an excellent idea, especially with the introduction of expressions. Without expressions, i don't see nearly as much benefit.
I'm a little confused as to your use of scripting languages as a argument against type safety. Scripting language types are resolved at runtime. Depending
http://www.theserverside.net/news/thread.tss?thread_id=27132
Grab an eval - the demo's are impressive.
---
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital se
I realize this has been put on the floor before, but is there a concensus as to some target dates for completing a next release? There seems to be a significant amount left in the 0.8.x task list, but I would propose that between bug fixes, task updates, and expressions a release is within sight.
I'm not positive as i don't use the nightly builds, but seems that it should be net-1.1, net-1.0, mono-1.0, etc
Original Message Follows
From: "Bonnett, Evan A" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: [Nant-users] Valid Framework Identifiers
Date: Wed, 23 Jun 2004 09:36:49 -
Regarding the Windows Installer stuff, take a look at the following blog. We are using this technique to promote along our test/dev chain and it has been VERY successful.
http://weblogs.asp.net/lorenh/archive/2004/05/09/128899.aspx?Pending=true
The follow-up blog notes a somewhat annoying issue w
try one of the following -- wmi, scheduled tasks, or Sysinternals psexec.
Original Message Follows
From: "Jonni Faiga" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: [Nant-users] Initiating a remote nant build
Date: Mon, 17 May 2004 13:01:18 +0200
Hi,
Any ideas of what is the
Man - i can't wait until 0.85 is release :) I'd love to start using functions, but we just can't concider using a nightly for a production buildsserver.
Original Message Follows
From: Ian MacLean <[EMAIL PROTECTED]>
To: Ian MacLean <[EMAIL PROTECTED]>
CC: "Price, Henry" <[EMAIL PROTECT
i would suggest using version task's revisiontype=increment for the daily build and revisiontype=automatic when you are going to test. Major and minor or done manually to the .version file that is maintained by the version task. I think that would follow your scheme
Original Message Follows-
Stephen Boom mentioned that I missed the
NDoc.xslt include. This was just a result of my very half-a** attempt at
cleaning the VS.Net Project to NAnt build.xslt. It just includes your
NDoc task content.
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ryan
>
>
>
>>-Original Message-
>>From: [EMAIL PROTECTED]
>>[mailto:[EMAIL PROTECTED] On Behalf Of Ian
>>MacLean Sent: Tuesday, April 06, 2004 1:21 AM
>>To: Ian MacLean
>>Cc: Ryan Cromwell; [EMAIL PROTECTED]
>>Subject: Re: [Nant-use
I completely agree - msi2xml and nant msi tasks are all more than sufficient, but i'm excited to see this unprecedented move towards community collaboration.
Original Message Follows
From: Ian MacLean <[EMAIL PROTECTED]>
To: Ian MacLean <[EMAIL PROTECTED]>
CC: Ryan
How exciting would an NAnt Wix task or refactoring of the NAntContrib - Msi/Msm tasks be! Maybe I'll work on a transform for vdproj -> Wix xml.
http://blogs.msdn.com/robmen/archive/2004/04/05/107709.aspx
http://sourceforge.net/projects/wix Tax headache? MSN Money provides relief with tax tips, t
The NAntContrib version task will increment the version number and return the new one in a property. You don't have to provide it the current version, it persists that to disk. You then use the asminfo task to create a new AssemblyInfo file. asminfo is a task in NAnt core.
A couple months ago I
Why was this removed? I would presume that to be a big breaking change.
Original Message Follows
From: "Gert Driesen" <[EMAIL PROTECTED]>
To: "Zigomanis, Nick" <[EMAIL PROTECTED]>,<[EMAIL PROTECTED]>
Subject: Re: [Nant-users] Question about style task in latest nightly build
Date: Thu,
This post is definitly in the wrong place, but I can't find any NDoc user group that has any substance to it. Point one out and I'll ask the question there.
Anyways, I'm curious to here about people's experiences publishing there HTML help documentation. We have been generating MSDN and CHM hel
Wonderful. I recompiled the MSDN Documenter as well with a fix using a temporary path in the temp folder rather than the the application path - all's been well since.
For those interested - the contention problem, at least this one, is on line 166 of MSDNDocument.cs
Original Message Follows--
I have created a script task which populates a property solution.projects with a | delimited string. This is all fine and dandy, but web projects return web urls. I could use DirectoryServices to look up the physical path of the url while still in the script, but i really want to use the NAntCont
30 matches
Mail list logo
