Page 61, inside the box. > -----Original Message----- > From: Andy Smith [mailto:[EMAIL PROTECTED]] > Sent: Monday, April 22, 2002 4:56 PM > To: Smith, Eric V.; [EMAIL PROTECTED] > Subject: RE: [nant-dev] Version task > > > I have that book, but don't remember reading that. > can you give me a page reference? > > ____________ > Andy Smith > Chief Code Monkey > > -----Original Message----- > From: Smith, Eric V. [mailto:[EMAIL PROTECTED]] > Sent: Monday, April 22, 2002 2:54 PM > To: [EMAIL PROTECTED] > Subject: RE: [nant-dev] Version task > > > Jeff Richter in "Applied Microsoft .Net Framework > Programming" argues against using the asterisk. I'm not sure > I buy his argument, but I respect his opinion. In addition, > I like having a deterministic nightly build number, or more > often if I build releases multiple times per day. > Accordingly, I like having more control over the entire > version number. > > My code supports asterisks, in any event. So you could have > a task that increments the minor version number from 1.2.* to > 1.3.* as such: > > <version increment="minor" property="project.version" > filename="AssemblyInfo.cs"/> > > > > -----Original Message----- > > From: Andy Smith [mailto:[EMAIL PROTECTED]] > > Sent: Monday, April 22, 2002 4:11 PM > > To: [EMAIL PROTECTED] > > Subject: RE: [nant-dev] Version task > > > > > > I don't understand why you need to write out the version > > number again... > > > > the whole asterix thing in the version number is designed to > > auto-increment the version. does this behavior only exist in c#??? > > > > ____________ > > Andy Smith > > Chief Code Monkey > > > > -----Original Message----- > > From: Smith, Eric V. [mailto:[EMAIL PROTECTED]] > > Sent: Monday, April 22, 2002 2:07 PM > > To: [EMAIL PROTECTED] > > Subject: RE: [nant-dev] Version task > > > > > > Andy Smith had an interesting comment in a private email. He > > suggested loading the file in with the CodeDom and then > > retrieving the assembly level attribute, and then > > generalizing this to reading any assembly attribute. I think > > this is a great idea, but now that I've thought about it I'm > > not sure about using it to write the file back out, which is > > what I do when incrementing the version number. > > > > For now, I think I'll just base it on the file extension and > > use a regex. I'll make the filename a required attribute. > > I'll play with the CodeDom version in my spare time. > > > > I've got the VB and MC++ versions working, but I can't figure > > out how to create a Jscript project. Does anyone know what > > the syntax for an assembly level attribute in Jscript would be? > > > > Eric. > > > > > -----Original Message----- > > > From: Scott Hernandez [mailto:[EMAIL PROTECTED]] > > > Sent: Monday, April 22, 2002 3:34 PM > > > To: Smith, Eric V.; [EMAIL PROTECTED] > > > Subject: RE: [nant-dev] Version task > > > > > > > > > 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 > > > > _______________________________________________ > 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
