mRemoteNC - fork of mRemoteNG

[Exaktus]

[CKCobra]

Funny, I just did the same thing . C# port and all too. I haven't put mine on git yet. Maybe I'll take a look at yours and contribute instead.

[Exaktus]

[rmcardle]

You guys should talk to . He has expressed interest in organizing the mRemoteNG project going forward. I would hate to see the community split and it seems like there's already been a lot of duplication of work.

I would urge you to focus on bug fixes rather than adding features. I would also urge you to think very carefully about the switch to C#. I'm not a huge fan of VB, but the differences between it and C# are really only skin deep. Is it really worth the effort to convert it? Worth dealing with bugs caused by the conversion? Worth splitting the already extremely limited pool of people who are willing to work on this project in two? Worth duplicating effort implementing fixes made to NG in NC and vise-versa?

That said, if you are really intent on continuing along this line, I would like to offer to host your project alongside mRemoteNG. Much of the work of forking mRemote into mRemoteNG was getting this infrastructure set up--website, forum, JIRA, wiki, Crowdin, etc.

[DVT_Sogh]

I agree with , create a new project with the same functionality just because it is compiled in C # will increase the work for little changes.

I understand the value of adding missing features (and some would help me a lot), but the stabilization of the current function code is a plus.

I am not against the idea of ​​compiling the project in another language, but the dispersion of resources may slow the current project and move slowly your solution. If you gather under the same banner, you'd be 4 to work together (see 5 with me, but I'm not a developer) :
-
-
-
-
-

Sincerely,

PS: I am French and my English is not necessarily the best

[rmcardle]

Well, thanks to my (now former) boss, I have a lot more free time. I hope to start working on mRemoteNG more now.

[CKCobra]

I'm sorry to hear that.

I agree that fixes and stabilizing should be looked at first before new features. The port I started was a straight 1.70 beta port to C#. I didn't add any new features yet. I was planning to look at the reported bugs first. Since it appears that dev is still on going I understand if you choose to stick with VB. I started my port because it appeared that it was abandon and I know C# better than VB.

[Exaktus]

[squires]

[DVT_Sogh]