Title: Future of Add-Type · Issue #5725 · PowerShell/PowerShell · GitHub
Open Graph Title: Future of Add-Type · Issue #5725 · PowerShell/PowerShell
X Title: Future of Add-Type · Issue #5725 · PowerShell/PowerShell
Description: Current version of Add-Type cmdlet is partially ported on Roslyn from Dom. It is large breaking change. It is true for most of the parameters. Some parameters was related to Dom and was removed. Some parameters don't implemented. In fact...
Open Graph Description: Current version of Add-Type cmdlet is partially ported on Roslyn from Dom. It is large breaking change. It is true for most of the parameters. Some parameters was related to Dom and was removed. So...
X Description: Current version of Add-Type cmdlet is partially ported on Roslyn from Dom. It is large breaking change. It is true for most of the parameters. Some parameters was related to Dom and was removed. So...
Opengraph URL: https://github.com/PowerShell/PowerShell/issues/5725
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Future of Add-Type ","articleBody":"Current version of Add-Type cmdlet is _partially_ ported on Roslyn from Dom. It is large breaking change. It is true for most of the parameters. Some parameters was related to Dom and was removed. Some parameters don't implemented. _In fact, we already have a new cmdlet._\r\nBefore I push new enhancements I want discuss a few points. We could remove old things.\r\n\r\n - [public enum `Language`](https://github.com/PowerShell/PowerShell/blob/master/src/Microsoft.PowerShell.Commands.Utility/commands/utility/AddType.cs#L33)\r\nShould we keep JScript for backward compatibility?\r\nShould we add FSharp for future?\r\nShould we keep CSharpVersion1, CSharpVersion2 and so on? If yes should we add VisualBasicVersion9 and so on? Could we leave only CSharp and VisualBasic in the enum? Why anybody can want to use CSharpVersion1 in PowerShell?! I found nothing on GitHub - I think we should old elements.\r\nCurrently I have to add language family type with CSharp and VisualBasic internally. So I'd prefer simplify `public enum Language` and don't use the new type and helper functions to translate these types.\r\n- Roslyn can accept parsing and compile options. It is _different types_ for every language (currently CSharp and VusualBasic). Some options (not all) can be useful for Add-Type (language version, preprocessor variables). \r\nHow we can better expose the options? Generic or by language? The question related with previous one - with options we can specify the language version. We could Roslyn generic classes but they are not convenient to work in PowerShell. I have no conclusion.\r\n- Should we support creation new assembly without loading? Currently we always load created assembly, even with `-Passthrou`. I think we could add `-CompileOnly` switch.\r\n\r\n/cc @SteveL-MSFT @daxian-dbw \r\n\r\n ","author":{"url":"https://github.com/iSazonov","@type":"Person","name":"iSazonov"},"datePublished":"2017-12-20T18:23:36.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":10},"url":"https://github.com/5725/PowerShell/issues/5725"}
| 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:a2a0a013-b509-8335-2de4-805119a17657 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | E55A:2AE5C2:2DA4593:41BEDF4:6A5520BB |
| html-safe-nonce | 173ddf19644753d374991c8f307d72e7016fc2b3e05f8fe16a066c70b7bb9da8 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJFNTVBOjJBRTVDMjoyREE0NTkzOjQxQkVERjQ6NkE1NTIwQkIiLCJ2aXNpdG9yX2lkIjoiNzU0MzY2NjUzNzQxMDE0MjM5NSIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 4c8523909eeed3084743cbf452ea28759145e3cf5bf1da64b66c83f4da400b70 |
| hovercard-subject-tag | issue:283653938 |
| 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/5725/issue_layout |
| twitter:image | https://opengraph.githubassets.com/45a5eda045eb92cbc9761975ec41ca1539bb9f1255155f4fb0668ae6d1005c95/PowerShell/PowerShell/issues/5725 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/45a5eda045eb92cbc9761975ec41ca1539bb9f1255155f4fb0668ae6d1005c95/PowerShell/PowerShell/issues/5725 |
| og:image:alt | Current version of Add-Type cmdlet is partially ported on Roslyn from Dom. It is large breaking change. It is true for most of the parameters. Some parameters was related to Dom and was removed. So... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | iSazonov |
| hostname | github.com |
| expected-hostname | github.com |
| None | 682d273eacb2ac51680c6eb9c0b270f029f7ce74c32090f319083c34497e28a5 |
| 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 | 358dd24ad7465d20e3fae729b5b169d35b0dd7f8 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width