[Nant-users] Accessing framework DLL's

2003-01-24 Thread Nick Robinson



Hi,
 
Can someone offer 
some guidance when dealing with assemblies that are dotted around the 
framework.  Using Slingshot, it places ${reference.path} in front of such 
items, such as 
 
${reference.path}/envdte.dll
 
If I was checking 
this project into sourcesafe, and expecting draco to do a check out, how would I 
deal with such files?
 
Thanks
 
Nick.
<>

RE: [Nant-users] Accessing framework DLL's

2003-01-24 Thread Lorphelin, Yves
Title: RE:  [Nant-users] Accessing framework DLL's






Hi Nick, 
The way We deal here with 3d party bianries is just check them in in sourcesafe in a project "lib" with the source code: that way we are sure that every developper uses the same version, 

& the 3rd parties binaries are versioned with the product: for example:
MyProduct Version 1.0 uses 3d party 1.0
MyProduct Version 2.0 uses 3d party 1.0
My product Version 3.0 uses 3d party 2.0
If I have to patch Version 2.0 I'don't need to find 3'd party 1.0 , it's in souresafe.



Hope this helps .



-Original Message-
From: Nick Robinson [mailto:[EMAIL PROTECTED]] 
Sent: 24 January 2003 15:33
To: [EMAIL PROTECTED]
Subject: [Nant-users] Accessing framework DLL's



Hi,


Can someone offer some guidance when dealing with assemblies that are dotted around the framework.  Using Slingshot, it places ${reference.path} in front of such items, such as 

${reference.path}/envdte.dll


If I was checking this project into sourcesafe, and expecting draco to do a check out, how would I deal with such files?

Thanks


Nick.





Re: [Nant-users] NAnt and Visual Studio.NET Projects

2003-01-24 Thread Brant Carter
Klaus, there is a tool called Slingshot which with a bit of work will do 
what you want.  It will read your .sln files and generate nant compliant 
.build files.  You might also want to look at this article which provides a 
different solution to the problem.

http://radio.weblogs.com/0106046/stories/2002/08/10/supportingVsnetAndNant.html

You probably want to generate the .build files from the .sln since that is 
what the developers will be using.  Note that Slingshot is part of the 
NAntContrib project.

cheers,

brant
...



Message: 2
From:	Klaus Hofmann <[EMAIL PROTECTED]>
To:	"'[EMAIL PROTECTED]'"
	<[EMAIL PROTECTED]>
Date:	Thu, 23 Jan 2003 09:45:13 +0100
Subject: [Nant-users] NAnt and Visual Studio.NET Projects

Hi all,

we are developing a new product and use NAnt for the builds on our compile
server. For each project we also use Visual Studio.NET project files,
because we need them for debugging and other things.

Now i am looking for a way to generate these Visual Studio.NET project 
files
from the NAnt build files or to generate NAnt build files and VS.NET 
project
files from a XML Meta Definition. Has anybody done some work in this area 
or
can you give me a hint for information.

I know about Slingshot but thats not realy what i want. I want to use the
NAnt build system for the master build on the compile server because we 
have
to integrate other usefull stuff: unit tests, documentation generation,
additional checks for programming conventions, etc.

Thanx
  Klaus




_
The new MSN 8: advanced junk mail protection and 2 months FREE*  
http://join.msn.com/?page=features/junkmail



---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
___
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users