Ok, so I'm not doing anything out of the ordinary.
Looks like it is only tools like DevExpress that REQUIRE that you install it
onto the build server that messes things up.
-David Burela
On 8 February 2011 21:05, Stephen Price step...@littlevoices.com wrote:
+1 for a Third party/dependencies
Any reason you can't just grab their binaries and check them in?
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of David Burela
Sent: Wednesday, February 09, 2011 5:25 AM
To: ozDotNet
Subject: Re: Handling 3rd party assemblies with build servers
Ok, so I'm
Telerik play nice, we've just got a lib folder with the 3rd party
binaries in there. All compiles find on a clean checkout and on the
build server. We've done this with both their WPF controls and their
MVC controls.
Neil.
On 10 February 2011 09:42, David Burela david.bur...@gmail.com wrote:
Like others I use a 3rdParty folder for my dependencies, but I'm undecided
whether to do this for my installer bootstrapper.
So far I've been embedding the .NET 4 web installer (869 KB) which I've
added to my 3rdParty folder so it's included in a fresh checkout in order to
build the bootstrapper.
On Thu, Feb 10, 2011 at 11:44 AM, Matt Siebert mlsieb...@gmail.com wrote:
Like others I use a 3rdParty folder for my dependencies, but I'm undecided
whether to do this for my installer bootstrapper.
So far I've been embedding the .NET 4 web installer (869 KB) which I've
added to my 3rdParty
I guess I was reluctant because of the delay involved in doing a checkout
over a slow network - i.e. if I did a checkout from home then it'd take
forever since the office's upstream bandwidth is so slow.
That said it's pretty rare to do a full checkout (usually just updates) so I
think I can live
