snk problem

H

Heron

Hi

I need to work on an application of wich the assemblies are signed with
a snk file. Problem is when I try to debug/run the app under my windows
account it will show a dialog asking for a key, on the windows account
of the previous developer it doesn't show the dialog. Anyone know how to
solve this?

Best regards.
 
J

Jeroen Mostert

Heron said:
I need to work on an application of wich the assemblies are signed with
a snk file. Problem is when I try to debug/run the app under my windows
account it will show a dialog asking for a key, on the windows account
of the previous developer it doesn't show the dialog. Anyone know how to
solve this?
It doesn't sound as though this has anything to do with the fact that the
assemblies are strongly named (which is what signing does). This should only
be an issue when *building* the application: if the build specifies that the
assembly must be signed and you don't have the key file, you can't build.
You'll need to make sure the original .snk file is included with the sources.

If you're not building, are you sure the "key" the dialog is referring to
doesn't refer to some sort of license key needed by the application itself?
Are you running the application from a network share or other untrusted
location? Is it complaining about missing or mismatched assemblies?

Failing all that, you'll have to be more specific about the message you're
getting.
 
J

Jeroen Mostert

Jeroen said:
It doesn't sound as though this has anything to do with the fact that
the assemblies are strongly named (which is what signing does). This
should only be an issue when *building* the application: if the build
specifies that the assembly must be signed and you don't have the key
file, you can't build. You'll need to make sure the original .snk file
is included with the sources.
Also, it's possible that the key file is itself protected with a password. I
forgot about this since I never use it, but it's possible you'll need to
re-enter the password if you switch accounts or project files.

Finally, the assembly might be delay signed. That means the key used for
signing cannot actually produce a working assembly without turning off
assembly verification, and for the final build you have to have the "real"
key (for more information about this, see the help).
 
H

Heron

The source is located on my local d drive and has the original snk set.
I'll post the specific message tomorrow since I'm not at work anymore
now. Anyway, I had asked some ppl on the floor about it and found out
they had the same problem long ago but couldn't remember how to solve it
exactly, like "...uuuhmmm...you need to change some properties in a
certain order and that will fix it ..." :p


Jeroen Mostert schreef:
 

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

Top