re you using ?
Gert
- Original Message -
From: "Kevin Miller" <[EMAIL PROTECTED]>
To: "Gert Driesen" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Monday, March 01, 2004 6:54 PM
Subject: RE: [nant-dev] AsmInfo patch
Another bug that I noticed is
Title: RE: [nant-dev] AsmInfo patch
Funny, oh well it was fun getting my hands dirty with NAnt stuff again.
I say use my implementation :) Hmm, Not sure what which would be better.
I don't understand the importance of the 1.0 vs 1.1 comment differences when the file generated wil
Title: RE: [nant-dev] AsmInfo patch
Ah interesting. I am sure your CodeDOM-fu is better than mine.
I am not sure how negative the "extra" generation of the assemblyinfo file when switching runtimes is. I am guessing if you are building multiple runtime versions of your application
Saturday, February 28, 2004 4:28 PM
Subject: RE: [nant-dev] AsmInfo patch
Ah interesting. I am sure your CodeDOM-fu is better than mine.
I am not sure how negative the "extra" generation of the assemblyinfo file
when switching runtimes is. I am guessing if you are building multiple
r
ock that's automatically
generated by the code provider will be different) ...
Gert
- Original Message -
From: "Kevin Miller" <[EMAIL PROTECTED]>
To: "Gert Driesen" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Saturday, February 28, 2004 3:58 PM
Subject:
CTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, February 27, 2004 9:24 PM
Subject: [nant-dev] AsmInfo patch
I found the asminfo task today and fell in love. It solved a few
problems I was having with signing assemblies and paths to the key file.
I was frustrated by the fact that it always ge
I found the asminfo task today and fell in love. It solved a few
problems I was having with signing assemblies and paths to the key file.
I was frustrated by the fact that it always generates the
AssemblyInfo.cs file even if there are no changes. This causes the
csc/vbc task to build the project ev
