Not possible to specify custom attributes with more than one constructor parameter

[petemounce]

I'm trying to use AssemblyInfoTask's custom-attributes feature to specify an FxCop System.Diagnostics.SuppressMessageAttribute, whose constructor has the following signature:

SuppressMessage(string categoryId, string checkId)

with optional parameters Justification, MessageId, Scope and Target but that feature seems to only support attributes with a single-parameter constructor.

I would like either

• to have support for that attribute a la the other specifically-supported ones
• to have support for attributes with more complicated constructors (more than one constructor parameter, plus optional named arguments)
• to have support for pushing in attributes as strings

[haf]

This could be a nice feature. If you are interested in cutting your teeth a little, then it would be a fix between these:

• https://github.com/derickbailey/Albacore/blob/master/lib/albacore/assemblyinfo.rb
• https://github.com/derickbailey/Albacore/tree/master/lib/albacore/assemblyinfolanguages

and this specification:

• https://github.com/derickbailey/Albacore/blob/master/spec/assemblyinfo_spec.rb

Workflow is:

• clone https://haf@github.com/derickbailey/Albacore.git -b dev
• git checkout -b multiparam_asminfo
• hack the code, specifically the spec
• run bundle exec rspec spec/assemblyinfo_spec.rb
• hack the implementation
• loop...
• git add . -A
• git commit -m "my fixes"
• git push -u petemounce multiparam_asminfo
• pull req. in github

[mxriverlynn]

it should be easy to add this as a feature to any attribute, so that we can do something like:

assemblyinfo do |asm|
  asm.custom_attribute :SomeAttribute => ["Arg1", true, "Arg3"]
end

and have that array generate the individual arguments to the attribute.

We would need to update the individual language engines for attribute generating. instead of: attribute << "#{attr_data.inspect}" it would be something like: attribute << [attr_data].flatten.map{|attr| attr.inspect}.join(", ")

of course, tests need to be written around this... and this is a total hackery-guess at the moment. :)

for now, you can manually produce what you need using the .custom_data field, which takes an array of strings and dumps them directly in to the output:

assemblyinfo do |asm|
  asm.custom_data "[assembly: SuppressMessage('someid', 'some message')]"
end

[petemounce]

Ah - I missed the .custom_data field; thanks.