Version 3.0 final development tests

Topics: Developer Forum, Project Management Forum, User Forum
Mar 15, 2013 at 11:19 PM
Edited May 6, 2013 at 10:20 PM
Hi every body. New version has changed lot in data files manipulations. Specially, there is new passwords encryption implementation. As you can understand, even if we have 41 unit tests some things have to be tested manually. For me everything works.
I tested:
  • upgrade installed version overwritten by new setup
  • upgrade binaries only without setup installation
  • upgrade of credentials, stored favorite passwords and master password
  • files are moved to proper location
  • in case of not "portable version", files are stored in user profile
Hidden build page is already prepared, but i didn't publish binaries yet. All other stuff to test is described there.
Please have a look at the same things on your environment and let me know, so we can publish at least new version beta.
Apr 3, 2013 at 5:13 PM
Any feedback? If nobody confirms, till end of next week i will publish new version, even if we are not sure with the stability. :-)
Apr 4, 2013 at 11:52 AM
Edited Apr 4, 2013 at 11:38 PM
Hi, I just wrote a detailed email and boom, email app crashed.

In short: The v3 install (upgrade from v2) only works for me in portable mode. Memory blew out to 2GB then crashed.

Import favorites with overwrite required restart of terminals (displayed duplicates and program complained).

Stored credential templates were not exported from v2? Maybe I missed something here?

SQL DB build script is not present?

You guys are doing great work! I'm so sick of the old "free" options moving to paid especially when RoyalTS and Devolutions are getting so bloated and confusing that finding and opening a session is quicker with mstsc.exe!

EDIT: Formatting (Paragraphs)
Apr 5, 2013 at 9:37 AM
Edited Apr 5, 2013 at 12:31 PM
Development closed, what i found is fixed.
I am currently testing the setup and based on your remarks and i got you. You don't have master password defined. In this case the upgrade routine fails.
To fix in Setup:
  • Upgrade Logs path pointing to user profile to follow Win7 standards
  • Remove obsolete Launcher application (fix installed icon link)
  • Fix upgrade routine to support upgrade with empty master password
Apr 5, 2013 at 9:38 AM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.
Apr 14, 2013 at 4:20 PM
All collected issues are fixed. Something else to burn down?
Apr 18, 2013 at 9:15 PM
Edited Apr 28, 2013 at 8:12 AM
Known issues:
  • Second day after installation all favorites except very popular "Terminals News" are lost. :-) I promise, that i will remove this Favorite.[DONE]
  • Sometimes application freezes on start, when loading shortcuts [DONE]
  • After upgrade of favorites from version 2.0 assigned credentials from Credential manager are lost [DONE]
  • Credentials columns are empty in Organize favorites form and sort by them throws an exception [DONE]
Apr 23, 2013 at 8:44 AM
After testing the Favorites problem by changing the Date, i get the following error when starting Terminals:
Terminals has encountered a problem and needs to close.
For more details see the log files.

The version I'm using is the latest source compiled (102558).

INFO 2013-04-22 10:33:04,218 421ms Terminals Main - -------------------------------Title: Terminals 3.0.0 started Version: Date:22-4-2013 12:12:16-------------------------------
INFO 2013-04-22 10:33:04,343 546ms Terminals Main - Start state 1 Complete: Unhandled exceptions
INFO 2013-04-22 10:33:04,359 561ms Terminals gGeneralProperties - CommandLine:"C:\Program Files (x86)\Terminals\Terminals.exe"
INFO 2013-04-22 10:33:04,359 561ms Terminals gGeneralProperties - CurrentDirectory:C:\Program Files (x86)\Terminals
INFO 2013-04-22 10:33:04,359 561ms Terminals gGeneralProperties - MachineName:PC
INFO 2013-04-22 10:33:04,359 561ms Terminals gGeneralProperties - OSVersion:Microsoft Windows NT 6.2.9200.0
INFO 2013-04-22 10:33:04,359 561ms Terminals gGeneralProperties - ProcessorCount:2
INFO 2013-04-22 10:33:04,359 561ms Terminals gGeneralProperties - UserInteractive:True
INFO 2013-04-22 10:33:04,359 561ms Terminals gGeneralProperties - Version:4.0.30319.18033
INFO 2013-04-22 10:33:04,359 561ms Terminals gGeneralProperties - WorkingSet:37646336
INFO 2013-04-22 10:33:04,359 561ms Terminals gGeneralProperties - Is64BitOperatingSystem:True
INFO 2013-04-22 10:33:04,359 561ms Terminals gGeneralProperties - Is64BitProcess:True
INFO 2013-04-22 10:33:04,359 561ms Terminals Main - Start state 2 Complete: Log General properties
INFO 2013-04-22 10:33:04,359 561ms Terminals Main - Start state 3 Complete: Set application properties
INFO 2013-04-22 10:33:04,468 670ms Terminals Main - Start state 4 Complete: Parse command line
INFO 2013-04-22 10:33:04,468 670ms Terminals Main - Start state 5 Complete: User account control
INFO 2013-04-22 10:33:04,468 670ms Terminals Main - Start state 6 Complete: Set Single instance mode
INFO 2013-04-22 10:33:04,468 670ms Terminals Main - Start state 7 Complete: Configuration upgrade
INFO 2013-04-22 10:33:04,546 748ms Terminals LoadHistory - Loading History from: C:\Program Files (x86)\Terminals\Data\History.xml
FATAL 2013-04-22 10:33:09,967 6170ms Terminals howApplicationExit - System.NullReferenceException: Object reference not set to an instance of an object.
at Terminals.Data.HistoryByFavorite.AddItemToGroup(SerializableDictionary2 groupedByDate, HistoryItem item) in C:\Users\%username%\Desktop\terminals-102558\Main\Source\Terminals\Data\History\HistoryByFavorite.cs:line 43
at Terminals.Data.HistoryByFavorite.GroupFavoriteKeysByDate(SerializableDictionary
2 groupedByDate) in C:\Users\ADMINISTRATOR\Desktop\terminals-102558\Main\Source\Terminals\Data\History\HistoryByFavorite.cs:line 35
at Terminals.History.ConnectionHistory.GetDateItems(String historyDateKey) in C:\Users\%username%\Desktop\terminals-102558\Main\Source\Terminals\Data\History\ConnectionHistory.cs:line 76
at Terminals.Forms.Controls.HistoryTreeView.RefreshGroupNodes(GroupTreeNode groupNode) in C:\Users\%username%\Desktop\terminals-102558\Main\Source\Terminals\Forms\Controls\HistoryTreeView.cs:line 119
at Terminals.Forms.Controls.HistoryTreeView.ExpandDateGroupNode(GroupTreeNode groupNode) in C:\Users\%username%\Desktop\terminals-102558\Main\Source\Terminals\Forms\Controls\HistoryTreeView.cs:line 111
at System.Windows.Forms.TreeView.TvnExpanded(NMTREEVIEW* nmtv)
at System.Windows.Forms.TreeView.WmNotify(Message& m)
at System.Windows.Forms.TreeView.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
FATAL 2013-04-22 10:33:09,983 6185ms Terminals howApplicationExit - Application has to be terminated.
Apr 24, 2013 at 8:50 PM
Edited Apr 24, 2013 at 8:52 PM
Are you able to reproduce the steps, which result in such exception? From your log i didn't identify any problematic point.
Edit: Aha, it is copied to another discussion. So it is related to the "Tomorrow" issue.
Apr 28, 2013 at 8:13 AM
Again, all collected issues are fixed. Something else to burn down?
Apr 29, 2013 at 4:13 AM
Hi all,

Using v3.0.0.136...

Not trying to cause headaches here but is there a keyboard focus issue with changing tabs (clicking a different active connection tab)?

When I switch between machines using the active tabs, the keyboard does not respond within the newly selected tab but remains in the previous tab until clicking within the RDP session window itself.

This was an odd effect as I was running keyboard commands (Win+R, cmd, ping servername, etc) and nothing happened on screen, then I switched back to the previous tab again and saw all my commands having been run on the original tabbed session!

While I don't expect a quick fix, I am very glad I wasn't rebooting production servers or the like. That could have been a big issue.

Apr 30, 2013 at 7:13 PM
@mickregan: does it appear only in the new version, or is it related also to the current version 2.0?
Apr 30, 2013 at 10:18 PM
From memory I did notice a few occasions with v2.0 where input wasn't working at first, it may have been the issue with focus but I can't be certain.
May 13, 2013 at 5:30 PM
New call for current development review. I fixed most issues i know on Beta 2. Can it be the last beta?
May 13, 2013 at 8:46 PM
Maybe you could take a look at workitem/34048?
Jun 14, 2013 at 2:46 PM
I am going to fix last issue in the DB persistence and lets publish the release.
I am not satisfied with the stability, but anyway it is better than before.