{"id":4044,"date":"2014-03-30T07:21:02","date_gmt":"2014-03-30T07:21:02","guid":{"rendered":"https:\/\/unknownerror.org\/index.php\/2014\/03\/30\/sp1-dlls-on-non-sp1-machine-public-deployment-collection-of-common-programming-errors\/"},"modified":"2014-03-30T07:21:02","modified_gmt":"2014-03-30T07:21:02","slug":"sp1-dlls-on-non-sp1-machine-public-deployment-collection-of-common-programming-errors","status":"publish","type":"post","link":"https:\/\/unknownerror.org\/index.php\/2014\/03\/30\/sp1-dlls-on-non-sp1-machine-public-deployment-collection-of-common-programming-errors\/","title":{"rendered":"SP1 dlls on non-SP1 machine (public deployment)-Collection of common programming errors"},"content":{"rendered":"

Hi<\/p>\n

I have unmanaged dll that I created using VS 2005. This dll is used by some managed C# code. \u00a0Prior to installing SP1, when\u00a0building the dll in VS, it was creating manifest that was referencing name=’Microsoft.VC80.CRT’ version=’8.0.50608.0′. After installing SP1 it started to create manifest that is referencing name=”Microsoft.VC80.CRT” version=”8.0.50727.762″. This behavior\u00a0causes breaking change for me, meaning that if I don’t change anything in my code, I won’t be able to run my dll on the machine that doesn’t have SP1 installed. My client machines have only .NET 2.0 installed. I personally think that it would make sense to keep old behavior and this way right version is used on both SP1 and non SP1 machines. Ideally I would like to have manifest tool or whatever else to simulate pre SP1 behavior and embed manifest with\u00a0the\u00a0‘8.0.50608.0’\u00a0build number.\u00a0 It is not acceptable for me to ship the app with the c runtime dlls. I am currently trying to deploy the dll with the manifest that I manually created, to see if this would work for me. (It might not because of the way this dll is used by the other processes)<\/p>\n

Questions:<\/p>\n

1) Am I missing something about new SP1 behavior? Why this change was made? Did anyone have similar problems?<\/p>\n

2) How can I embed manifest with my own version?<\/p>\n

Any suggestions would be appreciated<\/p>\n

Thanks<\/p>\n

Aleks<\/p>\n","protected":false},"excerpt":{"rendered":"

Hi I have unmanaged dll that I created using VS 2005. This dll is used by some managed C# code. \u00a0Prior to installing SP1, when\u00a0building the dll in VS, it was creating manifest that was referencing name=’Microsoft.VC80.CRT’ version=’8.0.50608.0′. After installing SP1 it started to create manifest that is referencing name=”Microsoft.VC80.CRT” version=”8.0.50727.762″. This behavior\u00a0causes breaking change […]<\/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-4044","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/posts\/4044","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=4044"}],"version-history":[{"count":0,"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/posts\/4044\/revisions"}],"wp:attachment":[{"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/media?parent=4044"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/categories?post=4044"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/unknownerror.org\/index.php\/wp-json\/wp\/v2\/tags?post=4044"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}