You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
Activity
nhabuiduc commentedon May 12, 2017
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)
So for CI, I think you can create your own app, and convert which every file you want.