This question is locked. New answers and comments are not allowed.
Hi,
I'm currently evaluating OpenAccess and I ran across what appears to be a bug or a limitation. Our application signs the assemblies to give them strong naming. We use a PFX file (password protected) instead of an SNK (not password protected) to do the signing. This is all done during compile time via Visual Studio. This was not using MSBuild (yet). When I compile the solution after adding an assemble that has been enabled for OpenAccess, I get errors due to those assemblies not being signed. I also verified in Reflector that they are not signed. After some searching and experimenting with VEnhance, I tried generating a one off SNK file and signed it with that. The assembly is now signed correctly.
Is this a known issue? Is there a workaround to sign the assembly using a PFX file?
Thanks,
Joe
I'm currently evaluating OpenAccess and I ran across what appears to be a bug or a limitation. Our application signs the assemblies to give them strong naming. We use a PFX file (password protected) instead of an SNK (not password protected) to do the signing. This is all done during compile time via Visual Studio. This was not using MSBuild (yet). When I compile the solution after adding an assemble that has been enabled for OpenAccess, I get errors due to those assemblies not being signed. I also verified in Reflector that they are not signed. After some searching and experimenting with VEnhance, I tried generating a one off SNK file and signed it with that. The assembly is now signed correctly.
Is this a known issue? Is there a workaround to sign the assembly using a PFX file?
Thanks,
Joe