Based on the code of the asminfo task, it looks like it
would be easy to add a "langauge" option that could
generate a VB.NET assemblyInfo file:
ICodeGenerator codegen = null;
switch(
this.Language )
{
case "vb":
VBCodeProvider vbProvider = new
VBCodeProvider();
codegen = vbProvider.CreateGenerator();
break;
case "cs":
CSharpCodeProvider csProvider = new
CSharpCodeProvider();
codegen = csProvider.CreateGenerator();
break;
// you'd need to add a reference to Microsoft.JScript.dll
to support JScript, and this didn't seem critical enough
at this point
//
case "jscript":
//
Microsoft.JScript.JScriptCodeProvider
jsProvider = new Microsoft.JScript.JScriptCodeProvider();
//
codegen = jsProvider.CreateGenerator();
//
break;
default:
throw new NotSupportedException
(AssemblyRM.GetString("UnsupportedLanguage",
this.Language));
}
using(
System.IO.StreamWriter sw = new
System.IO.StreamWriter
(Path,false,System.Text.Encoding.Default) )
{
codegen.GenerateCodeFromCompileUnit
(compileUnit, sw, new CodeGeneratorOptions());
sw.Close();
}
submitted by Brian Moore
(mailto:brmoore@hotmail.com)
Logged In: YES
user_id=707851
This was added a long time ago.
Note : the <asminfo> task has been moved to NAnt.