Visual Studio 2010 - Error signing assembly

Question

0.00/5 (No votes)

See more:

Hello,

I'm having an error when compiling my solution in Visual Studio 2010.

It gives me this error "Assembly signing failed; output may not be signed -- Error signing assembly -- The process cannot access the file because it is being used by another process.".

I have the same strong name key to all the projects in the solution (can this be the problem?).

Sometimes i'm able to compile it, but most of the time, gives me this error in one or another project. To be able to compile the solution i have to compile each project at a time.

Can you help me please?

Best regards

Bruno Fernandes

Posted 21-Feb-13 0:57am

bsilence

Add a Solution

2 solutions

Add a Solution

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)

Steve Maier · Answer 1 · 2013-02-21T04:29:00

Solution 1

What I have seen when I have had this is that VS2010 is compiling the code across multiple processes and it does not always play nicely with each other. To get around this, you can go into the Tools->Options->Projects and Solutions->Build and Run and then change the maximum number of parallel projects to 1. You might be able to experiment with 2 or 4, but the value defaults to the number of cores that you have. This will make your builds slower since it will only compile 1 project at a time, but I have seen this type of issue go away once I backed down on the parallel compiling.

Posted 21-Feb-13 4:29am

Steve Maier

Comments

bsilence 21-Feb-13 11:17am

Hello, thank you for your help, but this didn't solved my problem...

Steve Maier 21-Feb-13 17:10pm

Another thing that it could be is Symantec Auto-Protect. I am actually seeing that at work today. I am testing with putting my source code folder as an exception to the Auto-Protect. I don't see this at home because I use Vipre there and not Symantec.

Dominick Sidiropoulos 25-Oct-15 22:31pm

AntiViruses can definitely take the blame for many of these signing errors. Panda AV (free edition) certainly clogs signing in VS2013. Workarounds:

- Disable AV all together
- In VS options set the number of projects being build in parallel to 1 (this works only sometimes).

http://support.pandasecurity.com/forum/viewtopic.php?f=83&t=4916&sid=1ef0473328c75b12d65ddd11b209801d&start=10

Okwkwe Anyasi · Answer 2 · 2014-04-23T23:21:00

Solution 2

Take a look at this link

Error Deploying Visual Studio Workflows

I hope this helps.

Posted 23-Apr-14 23:21pm

Okwkwe Anyasi