mRemoteNC - fork of mRemoteNG

[Exaktus]

[Exaktus]

So, leave everything as is?

[rmcardle]

[jp.mrqs]

[rmcardle]

There's nothing I can do to stop you guys other than to strongly discourage you from splitting off. There's no going back. Any bug fixes or new features made in either codebase will be extremely difficult to merge back into the other.

[Exaktus]

[alphadog]

Exaktus, I just had to say love that you have ported this, it will make the replacement of putty and the additions of protocols much easier i believe.
I am watching your Port and think you will find a lot of support for this.

[ravensorb]

Is this still active? From the git repository it looks like there have been no changes in 3+ months. Maybe we could combine the two by starting to break out mRemoteNG into various class libraries (seperated from the main UI application) and then look at leveraging IOC to create more of a modular/extensible app that others could contribute to?

[alphadog]

They made an update the other day but a friend has show me another project that is been going a while and has all the same features (Was a port from mremote original as well)
its :
Open Source
written in C#
Has lots of extra features
Oh did I mention it has integrated SSH so putty is no longer required

Its over on codeplex its called Terminals

The page is

I Am now looking at stopping working on mine and working on this instead.

Have a look, I think it the way to go

[ravensorb]

Terminals is definitely an option (and an active one at that) however I am not a big fan of it's UI and how it organizes connections -- in that respect mRemoteNG is fare easier to work with (at least in my perspective).