Title: Is there a way to avert the diamond dependency problem for modules that use .Net types? · Issue #5504 · PowerShell/PowerShell · GitHub
Open Graph Title: Is there a way to avert the diamond dependency problem for modules that use .Net types? · Issue #5504 · PowerShell/PowerShell
X Title: Is there a way to avert the diamond dependency problem for modules that use .Net types? · Issue #5504 · PowerShell/PowerShell
Description: It seems like certain things can only be defined once per PowerShell session. Public enums named in calls to Add-Type are one such example. In the repro below, a .Net enum of a particular name could only be defined once even though the t...
Open Graph Description: It seems like certain things can only be defined once per PowerShell session. Public enums named in calls to Add-Type are one such example. In the repro below, a .Net enum of a particular name coul...
X Description: It seems like certain things can only be defined once per PowerShell session. Public enums named in calls to Add-Type are one such example. In the repro below, a .Net enum of a particular name coul...
Opengraph URL: https://github.com/PowerShell/PowerShell/issues/5504
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Is there a way to avert the diamond dependency problem for modules that use .Net types?","articleBody":"It seems like certain things can only be defined once per PowerShell session. Public enums named in calls to `Add-Type` are one such example. In the repro below, a .Net enum of a particular name could only be defined once even though the two definitions are in separate modules. Working around such naming collisions amongst unrelated modules is usually a one-time event. However, the same problem manifests when more than one version of the same module is required to exist in a single session. This occurs every time a .Net type in a low-level module changes and the mid-level modules aren't updated simultaneously. I've been running into this problem in PowerShell with increasing frequency as I incorporate more third-party libraries and as my code has become more modular. \r\n\r\nAs far as I've read this problem is called \"the diamond dependency problem\" ([video](https://www.youtube.com/watch?v=tISy7EJQPzI&feature=youtu.be&t=15m0s)). The repro below demonstrates the canonical scenario described in the video in PowerShell.\r\n\r\nThere seems to be some signs that C# projects can load multiple versions of the same assembly thereby averting the diamond dependency problem (e.g. [stackoverflow question](https://stackoverflow.com/questions/4451220/loading-multiple-versions-of-the-same-assembly)). Is there a similar strategy that works in PowerShell?\r\n\r\nSteps to reproduce\r\n------------------\r\n\r\n```powershell\r\nNew-Module libutil_v1 {\r\n Add-Type -TypeDefinition 'public enum E {a,b,c}'\r\n function f {\r\n param\r\n ( \r\n [e]\r\n $E\r\n )\r\n }\r\n} | Import-Module\r\n\r\nNew-Module libutil_v2 {\r\n Add-Type -TypeDefinition 'public enum E {a,b,c,d}'\r\n function f {\r\n param\r\n ( \r\n [e]\r\n $E\r\n )\r\n }\r\n} | Import-Module\r\n\r\nNew-Module liba {\r\n Get-Module libutil_v1 | Import-Module\r\n\r\n function g_a {\r\n f -E c\r\n }\r\n} | Import-Module\r\n\r\nNew-Module libb {\r\n Get-Module libutil_v2 | Import-Module\r\n\r\n function g_b {\r\n f -E d\r\n }\r\n} | Import-Module\r\n\r\n\r\ng_a\r\ng_b\r\n```\r\n\r\nExpected behavior\r\n-----------------\r\n\r\nNo exception thrown.\r\n\r\nActual behavior\r\n---------------\r\n\r\n```none\r\nAdd-Type : Cannot add type. The type name 'E' already exists.\r\nAt C:\\users\\un1\\Desktop\\test.ps1:13 char:5\r\n+ Add-Type -TypeDefinition 'public enum E {a,b,c,d}'\r\n+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r\n + CategoryInfo : InvalidOperation: (E:String) [Add-Type], Excepti\r\n on\r\n + FullyQualifiedErrorId : TYPE_ALREADY_EXISTS,Microsoft.PowerShell.Command\r\n s.AddTypeCommand\r\n\r\nf : Cannot process argument transformation on parameter 'E'. Cannot convert\r\nvalue \"d\" to type \"E\". Error: \"Unable to match the identifier name d to a\r\nvalid enumerator name. Specify one of the following enumerator names and try\r\nagain:\r\na, b, c\"\r\nAt C:\\users\\un1\\Desktop\\test.ps1:35 char:14\r\n+ f -E d\r\n+ ~\r\n + CategoryInfo : InvalidData: (:) [f], ParameterBindingArgumentTr\r\n ansformationException\r\n + FullyQualifiedErrorId : ParameterArgumentTransformationError,f\r\n```\r\n\r\nEnvironment data\r\n----------------\r\n\r\n\u003c!-- provide the output of $PSVersionTable -->\r\n\r\n```powershell\r\n> $PSVersionTable\r\n\r\nName Value \r\n---- ----- \r\nPSVersion 6.0.0-beta.8 \r\nPSEdition Core \r\nGitCommitId v6.0.0-beta.8 \r\nOS Microsoft Windows 6.3.9600 \r\nPlatform Win32NT \r\nPSCompatibleVersions {1.0, 2.0, 3.0, 4.0...} \r\nPSRemotingProtocolVersion 2.3 \r\nSerializationVersion 1.1.0.1 \r\nWSManStackVersion 3.0 \r\n```\r\n","author":{"url":"https://github.com/alx9r","@type":"Person","name":"alx9r"},"datePublished":"2017-11-20T01:03:49Z","url":"https://github.com/PowerShell/PowerShell/issues/5504"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:b532a78b-7dc8-965d-b1a9-d270428141d9 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | E2EE:D21F4:14B71D:1D0C2B:6AFD4E58 |
| html-safe-nonce | 0cfa83d8194a186df892eaf9b6f4b960c983c7b6f7edc856b8f49eeaf743e847 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJFMkVFOkQyMUY0OjE0QjcxRDoxRDBDMkI6NkFGRDRFNTgiLCJ2aXNpdG9yX2lkIjoiMTg3MzAzNTg1Mzc2MDkwODg4OCIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | ea3991c9b98db45447369c3e8ccccf5f136a8562872cd8480dd930abfced857b |
| hovercard-subject-tag | issue:275210876 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/PowerShell/PowerShell/5504/issue_layout |
| twitter:image | https://opengraph.githubassets.com/d74e34b622686b55450c1ea587667373f03ec60c648ced07d5696a2383650b35/PowerShell/PowerShell/issues/5504 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/d74e34b622686b55450c1ea587667373f03ec60c648ced07d5696a2383650b35/PowerShell/PowerShell/issues/5504 |
| og:image:alt | It seems like certain things can only be defined once per PowerShell session. Public enums named in calls to Add-Type are one such example. In the repro below, a .Net enum of a particular name coul... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | alx9r |
| hostname | github.com |
| expected-hostname | github.com |
| None | 66653c2e55a6fff2930be1bdf07ee4f8aa137e3956d056c822563be6f878755e |
| turbo-cache-control | no-preview |
| go-import | github.com/PowerShell/PowerShell git https://github.com/PowerShell/PowerShell.git |
| octolytics-dimension-user_id | 11524380 |
| octolytics-dimension-user_login | PowerShell |
| octolytics-dimension-repository_id | 49609581 |
| octolytics-dimension-repository_nwo | PowerShell/PowerShell |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 49609581 |
| octolytics-dimension-repository_network_root_nwo | PowerShell/PowerShell |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | b6f01f7cb9f35f8c09949773241a3d49dd04b340 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width