Databases
StackOverflow2013
Postsdbo
POStrong name validation failed on VB.NET Assembly
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POStrong name validation failed on VB.NET Assembly
    primarykey
    data
    text
    <p>I have a VB.Net 1.1 application works just fine after compiling in Visual Studio. However, I want to use ILMerge to combine all the referenced assemblies into a single executable just to make it easier to move around. After I send it through ILMerge and try to run it I get the error </p> <p>"Strong name validation failed for assembly.exe" .....</p> <p>But none of my stuff is strong named! I saw this post here: <a href="https://stackoverflow.com/questions/403731/strong-name-validation-failed">Strong Name Validation Failed</a> and tried running it through 'sn.exe -Vr merged.exe' but that gives me this error:</p> <p>"merged.exe does not represent a strongly named assembly"</p> <p>Has anyone else had this problem before? How do I fix it?</p> <p>UPDATE:</p> <p>I'm starting to feel like Strong name validation isn't the real problem here. I'm building against .NET v1.1 and running on a machine where that is the only .NET version installed (happens to be Windows 2003). The merged executable appears to die with that error on every Windows 2003 machine I try, but if I try to run it on a more modern OS (Vista) it at least starts, but that's not really a good test since the environment isn't fit for a real test.</p> <ul> <li>I have verified that my app.config has the correct settings (specifying required and supported runtime version of v1.1.4322)</li> <li>I use the /targetplatform:v1.1 option when running my assemblies through ILMerge. </li> </ul> <p>ILMerge is definitely causing the problem (i.e. it works fine before I merge), I just don't know how to fix it.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USMatt Baker
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POStrong name validation failed on VB.NET Assembly
      1. This table or related slice is empty.
      1. VTUpMod
    1. CODocument the references you use. Click the "show all files" icon in Solution Explorer and open the References node.
      singulars
      1. POStrong name validation failed on VB.NET Assembly
      1. USHans Passant
    2. COAll I'm referencing is a COM interop assembly and the standard System Assemblies. I am NOT internalizing the Interop assembly, only the assemblies that are part of this project (one executable and a DLL), neither of which are signed. None of the referenced assemblies are signed either (except the Core .NET assemblies; but again, I'm not internalizing those).
      singulars
      1. POStrong name validation failed on VB.NET Assembly
      1. USMatt Baker
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload