Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate code to C# or F# #16

Open
lupino3 opened this issue Aug 14, 2019 · 2 comments
Open

Migrate code to C# or F# #16

lupino3 opened this issue Aug 14, 2019 · 2 comments
Labels
enhancement New feature or request

Comments

@lupino3
Copy link
Member

lupino3 commented Aug 14, 2019

The PowerShell code works, but at this point it might be better to implement the cmdlet in pure C#.

This should buy us some more advantages, as the dotnet tool seems to not support very well the PowerShell sources, treating them more as resources than as source files, and requiring us to write ad-hoc scripts to do the "build" and publishing of the code.

This would also remove the ugly part of the code where we try to find the JSON and JSON Schema DLLs and load assemblies directly from those files.

@lupino3 lupino3 added the enhancement New feature or request label Aug 14, 2019
@lupino3
Copy link
Member Author

lupino3 commented Aug 16, 2019

The other advantage of migrating to C# would be making available the core features in C# and all the .NET language, leaving the PowerShell Cmdlets as shims over a generic .NET library.

@pviotti
Copy link

pviotti commented Aug 18, 2019

Another benefit of this migration could be using CoreRT to build a single binary, which would be easier to deploy.

@lupino3 lupino3 changed the title Migrate code to C# Migrate code to C# or F# Oct 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants