Jean-Sebastien Carle
Jean-Sebastien Carle
@WojciechNagorski At the [homepage](https://github.com/sshnet/SSH.NET) of the repository, in the about section, in the gear , it would be useful to check this:
In my personal opinion, I believe that trying to introduce Task within the existing code base will be quite a challenge as you'll face a lot of collision. The repo...
I think there'd be a lot of benefit in starting a new repository and separating things into various smaller projects, sort of the way that Microsoft divides things into a...
We could also use it as an opportunity to support only .NET 6+ (or even .NET 8+) thus splitting this project into a legacy code base and a modern one.
> I think it looks good as a proof of concept. On a high level: > > * I think we should try to make it work for all frameworks...
I don't really know what would be best. A new repo or a new branch, rewrite or not, I know that if we want to move forward, it'll require breaking...
Perhaps we could add an obsolete or deprecated warning? Or make it opt-in in a very intentional manner? Ideas?
I like that idea, but two things. There are [quirks for testing](https://stackoverflow.com/questions/59267036/unit-testing-appcontext-switches/63110138#63110138) that must be taken into account and there should be a conscious naming convention for all switches that...
I also have the same issue.
Oooh! I have code that I had to hack around to get SSE to work with Hey API, I'll be able to test this out soon. Thanks! 🙏🏻