[Mono-bugs] [Bug 542461] New: Assembly signing configuration properties inconsistent with MSBuild

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Sat Sep 26 15:36:38 EDT 2009


           Summary: Assembly signing configuration properties inconsistent
                    with MSBuild
    Classification: Mono
           Product: Mono: Tools
           Version: 2.4.x
          Platform: i386
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: xbuild
        AssignedTo: jankit at novell.com
        ReportedBy: xenolinguist at gmail.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US;
rv: Gecko/20090824 Firefox/3.5.3 GTB5

Xbuild currently uses a property called "KeyOriginatorFile" to control whether
assembly signing is performed by the compiler. Projects created by Visual
Studio will never provide this property, however.

Visual Studio creates project files with 2 properties regarding (normal,
non-delay) assembly signing. One property is a boolean named "SignAssembly"
which when false should bypass signing altogether. The other is a string named
"AssemblyOriginatorKeyFile" containing the name/path of the strong-name key
file. This latter property's value should only be passed to the compiler when
the aforementioned boolean is "true".

Reproducible: Always

Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

More information about the mono-bugs mailing list