As I mentioned in a few other threads, I am working on a .net control replacement for Putty. Doing so should resolve a good chunk of the bugs and features posted in the forum. I had a few false starts trying to use a vanilla copy of Poderosa from CVS. Those unfamiliar with the project, it is an open source mutli pane SSH client. The lastest version is difficult to work with due to everything being modularized (having a majority of the comments in Japanese doesn't help either). So to the sake of time and my sanity, I am using http://www.codeproject.com/KB/IP/Terminal_Control_Project.aspx, the project I took/shamelessly stole the inspiration from, as a base. The developer did an excellent job of making a easy to use SSH Terminal Emulator control but unfortunately limited its capability. I have been rewriting the control to be able to easily access functions like unicode terminals, different log on methods, and screen colors. So far I am able to connect to a simple SSH2 client (my router) without Putty in mRemoteNG and have multiple sessions. Currently the minimum requirement is .net 2.0. But there is a lot more I need to complete:

To Do

Correct error in the Poderosa base to correctly terminate a connection. Somewhere there is a System.ObjectDisposedException error being generated

Inplement the remaining build in protocols Telnet,Serial,SSH1,Cygwin and Socks. SSH clients will have their public keys stored in the connection conf instead of in the registrty (true portability)

Write protocol specs for rlogin and raw connections. If removing Putty, I don't want to remove any functionality. Should not be too hard; these are similar to telnet.

Have connections for SCP and SFTP. SCP I believe is buried in there somewhere already. This will remove the SharpSSH and Mentalist/DiffieHellman libraries.

As the terminal isdiffectly accessible, scripts and snippets can be added. A very basic UI editor in mRemoteNG will need to be added.

Update the connection settings for all of the added options. This will also require additions to the connection conf.

Testing, testing, testing and maybe some more testing. This is a major change with a number of points for bugs. Putty is a solid piece of software used the world over; I am faking my way through the c# because its like the bastard child of VB.net and Java. Before release to users who depend of a SSH client for their work and livelihoods, I want to make sure it is as stable as it possibly.

This seems like a tall order, but a majority of it was completed in Poderosa and just needs to be given an interface to it. I will keep hacking way at this and give updates when they come about. Any developers who are curious on how it is coming along, I have the current code checked in to the github https://github.com/Thrilleratplay/TerminalControl.

Replacement for PuTTY -Status

I made a few updates. A majority of what I did was cleaning up formatting by adding an interface and internal base class for connections, added event hooks for connection and disconnection to the form control level, fixed the System.ObjectDisposedException .net warning. For non programmers, its all boring stuff. But at this point I think I can start added in other protocols.

I probably should give an update on what I have been working on. I started to run into issues with trying to implement the raw and rlogin protocols due to the structure of everything. The more I looked into it, the more I saw I would have to alter. It is just not worth the effort. The project referenced originally was a modification of Poderosa v3 from 2005. In 6 years there have been a number of changes in OS and hardware that may result in bugs and creep up later on. Poderosa v4 is active once again and bugs are being fixed. Bugs that deal with response time and 64bit processors. There are also a number of features added like support for other Asian languages, port forwarding and Raw protocol. The problem is that developer who took over the project basically rewrote the program to be well structured plug-ins interacting with each other. Leaving the work I have to be semi useless. I have been going through the latest versions (It is updated almost daily at the moment) seeing where I can make very small and very precise alterations to the project. The hope is to be able to update as needed in the future without needing to devote so much time to it. My time should be more focused on mRemoteNG as a whole. There is also the possibility the developer likes the idea and it becomes part of the project. I am not sure how long this will take, so please bear with me and stay tuned.

always nice to hear that you are still on this. I have finally a working setup in a vm so that I am able to compile mremote (works not under windows 7).I really interessted to get the sql server function working and give it more features. As my company is mostly using oracle and I have some expierience in oracle SQL I wanted to port the MS SQL Script the oracle syntax. When I had a look on the script I saw that the database is note really well designed. Its mostly looking like the confcons.xml translated into tables. Nothing about relations and so on...So I will try to set up a little better database model. As I have no much expirience in vb.net it would be nice if I had somebody who I could ask some dummy questions. But perhaps this is easier by using a more instant communication channel ?

With the limited number of people and the timezone difference between everybody, I think a irc chatroom maybe premature as there would be at most one person in there at a time. But I do agree there needs to be better lines of communication between everyone. Also better methods to handle handle questions, bugs and feature request. Github has a bug tracker but it doesn't seem to have something that handles feature request. If you look at Google code projects, they are part of the same tracker. So a feature request may have priority over a bug. When I first start reading through the forums a few weeks ago, I had no way to tell if a question or issue was still active. I stepped up as interim project manager as no one else felt they had the experience (neither do I, but I'm willing to learn to ensure this project doesn't die). I have really only been developing during this time. The idea I had was, once PuTTY has been replaced thus satisfying half of the bugs and feature request, I was going to send an message to everyone to try to gather more support. New features=new enthusiasm. (bear with me here and try to not to roll your eyes) I was going to post a request for a mRemoteNG equivalent of Oceans 11. To give this project a shot in the arm, it will need a variety of people to do different tasks. The obvious roles are developers, testers and documentation writers. Other roles would be someone to redesign and maintain the website so it is more inviting (maybe a wiki so users can write how-to's or list programs known to work/not work with external applications), someone to monitor the forum (remove spam, answer basic questions that documentation didn't help with/tell them to RTFM and escalate possible bugs and issues), and a saleman (post to forums with users frustrated with remote sotware X with the joys of mRemoteNG and I think we should have an entry here en.wikipedia.org/wiki/Comparison_of_remote_desktop_software). Sorry for the rambling. This just what I had in mind.

Good news. I finally have something that should meet my ridiculously high standards. I started a new project repository on github called PoderosaDotNet. Using the latest version of the Poderosa source and not a six year old version, I have been able to create SSH2 connections added to forms in a different project. Only two of the original source files had to be altered and a new c# project l created to accomplish this. So keeping this up to date will the latest features and bug fixes should be relatively easy. The reaction time is also significantly faster. I am still working on how to structure everything, so don't mind to much to the current version. Don't get too excited, there are still a number of things that need to tested an implemented.

For anyone following this thread and did not notice other posts I made, this component has been put on the back burner for the time being to deal with a major issue with the VNC library. What I thought was going to be a quick fix uncovered a year old bug that is taking far longer than expected to track down and correct. Sorry to anyone waiting for this to be implemented. I am eager to get back to it but at the moment it will have to wait.