search

microsoft / vs-pty.net

Fork pseudoterminals in C#
MIT License
49 stars 18 forks source link

NuGet Package? #16

Closed munirusman closed 3 years ago

munirusman commented 4 years ago

Is vs-pty.net published as a NuGet package or a compiled library?

javierdlg commented 3 years ago

It isn't publicly available as a NuGet package as of today, but you can build it as a nuget package by running msbuild \t:pack .\Pty.Net.sln which should compile a nuget package for you.

RHamers commented 10 months ago

Hey. I'm unable to build this. There are missing nuget packages. Could you help me to get the binaries so they can be used and implemented? :) Thank you.

javierdlg commented 10 months ago

@RHamers we've moved this to an internal repository due to some limitations with github repos and our internal pipelines. Regardless, I've uploaded the Pty.Net NuGet to our public preview feed msft_consumption. Simply add that feed as a NuGet source and you can then add the package as a package reference to your project.

You can also manually download it from here: https://dev.azure.com/azure-public/vside/_artifacts/feed/msft_consumption/NuGet/Pty.Net/overview/0.3.94-pre

RHamers commented 10 months ago

Thank you! :) I'll give it a go.

RHamers commented 10 months ago

Hey, I got the Nuget package to work but I'm trying to wrapp my head around on how to use it exactly. When I for example start a bash terminal on widows I get all these ANSI VT100 encoded strings back. What's the best way to deal with this? I would like to use vs-pty to implement an integrated terminal in my application so I basically just need to interface to talk to and pass I/O back and forth. Thx!

RHamers commented 10 months ago

Hey, never mind :) I found this unit test in the package which made things clear :) I do have another followup question though: is there a nice way to send ascii based characters across to the console? Like Enter=0x0D or Ctrl+X=0x18?