Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 966475
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 16, 20262026-05-16T02:09:43+00:00 2026-05-16T02:09:43+00:00

I have a test project for a web service and, when I run tests

  • 0

I have a test project for a web service and, when I run tests in debug mode, everything works ok. However, when I just run tests, I get following error, for a referenced assembly that I try to obtain code coverage:

Class Initialization method WebServiceTest.wstest.MyClassInitialize threw exception. System.IO.FileLoadException: System.IO.FileLoadException: Could not load file or assembly ‘TestAssembly, Version=1.0.0.0, Culture=neutral, PublicKeyToken=57f286581e1d278a’ or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A) —> System.Security.SecurityException: Strong name validation failed. (Exception from HRESULT: 0x8013141A).
Everything I found said to register TestAssembly in GAC. Is this what should I do? Why is it working in debug mode?
Thank you

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-16T02:09:44+00:00Added an answer on May 16, 2026 at 2:09 am

    I had the same problem, and the link below helped me…

    http://weblogs.asp.net/soever/archive/2005/07/23/420338.aspx

    VS.NET 2005: Code coverage for signed assemblies
    I am currently working on an application using VS.NET 2005, and because all the TDD tools like unit testing and code coverage are available I started to use them.

    When I started code coverage on my signed application I got the following exception:

    Test method X threw exception: System.IO.FileLoadException: Could not load file or assembly ‘Y, Version=1.0.0.0, Culture=neutral, PublicKeyToken=Z’ or one of its dependencies. HRESULT: 0x8013141A Strong name validation failed. —> System.Security.SecurityException: Exception from HRESULT: 0x8013141A Strong name validation failed at X.

    Not so strange if you think about it. Assembly is signed, code coverage needs code instrumentation, means modifications of the assembly, resulting in incorrect assembly so the validation failed.

    Solution is to resign the assembly after instrumentation.

    If you open the localtestrun.testrunconfig file (or something similar) in your solution items (double-click it), you can enable resigning in the Code Coverage section. This solves the problem.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have the following layers in my project Web/UI, Service, Repository, Common and some
I have this simple test project just to test the IncludeExceptionDetailInFaults behavior. public class
We are currently using unit tests to test our project. We have the majority
I have a web service that is quite heavy on database access. It works
I use asp.net and web forms. In my project I have asmx web service
We have a large system of physical devices which all run a web service
I have a web service project that contains 3 classes: 1 Abstract public class
I have a WCF web service called Palladium that is created as a project
I have a test project using MbUnit and TestDriven.Net. If I right-click on an
I have a unit test project based on UnitTest++. I usually put a breakpoint

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.