Nice spotting there ;-)
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of David Burela
Sent: Thursday, 17 March 2011 1:13 PM
To: ozDotNet
Subject: Re: Handling 3rd party assemblies with build servers
For anyone interested, I just saw this article come up
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
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 not doing anything out of the ordinary.
Looks
Burela
Sent: Wednesday, February 09, 2011 5:25 AM
To: ozDotNet
Subject: Re: Handling 3rd party assemblies with build servers
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
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
Interesting, our dev team was talking about this issue just today.
In our team we check in any 3rd party assemblies into a folder like
you've done. If an assembly is downloadable in source form we do a
compilation and then the source goes with the pre-built assembly and
generally works pretty
+1 for a Third party/dependencies folder. Here its called Lib. I've
used Dependencies in the past. Its good to have everyone using the
same version.
I had an issue with a fresh get of the solution yesterday and it
turned out the reference was pointing at the release folder of a
solution. The devs
[mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of David Burela
Sent: Monday, February 07, 2011 8:09 PM
To: ozDotNet
Subject: Handling 3rd party assemblies with build servers
For the last few years I've used a fairly standard way of handling 3rd party
assemblies.
In source control, I create
Of *David Burela
*Sent:* Monday, February 07, 2011 8:09 PM
*To:* ozDotNet
*Subject:* Handling 3rd party assemblies with build servers
For the last few years I've used a fairly standard way of handling 3rd
party assemblies.
In source control, I create a folder called 3rd Party Assemblies
On Tue, Feb 8, 2011 at 3:48 PM, David Kean david.k...@microsoft.com wrote:
Now I’m from Microsoft, so bear in mind that we tend to over engineer
solutions, however, we typically make sure everything is in source control.
(In the Developer Division case, this even extends to.NET [and VS!], but
[mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of mike smith
Sent: Monday, February 07, 2011 10:13 PM
To: ozDotNet
Subject: Re: Handling 3rd party assemblies with build servers
On Tue, Feb 8, 2011 at 3:48 PM, David Kean
david.k...@microsoft.commailto:david.k...@microsoft.com wrote:
Now I’m from
13 matches
Mail list logo
