Eric Fetzer wrote:
The big benefit to the project references is that you
can step into the code. Log4net, we definitely
wouldn't want to do that with, but it can be helpful
for these in house projects...
You can step into the project even without project references - if the
debug symbols file
OTECTED]
14/09/2006 16:06
To
Bill Martin <[EMAIL PROTECTED]>,
'Nant Users'
cc
Subject
Re: [NAnt-users] Shared Components
I think that would be REALLY tough to maintain here.
In one of our apps, we have around 30 projects with
many dependancies interwoven throughout
scripts file that
> has all the / tasks etc in it so I can do
> global changes in one
> location. Any project file can always override the
> generic behaviour if it
> needs to implement a target in a specific fashion.
>
> HTH,
>
> Bill
>
>
>
> -----Orig
> Rod
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Bob
> Archer
> Sent: Tuesday, September 12, 2006 11:29 AM
> To: Eric Fetzer; Nant Users
> Subject: Re: [NAnt-users] Shared Components
>
> Do you have a link t
personally
> never found that necessary.
>
> Remember, if it were easy, everyone would be doing
> it.
>
> Bob
>
>
> -Original Message-
> From: Eric Fetzer [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 12, 2006 2:12 PM
> To: Bob Archer; Nant Us
ric behaviour if it
needs to implement a target in a specific fashion.
HTH,
Bill
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Eric Fetzer
Sent: 12 September 2006 16:39
To: Nant Users
Subject: [NAnt-users] Shared Components
I'm looking for &
idea!
Rod
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob
Archer
Sent: Tuesday, September 12, 2006 11:29 AM
To: Eric Fetzer; Nant Users
Subject: Re: [NAnt-users] Shared Components
Do you have a link to that article?
He is absolutely right. Whe
riginal Message-
From: Eric Fetzer [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 12, 2006 2:12 PM
To: Bob Archer; Nant Users
Subject: RE: [NAnt-users] Shared Components
Actually, John Mischel at Microsoft put out an article
entitled "Project Structure Best Practices" where he
ssage-
> From: Eric Fetzer [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 12, 2006 1:43 PM
> To: Bob Archer; Nant Users
> Subject: RE: [NAnt-users] Shared Components
>
> Thanks for your reply Bob and Rod!
>
> We've got a new twist that developed in a
roject and circumstances.
BOb
-Original Message-
From: Eric Fetzer [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 12, 2006 1:43 PM
To: Bob Archer; Nant Users
Subject: RE: [NAnt-users] Shared Components
Thanks for your reply Bob and Rod!
We've got a new twist that developed in a meeti
: Bob Archer; Nant Users
Subject: Re: [NAnt-users] Shared Components
Thanks for your reply Bob and Rod!
We've got a new twist that developed in a meeting this morning. We're
moving over to project references only. The lead architect here is
insistent because Microsoft considers this
to go with DLL
> references for internal
> DLLs that are shared by multiple projects. I think
> this is the way to
> go, and it works for us.
>
> BOb
>
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Eric
&
TED]
[mailto:[EMAIL PROTECTED] On Behalf Of Eric
Fetzer
Sent: Tuesday, September 12, 2006 11:39 AM
To: Nant Users
Subject: [NAnt-users] Shared Components
I'm looking for "Best Practices" for components that
are shared among several applications in reference to
NAnt. First of all, dll or
:[EMAIL PROTECTED] On Behalf Of Eric
Fetzer
Sent: Tuesday, September 12, 2006 8:39 AM
To: Nant Users
Subject: [NAnt-users] Shared Components
I'm looking for "Best Practices" for components that are shared among
several applications in reference to NAnt. First of all, dll or project
I'm looking for "Best Practices" for components that
are shared among several applications in reference to
NAnt. First of all, dll or project references. If I
have dll references, I have to get all of the
developers to keep these components in the same place
as I keep them for the build so that t
15 matches
Mail list logo