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.
