You can have as many AssemblyInfo.cs as you want; the actual file name doesn't
matter.
So you can just put additional assembly attributes in a different file, which
then will be compiled, but let untouched by NPanday.
_
Lars
Am 10.01.2012 um 13:40 schrieb Brett Porter:
I don't think that's possible, from my understanding of the code.
You could probably supply a custom AssemblyInfo.cs generated/modified by
hand. Otherwise, DefaultAssemblyInfoMarshaller would need to be improved to
support custom/missing types.
- Brett
On 10/01/2012, at 9:07 PM, Matthias Wessendorf wrote:
using the assemblyInfo @parameter, like:
assemblyInfo
key1FOO/key1
key2FOO/key2
/assemblyInfo
gives me the following:
[assembly: CustomStringAttribute(key1, FOO)]
[assembly: CustomStringAttribute(key2, FOO)]
Not quite what I want -
On Tue, Jan 10, 2012 at 10:41 AM, Matthias Wessendorf mat...@apache.org
wrote:
Hi,
is there a way to easily append (desired) attributes to the generated
AssemblyInfo.cs file ?
I'd like to have the following attributes in there:
[assembly: InternalsVisibleTo(Mocks)]
[assembly: InternalsVisibleTo(MockObjects)]
Thx!
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/
