Hi James, I would be also interested to use such task, feel free to give it out for testing :). May be I would prefer to be able to use (test) in the way, that does not conflict with current nant installation, if possible. As far as I understand if you will give to the task "asm_info" name, it will conflict with nants ant_info task, and couldn't be loaded with loadtask. Right?
Boni -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gert Driesen Sent: Dienstag, 22. August 2006 19:47 To: 'James Johnston'; nant-users@lists.sourceforge.net Subject: Re: [NAnt-users] Extending asminfo Task > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:nant-users- > [EMAIL PROTECTED] On Behalf Of James Johnston > Sent: dinsdag 22 augustus 2006 20:07 > To: nant-users@lists.sourceforge.net > Subject: [NAnt-users] Extending asminfo Task > > It seems that the AssemblyInfoTask (asminfo) is very inflexible in > that you are fixed to using the VB/C# code DOMs. I would like to use > it with the new CppCodeProvider in .NET 2.0 for generating C++ code, > and I'm sure there are other code generators out there that people > would also like to use. > > Has any work been done to add this sort of feature to AssemblyInfoTask? > The current "Language" property is a simple enumeration. I'm thinking > that in addition to that property, there should be a "CodeProviderType" > property that contains the full type name so one can use any arbitrary > code generator. E.g. one could set it to > "Microsoft.VisualC.CppCodeProvider, CppCodeProvider, Version=8.0.0.0, > Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a". I think the answer > is not to simply add "C++" to the CodeLanguage enumeration, because > there are three different C++ code generators: MCppCodeProvider (for > v1.1), CppCodeProvider (for v2.0), and CppCodeProvider7 (also comes > with > VC++ 8.0). And there are likely code DOMs for other languages too. > > If there is interest for this enhancement, I would just as soon make > the changes myself and submit a changeset - I don't think it would be > very hard to add a feature like this. Sure, there's interest for this. I wouldn't add a new attribute though. Let's just change the existing Language property (language attribute) to take a string. Have a look at the <script> task as we do exactly the same there. The <asminfo> task should probably also support setting named attribute arguments (using a nested <argument> type). Gert ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ NAnt-users mailing list NAnt-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ NAnt-users mailing list NAnt-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
