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 7059753
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 28, 20262026-05-28T04:16:13+00:00 2026-05-28T04:16:13+00:00

We need to patch an assembly and we can’t rebuild from source code at

  • 0

We need to patch an assembly and we can’t rebuild from source code at the moment. I can dump the IL using ildasm mydll.dll /all /out=mydll.il and then I can rebuild it with ilasm /dll mydll.il and it’s all good except that things like file version, public key, etc are all missing from the new binary. How can I tell ilasm to add these in? I’ve tried the /mdv switch with no luck.

  • 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-28T04:16:14+00:00Added an answer on May 28, 2026 at 4:16 am

    The key won’t round trip – otherwise you would be able to hack anyone’s assembly and pass it off as an original.

    In order to sign the assembly in your situation you’ll need the key. Once you have decompiled your assembly, patched it – its easiest if you go ahead and add the following line in the area where the other Assmbly attributes are:

    .custom instance void [mscorlib]System.Reflection.AssemblyDelaySignAttribute::.ctor(bool) = ( 01 00 00 00 00 ) 
    

    That attribute tells ilasm to leave room for the key. Once you’ve added that attribute and reassembled your code using ilasm, you then need to use the sn utility to delay sign it. The syntax should be something like this:

    sn /R myreassembled.dll originalassemblykey.snk
    

    That should resign the assembly.

    Which file version are you refering to? It should be an assembly attribute in the IL, but if not you may need the al.exe utility to do that.

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

Sidebar

Related Questions

I'm compiling from csc.exe (well, CruiseControl is...), and I need to reference a DLL
I need to access a web application's web.config from a referenced assembly. I need
How do I get the path of the current assembly? I need to get
I need to write a small console app (patch) that turns off the print
If we need to issue a bug patch that does not include current development
The following code works, but I'm curious as to why I need the Path
I know you need to turn on the 'Native Code' debugger in order to
I need to add an assembly probing path at runtime , not through the
I have a ASP.net application that is referencing a external assembly that I need
How can I get the (physical) installed path of a DLL that is (may

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.