Just so anyone else might need to do the same thing. Here's the link
that I thought you all might be interested.
http://dotnetjunkies.com/WebLog/appeng/archive/2005/03/15/60381.aspx
Granted, the blog was originated since beta1, but I found it's still
work (at least for me).
Daniel
-Origina
Thanks Gert,
Yes, you are correct. Unfortunately, there are two locations where .xsd
show up. The one you defined is the correct location!
-Alan
Original Message Follows
From: "Gert Driesen" <[EMAIL PROTECTED]>
To: "'Alan Guedeney'" <[EMAIL PROTECTED]>,
CC: <[EMAIL PROTECTED]
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:nant-users-
> [EMAIL PROTECTED] On Behalf Of Alan Guedeney
> Sent: woensdag 15 november 2006 21:15
> To: nant-users@lists.sourceforge.net
> Cc: [EMAIL PROTECTED]
> Subject: [NAnt-users] NAnt & VS 2005 Intellisense
>
>
> I can't get
I can't get this work. Most articles ask to me to follow the steps I
provided below. Does anyone have the same experience? Can anyone help me
solve this problem?
NAnt 0.85.2344.0
Microsoft Visual Studio 2005 Version: 8.0.50727.42
The nant.xsd second line is pointing to: http://nant.sf.net/rele
Michael Frederick wrote:
> Well, CCNet can do a "wait for multiple files to appear and start a
> project", but the changes all have to appear within one CCNet
> project-defined polling interval. Since I mentioned that the 3 worker
> projects may finish hours apart, I'm not sure if this is a goo
Well, that was a *thousand-foot-view* of the process. We use the same
technique (with lots more details) to accomplish the scenarios you
described. So far, it's been working for us (knock on wood).
Daniel
-Original Message-
From: Gary Feldman [mailto:[EMAIL PROTECTED]
Sent: Wednesda
Bill suggested using the asminfo task to generate AssemblyInfo files at
build time. That is exactly what we do and it works great. We source
control the file that stores the version number. When it is time to
make a build, we
- check out the version number for the particular project from source
Nguyen, Daniel wrote:
> Michael,
>
> My following suggestions may sound like a quick, ugly *hack*, so
> please take it with a grain of salt.
>
> If project B has to wait for project A to complete, can you place a
> call at the end of the project A to call project B once it's completed
> its
Yes, it does. We use it here for the same reason as Michael was looking
for. There are several nested elements comes with the task that
I thought were quite useful. You can check NAnt docs for more details
on this topic, but here's one of the examples --
Michael,
My following suggestions may sound like a quick, ugly *hack*, so please
take it with a grain of salt.
If project B has to wait for project A to complete, can you place a call
at the end of the project A to call project B once it's completed its
run?
Example:
http://nant.sf.net/schema
Well, CCNet can do a "wait for multiple files to appear and start a
project", but the changes all have to appear within one CCNet
project-defined polling interval. Since I mentioned that the 3 worker
projects may finish hours apart, I'm not sure if this is a good idea.
___
Can't cruise control do this for you by setting up a dependency on the
output of the first projects which cause the other projects to kick off,
etc.?
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Michael
Frederick
Sent: Wednesday, November 15,
I need a NAnt project to do some work and then wait for some event to
occur, such as a specific file in a specific directory to appear. To do
this I will need some sort of "while (file-exists != "true")"
capability. This means I would need 2 capabilities; a "sleep" taks
(which is present) and a l
Hi,
I'm using copy and filterchains to generate stub project layouts for visual
studio.
VisualStudio 2005, solution files start with the BOM, 0xefbbbf, and if the
BOM's not there, visual studio ignores the file (unhelpful!)
My task looks like this...
Hi Bob,
The way that I do this is to use the task
to generate the assemblyinfo file on the fly rather than having one in
the project. This way I can work out the version numbers into properties
(I use a time stamp style version number) and set this to the AssemblyVersionAttribute.
There's also
15 matches
Mail list logo