Latest update and plans for the future

Announcements, news and other important information about mRemoteNG.

Latest update and plans for the future

Postby dmsparer » Tue Mar 22, 2016 4:49 pm

Hello all,

I figure it's time I made a post about what has been going on and what I have planned for the future. My intention is to have these sorts of posts somewhat often (once or twice a month at least) to give the community a sense of where the project is and where it is going.

  1. I've been working almost daily since announcing my take-over of the project to refactor and decouple the current code base. The current code is so huge and complex that it is suicide to try to get anything done without trying to entangle things. This needs to happen, and for sanity's sake it needs to happen first. The connection/protocol subsystem will be targeted first.
  2. I want to convert the code base to C# and more away from Actually, the conversion has already happened on my personal fork of the code. I used this to better learn the current code base and learn syntax. However, I want to have a dialog with the community before deciding whether to move the official project over to a different language. Disclaimer: the conversion did cause a few bugs, which is to be expected. Most are fixed, though minor GUI bugs still exist.
  3. Update the supported versions of RDP, along with other protocols (VNC is largely broken, and SSH needs some love). There have been numerous protocol updates since the last mRemoteNG (mRNG) update. The refactoring work being done in point #1 (above) is in direct support of this goal. I intend to have sufficient abstract to allow users to choose whichever specific version of RDP (or ssh/vcn/etc) they would like to use. This should help folks on newer systems (Win10, Server 2012) take advantage of the most recent protocols, while not giving up support for the poor souls who must still use Server 2003.
  4. Move away from PuTTY. In support of updating SSH and related command line protocols, the goal is to move away from PuTTY as the default SSH provider in support of SSH.Net. SSH.Net is a native .Net library for managing remote connections which has also recently found a new owner. It has been ported over to GitHub from CodePlex (GitHub repo here: Please note, this does not mean that PuTTY will no longer be supported as an SSH/telnet/RAW/whatever provider. PuTTY will be, at least for now, still be supported as an option for future mRNG versions. The goal with SSH.Net is to not -require- PuTTY.
  5. Credential manager. Yes. If you have to manage more than a single domain of servers, you have likely been frustrated with your username/password management options. The goal is to have a single credential manager within mRNG where username/password pairs are stored. Connections can use a stored credential pair from the manager, or use a manually entered pair (similar to how things work now.) Inheritance will not go away - the credential manager will just be one more way to manage credentials. This feature will provide the groundwork for user-specific credentials when utilizing SQL Server for team-sharing your connections files. This also opens up support for KeePass/PasswordSafe/etc integration. Why save your credentials twice?
  6. Work spaces. Similar to Linux/Mac virtual desktops, the idea is there for virtual work spaces. This will be especially useful for those of your who manage several external customer environments. Load separate connections files (or SQL) into separate work spaces with optionally separate credential management.

Now, some of those items are admittedly a long ways off. I don't want to mislead anyone into thinking this is going to happen quickly. However, I'm excited about working on this project and seeing it grow. I intend to communicate that excitement to you over the next few months as the project picks up speed.
Posts: 91
Joined: Mon Feb 15, 2016 10:42 am

Latest update and plans for the future


Re: Latest update and plans for the future

Postby agiz » Thu Apr 14, 2016 12:26 am

Wow, i really like what i am seeing here!
I love the project for a VERY long time now, and was sad to see it stagnate, but i really like your post above.
I can only support you with kind words and a donation now and then, but i am quite certain there are many that are looking to see a new version in the future :)
Posts: 5
Joined: Thu Apr 14, 2016 12:21 am

Re: Latest update and plans for the future

Postby dmsparer » Thu Apr 14, 2016 1:40 pm

Thanks agiz!

Kind words and occasional donations are very welcomed :)
Posts: 91
Joined: Mon Feb 15, 2016 10:42 am

Re: Latest update and plans for the future

Postby pencoe » Thu Apr 21, 2016 5:46 am

I'm really excited to see that this great piece of software has a new maintainer :-) i wish you all the best!

I would like to give some comments to your goals:
@2: i think you should use the language you are most familiar with: the effort of migrating will definitely pay off later!
@5: i really, really would like to see Keepass integration... A dream would come true :-) . This would eleminate the use of the Keepass pageant plugin :-)
@6: this sounds promising!

Again: i'm very happy to see you here!

Posts: 6
Joined: Mon May 30, 2011 1:53 am

Re: Latest update and plans for the future

Postby DigitalDictator » Fri May 06, 2016 11:08 am

Great news! Good luck and keep the faith!
Posts: 2
Joined: Fri May 06, 2016 10:44 am

Re: Latest update and plans for the future

Postby kennyg » Wed May 18, 2016 12:48 pm

Just started using mRemoteNG today, 2 things i wish it had.
1. multiple ssh session code insertion with multi line scripting
2. commander style sftp(or winscp integration/not its own window)

Good luck
Posts: 1
Joined: Wed May 18, 2016 12:28 pm

Re: Latest update and plans for the future

Postby koumdros » Tue May 24, 2016 1:47 pm

great. I'm glad you are going full speed with this, after checking multiple simialr products, i keep coming back to Remote.

I think the support of multiple protocols , plus the intuitive way the connectins pane works is waht kepe bringing me back.

re the anouncements:
A. Languase wise: ti think the best language would be th one bringing most developers behind it. dont get me wrong i respct your effort, but i also see 3 different projects currently runing to keep the application allive, this more or less signifies the support /need for it.
B. there a re a lot of bugs in the code, including regressions, things that worked in previous version have problems in the latest mRemotNG
we should all help development work by reporting and combing throuth the functionality and UI
C. while a built in SSH support would be ideal, most of us have gotten really comfortable working with putty and it has proven a long tack record of code upgrades and keeping up with security. I hope net.SSH does the same but it is stil a relative new and lightly worked on project.
Posts: 5
Joined: Sat May 04, 2013 2:06 pm

Re: Latest update and plans for the future

Postby Cosebdd » Wed Jun 01, 2016 6:50 am

Glad to see this project back!

I've got a few questions:
  1. Is there some way to contribute? I found no workflow or contact data on github project page.
  2. Will you maintain mRemoteNG package in chocolatey repository? (
Posts: 2
Joined: Wed Jun 01, 2016 5:32 am

Re: Latest update and plans for the future

Postby dmsparer » Wed Jun 01, 2016 8:52 am

1. Contributions page is here: (or were you looking for info on helping in other ways?)
2. Hmm didn't know there was a Chocolatey package for mRemoteNG - I don't think that's maintained by us directly
Posts: 91
Joined: Mon Feb 15, 2016 10:42 am

Re: Latest update and plans for the future

Postby Cosebdd » Wed Jun 01, 2016 9:40 am

I meant code contribution
Posts: 2
Joined: Wed Jun 01, 2016 5:32 am


Return to Announcements

Who is online

Users browsing this forum: No registered users and 1 guest