Key usage permission with VS 2013 Update 4

Question

1.00/5 (1 vote)

See more:

Hi,

Starting from Update 4 for Visual Studio 2013 I started to get a "Request for permission to use a key" every time I compile an application. The options I have are grant or deny.

This seems to be related to the fact that the application is distributed using ClickOnce and the manifest is signed. The certificate is located in store (not in a file). If I remove the manifest signing the question disappears.

If I don't give the permission I'll ed up to error MSB3482 but this is obvious. If I grant the permission the compile works just fine but this is becoming rather annoying since I have to give this permission again and again, for each compile...

I tried to find info for this but I couldn't find anything. Is anyone else suffering from this kind of behaviour or better yet, know a solution? And as said the same project worked like a charm in VS2013 Update 3.

Posted 2-Dec-14 0:02am

Wendelius

Add a Solution

Comments

Kornfeld Eliyahu Peter 2-Dec-14 6:14am

I think you should report it to MS...https://connect.microsoft.com/

Wendelius 2-Dec-14 7:06am

Thanks for the suggestion! I reported this and let's see what happens... Anyhow, I'll keep this question open in case someone already has some info.

Kornfeld Eliyahu Peter 2-Dec-14 7:09am

You may add link to your report here, so those who experience it may vote for...

Wendelius 2-Dec-14 7:59am

Actually I reported this as private so it's not publicly visible. I'll update this if I get any info.

Member 11348764 2-Jan-15 20:27pm

Hi Mika

Do you find any resolution for this issue, i faced the same issue with my VS 2013Update 4, do let me know if you have any resolution.

Wendelius 3-Jan-15 3:40am

Hi, so far there's no solution for the problem. I've received few suggestions but they haven't helped me. However, have a try if they would be helpful for you.

Suggestions:
- instead of using a certificate file, save the certificate to local store and use it from there (for me this has been the case all the time)
- check that the certificate isn't expired
- remove the certificate from the store and and save it again.

Hopefully your situation would be solved with these :)

Cheers.

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)