{"action":"created","issue":{"url":"https://api.github.com/repos/Excel-DNA/ExcelDna/issues/59","repository_url":"https://api.github.com/repos/Excel-DNA/ExcelDna","labels_url":"https://api.github.com/repos/Excel-DNA/ExcelDna/issues/59/labels{/name}","comments_url":"https://api.github.com/repos/Excel-DNA/ExcelDna/issues/59/comments","events_url":"https://api.github.com/repos/Excel-DNA/ExcelDna/issues/59/events","html_url":"https://github.com/Excel-DNA/ExcelDna/issues/59","id":132070951,"number":59,"title":"Framework update 4.6.1 and Excel DNA","user":{"login":"zmohamedfakier","id":17119105,"avatar_url":"https://avatars.githubusercontent.com/u/17119105?v=3","gravatar_id":"","url":"https://api.github.com/users/zmohamedfakier","html_url":"https://github.com/zmohamedfakier","followers_url":"https://api.github.com/users/zmohamedfakier/followers","following_url":"https://api.github.com/users/zmohamedfakier/following{/other_user}","gists_url":"https://api.github.com/users/zmohamedfakier/gists{/gist_id}","starred_url":"https://api.github.com/users/zmohamedfakier/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zmohamedfakier/subscriptions","organizations_url":"https://api.github.com/users/zmohamedfakier/orgs","repos_url":"https://api.github.com/users/zmohamedfakier/repos","events_url":"https://api.github.com/users/zmohamedfakier/events{/privacy}","received_events_url":"https://api.github.com/users/zmohamedfakier/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2016-02-08T07:26:03Z","updated_at":"2016-02-08T12:03:00Z","closed_at":"2016-02-08T12:03:00Z","body":"Hi Govert,\r\n\r\nWe have been using ExcelDNA for a while now and it has been working brilliantly. Microsoft released the Framework update 4.6.1, and now 64bit Excel with ExcelDNA does not work. The sample code returns #num when the function is being executed.\r\n\r\nOur code - which is slightly modified crashes excel and the exception is occurring in the CLR (using windbg to trace). Uninstalling the 4.6.1 update does not fix the issue. A complete uninstall of Framework 4.0 and subsequent re-install of 4.5.2 fixes it.\r\n\r\nI am certain that ExcelDNA is not the culprit but that Microsoft update is. Any advice on how to pursue to get a fix?"},"comment":{"url":"https://api.github.com/repos/Excel-DNA/ExcelDna/issues/comments/181336872","html_url":"https://github.com/Excel-DNA/ExcelDna/issues/59#issuecomment-181336872","issue_url":"https://api.github.com/repos/Excel-DNA/ExcelDna/issues/59","id":181336872,"user":{"login":"zmohamedfakier","id":17119105,"avatar_url":"https://avatars.githubusercontent.com/u/17119105?v=3","gravatar_id":"","url":"https://api.github.com/users/zmohamedfakier","html_url":"https://github.com/zmohamedfakier","followers_url":"https://api.github.com/users/zmohamedfakier/followers","following_url":"https://api.github.com/users/zmohamedfakier/following{/other_user}","gists_url":"https://api.github.com/users/zmohamedfakier/gists{/gist_id}","starred_url":"https://api.github.com/users/zmohamedfakier/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zmohamedfakier/subscriptions","organizations_url":"https://api.github.com/users/zmohamedfakier/orgs","repos_url":"https://api.github.com/users/zmohamedfakier/repos","events_url":"https://api.github.com/users/zmohamedfakier/events{/privacy}","received_events_url":"https://api.github.com/users/zmohamedfakier/received_events","type":"User","site_admin":false},"created_at":"2016-02-08T12:03:00Z","updated_at":"2016-02-08T12:03:00Z","body":"The issues of functions returning #NUM only happens when debugging. In release the function works correctly. I downloaded the zip file and compiled and ran (in debug) and thought something was wrong when I saw #NUM. This incorrectly led me to believe something was wrong with DNA interacting with framework 4.6.1. ie. This behaviour (while not nice for someone playing with DNA for the first time on 64bit excel) is not related to my issue.\r\n\r\nAs for my issue, I have isolated the issue to our code changes. We modified the CreateMethodDelegate() function to bypass execution when Excels function wizard or find/replace dialogs are open. This helps performance when our Analysts have sheets with thousands of calls. The previous IL code worked fine - up until the update.\r\n\r\nThanks for the quick responses. This can be closed.\r\n\r\n"}}