Problem with signing assemblies using AL.exe (Strong name signing an unsigned assembly)

P

Poggs

I got this error while signing an unsigned assembly.
ALINK: warning AL1020: Ignoring included assembly 'Validator.dll'
ALINK: error AL1016: No valid input files were specified

This is my AL command : al /out:Validator2.dll /keyfile:myKey.snk
Validator.dll

What am I doing wrong here..

Anyway, my real problem is how to strong name sign an unsigned assembly that
contains unmanaged code. Is this possible. I tried signer.exe but it cannot
handle the non-IL codes in there.

Any help will be highly appreciated
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Anybody use Strong Name Signing? 7
problem with assembly signing and strong names 1
Install custom action fails when assembly signed w/ strong name ke 10
Satellite assemblies and strong names 2
Re: error CS1548: Cryptographic failure while signing assembly 1
code signing problem 2
Installing an assembly in GAC without strong name 1
Using AL.exe to link modules into assembly 4

Top