Replies: 1 comment
-
|
It's not currently. However, in 2026, I'm going to make a NuGet package for the agent services so they can be injected into another .NET app/agent. At that point, it would technically be possible to have Remotely's agent connect to both Remotely and ControlR's backend. That said, I also want to achieve feature parity with Remotely (plus a lot more stuff), and I'll be working on filling in the gaps throughout the year. Priorities will depend on user feedback. I've been working on a roadmap and intend to post it before the end of the month, along with some other overdue announcements. Hopefully others will be excited about them as I am! (I'm honestly quite a bit nervous about it too. 😬) Once I get those posted, I'd love to get your feedback on them! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello
I'd say compatible or 'roughly compatible'.
I am mildly interested in adapting the code to have a client on an (unsupported but near of a supported) operating system, and wonder if it could serve both with ControlR and Remotely servers - a few ifdef or something like that would not be a problem, however 2 complete different clients to manage would be, well, 2 times the hassle :-). Thanks in advance for any advice.
Beta Was this translation helpful? Give feedback.
All reactions