Yes but remember that AssemblyInfo.cs is not required meaning I could put
the assemblyinformation in helloworld.cs and it will compile just fine. I
guess this is the tradeoff between ease of use and assumptions.
Rob
"Scott Hernandez"
<[EMAIL PROTECTED]> To: "'Smith, Eric
V.'" <[EMAIL PROTECTED]>,
Sent by:
[EMAIL PROTECTED]
[EMAIL PROTECTED] cc:
eforge.net Subject: RE:
[nant-dev] Version task
04/22/2002 02:33 PM
Yeah, I think making the filename required is good. Or require a
language attribute (it could be an enum). Then you could set the default
filename based on that. Either way, it seems like one of them needs to
be required.
You could do something like:
<version language="CSharp/VB/C++Managed/etc" .../>
> -----Original Message-----
> From: [EMAIL PROTECTED]
[mailto:nant-developers-
> [EMAIL PROTECTED]] On Behalf Of Smith, Eric V.
> Sent: Monday, April 22, 2002 10:36 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [nant-dev] Version task
>
> It currently only works on AssemblyInfo.cs (or whatever file name you
> specify). I'll work on the vb.net and jscript.net versions, that's a
> good idea. I'll just base it off of the file extension. Should I
make
> the filename mandatory? It currently defaults to AssemblyInfo.cs. I
> sort of like making it mandatory, so that you can look at the .build
> file and tell where it's getting the version info.
_______________________________________________
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
_______________________________________________
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
