The name not only sounds “kingly”, it also had a familiar ring. I can’t really recall who suggested Royal TS but as soon as I heard it, I thought it would be perfect. I thought a lot about the name but all I knew was that it’s just a “better” terminal services (TS) client. I felt I could release it to the public as there was literally no tool out there which provided the functionality and user friendly workflow when it came down to RDP-ing into remote machines.
Royal ts numpad not working code#
Looking at the early code now makes me blush…Īfter a couple of weeks, the app was ready to use and mostly stable. In retrospect, Royal TS was purely a learning project for me to get used to C# and the. I’ve done a lot of Perl scripts for automation, so curly braces and a C-like language didn’t really bother me.
Royal ts numpad not working windows#
My programming experience on Windows at the time was mainly VB and I already started to look at VB.NET (which was still very new) but I wanted to dive into C#. After I realized that the ActiveX control offers most switches and allows me to host multiple sessions in an Explorer-like single-window interface, I decided to write my own little app for that. While you could do most stuff with mstsc.exe, I have found it very limiting and not very user friendly to work with multiple sessions at the same time. At the time Microsoft’s client didn’t expose much of the available settings and the MMC lacked something basic like the “Connect to Console” switch. My main motivation to write a tool like this was the poor implementation of Microsoft’s RDP MMC snap-in. I hope you enjoy… Why bothering writing an RDP client? Can you believe that? More than 10 years ago, on October 26th back in 2003, I released the first public version of Royal TS and it looked like this:Īs promised in this blog post, a little background story about the name and the tool itself.
0 kommentar(er)
