Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report for Bug 725 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
error CS1548: Error during assembly signing. The specified key file `xxx.key.pfx' has incorrect formatWhen I signing a class type project, it build success on Visual Studio 2010
Could you attach the actual key or generate one which causes same problem
.pfx are PKCS#12 files. It looks like newer (2010?) version of Visual Studio allows people to strong name assemblies using them.
Mono.Security.dll support PKCS#12 files (mscorlib.dll too but only when used with X.509 certificates) but it's not clear that we want to embed all that code into the compiler!?!
Sebastian, can you attach example of such key
Created attachment 335 [details]
sn key file
it contains passord:123456
The sn key file were created by virsual studio 2010.
If I create a sn key file by %Program Files%\Mono-2.10.5\bin\sn.bat, both virsual studio 2010 and monodevelop 2.6 works, but no password.
Marek, I don't have a windows VM running at the moment but Minco's attachment is a valid pkcs#12 file, but without a certificate - i.e. only an encrypted keypair.
Minco, Mono's 'sn' tool (sn.bat on windows) currently only supports .snk (password-less files) and key containers. The same is true for the xMCS compilers.
I have done some further investigation and the way how it works with VS is that the file does not have to be installed but VS asks for a password and creates temporary container, the command line to C# compiler then contains key container
I don't know whether XXXX is some file hash
I am leaving this as MD bug as it cannot send such files to compiler using -keyfile option