Skip to content

Command-line and/or library plans? #11

Open

Description

@joelsand

Hi there,

Do you have any plans, or hints as to a simple way how, to make this work in a continuous integration environment? Basically, we have several .NET core apps and packages where we'd like to generate TypeScript definition files as part of the build process.

Thanks,
Joel

Activity

  1. nhabuiduc commented on May 12, 2017

    @nhabuiduc
    Owner

    Initially I wanted to create a separate DLL Project for Converting C# -> Typescript, and then VSExtension project can have reference to it, but I got some problem, so in the end I have to put everything to VSExtension Project as of now.

    As a temporary solution, you still can use VSExtension as normal DLL, and invoke programmatically like below: (I checked in the new code with sample console project)

    var cScript = @"class Foo{}";
    
                CSharpToTypescriptConverter csharpToTypescriptConverter = new CSharpToTypescriptConverter();
    
                var typescript = csharpToTypescriptConverter.ConvertToTypescript(cScript, new MySettingStore());
    

    So for CI, I think you can create your own app, and convert which every file you want.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions