Hello,
I'm glad, I'm not the only one having problem with this :-)
queu ccnet build will help, since nant will compile those sequentially. Or I
think, it would help. But I'm not sure, if using _any_ cache is good thing.
I want to do CLEAN build, so I delete all output files, all obj folder
and
But I'm not sure, if using _any_ cache is good thing.
I understand, but we should remain compatible with VS where
possible and in this case it's even necessary (for creating
strong named assemblies).
Could you clarify that strong name thing, please?
VS compatibility is a good thing, but I
- Original Message -
From: Martin Aliger [EMAIL PROTECTED]
To: 'Gert Driesen' [EMAIL PROTECTED]; 'mike61079'
[EMAIL PROTECTED]; nant-developers@lists.sourceforge.net
Sent: Wednesday, August 02, 2006 11:16 AM
Subject: RE: [nant-dev] VSWebCache ObjectDir solution
But I'm not sure, if
Would a clean mode help you sleep better, or do you want to
get rid of the
VSWebCache for another reason (eg. for parellel builds,
although you'll have
this problem too with local obj dirs) ?
The parallel builds nighmares me. obj dirs are ok, I think. They should not
cause any trouble.
- Original Message -
From: Martin Aliger [EMAIL PROTECTED]
To: 'Gert Driesen' [EMAIL PROTECTED]; 'mike61079'
[EMAIL PROTECTED]; nant-developers@lists.sourceforge.net
Sent: Wednesday, August 02, 2006 12:50 PM
Subject: Re: [nant-dev] VSWebCache ObjectDir solution
Would a clean mode
Changing to a local store for intermediate build output will
not resolve
issues if you build a project in parallel from the same local project
directory, but I'm sure that's not what you're doing.
No no! I have 2 distinct local directories with project of the same name.
Those 2 projects
I have the same setup as you, everything is in distinct directories and then
it ends up sharing VSWebCache because the project names are the same.
I thought VS also built files in a local obj directory? I know for DLL's it
does that. Is there a way to use that with web projects? Ugh, if there
