{"id":5515,"date":"2014-03-30T23:33:52","date_gmt":"2014-03-30T23:33:52","guid":{"rendered":"https:\/\/unknownerror.org\/index.php\/2014\/03\/30\/why-exactly-does-regasm-warn-me-about-signing-with-a-strong-name-collection-of-common-programming-errors\/"},"modified":"2014-03-30T23:33:52","modified_gmt":"2014-03-30T23:33:52","slug":"why-exactly-does-regasm-warn-me-about-signing-with-a-strong-name-collection-of-common-programming-errors","status":"publish","type":"post","link":"https:\/\/unknownerror.org\/index.php\/2014\/03\/30\/why-exactly-does-regasm-warn-me-about-signing-with-a-strong-name-collection-of-common-programming-errors\/","title":{"rendered":"Why exactly does regasm warn me about signing with a strong name?-Collection of common programming errors"},"content":{"rendered":"<p>It is a clumsy warning. There are two aspects to COM DLL Hell. The really bad one is modifying the public interfaces and not assigning new GUIDs. A client app that wasn&#8217;t recompiled tends to crash and burn when it calls an entirely wrong method or bombs with a nasty AccessViolationException that gives no clue at all what the cause might be.<\/p>\n<p>The second one is doing everything right (assigning new GUIDs) but then overwriting the existing DLL with the new version. You&#8217;ll still crash that stale client app but more mildly with an E_NOINTERFACE hresult that generates a pretty specific exception that helps you diagnose the cause. The user isn&#8217;t any happier though.<\/p>\n<p><em>That<\/em> scenario has a ready solution in .NET, the GAC supports side-by-side deployment of assemblies with different version numbers so that both the old and the new version can co-exist and the stale client app continues to be happy with the old version. Which requires a strong name. Yes, that warning could certainly have been suppressed when you use \/codebase since that makes it quite clear you are not going to use the GAC. Although it doesn&#8217;t hurt to tweak your nose a bit at using \/codebase. Also, you never use the GAC on your dev machine while testing but certainly should consider it when deploying.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>It is a clumsy warning. There are two aspects to COM DLL Hell. The really bad one is modifying the public interfaces and not assigning new GUIDs. A client app that wasn&#8217;t recompiled tends to crash and burn when it calls an entirely wrong method or bombs with a nasty AccessViolationException that gives no clue [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-5515","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/posts\/5515","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/comments?post=5515"}],"version-history":[{"count":0,"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/posts\/5515\/revisions"}],"wp:attachment":[{"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/media?parent=5515"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/categories?post=5515"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/tags?post=5515"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}