Many improvements across the board since the October, 2010 installers which were the first with full SharePoint Web Part generation support.
Flynet Viewer Studio now requires the Serial Number/Access Code to be properly coded for use of the Web Service, Enhanced UI and SharePoint Web Part features. An administrative error may have created keys for customers that do not match your purchase. As long as you are on active maintenance, you can contact your Flynet vendor for an updated key. Any customers with Enhanced UI and SharePoint Web Part features should request an updated key prior to installation in order to access those features seamlessly following setup. Following installation of this release, the Help/About dialog will provide the features available with your key.
Updating Flynet Viewer Studio using the setup linked in this post will now run a standard upgrade (the Repair option dialog will no longer be presented unless you are running the same setup twice or more times).
One major enhancement for developers is the addition of the new Visual Studio context menu item on Task Project and Task entities in the Task Treeview. The Visual Studio options include convenient loading of Visual Studio to edit generated solutions (UI, Web Service and the Web Service Unit test GUI). Even more useful is the ability to find all changes that have matching Custom Code Properties in the FV Studio project, so that with a few mouse clicks, any changes made to the generated code can be captured so that any subsequent code generation will include the user changes.
Flynet Viewer Base Product and Components
FlyServer Emulation Service (FlyServer.exe version 5.0.16)
- 3270 protocol tweak to accomodate rare modified field attribute combination
- Improved 3270 clear screen detection for rare buffers that previously set the write flag
- Support added for 3270 Line Feed command not documented for 3270 display (only printer) but used by some 3270 optimization products
- 5250 Screen Save/Restore buffer was not cleaned-up consistently on close of a session
Recorder 2.0 and Terminal Emulation Control
- 3270 protocol tweak to accomodate rare modified field attribute combination
- Home key exceptions- pressing Home Key without re-mapping the key caused an exception in the recorder or terminal emulator (fixed).
- The internal Home Key function (position cursor to first field on 5250 or 3270 display) could not be mapped by the user (fixed).
- The SimHost.exe can now be loaded from a command line and run as an independent process from the service, with a unique Telnet listener port and script. This allows a single PC or server to host multiple test environments representing multiple simulated hosts.�The parameters are simple: SimHost -start ScriptName port
Example: SimHost -start “c:program filesflynetviewersimhostscriptsmyscript.sms” 24
ViewerLib.dll and ViewerLib4.dll Assemblies
- Screen recognition for ClearScreen better managed when potential for multiple definitions in a process (multiple Flynet ASP.NET applications running in then same IIS Application Pool…while you should keep your apps in separate pools, if you insist on one pool, your Clear screens won’t interfere with each other anymore)
- GenMapToXML and GenMapToJSON were not properly representing right-justified attributes
ViewerLibPool.dll and ViewerLibPool4.dll Assemblies
- Version number change caused some updates to require recompile, new installer includes both old and new versions to enable server upgrade without need for recompile
- This installer fixes a number of misconfigured ViewerLibPool issues with x64 as well as Framework 4.0 projects.
FVTerm Web Terminal Emulation Feature
- External Logging Extensions enhanced to support more events, including the terminal session close event and additional information, to allow logging of usage by terminal emulator users by time of connection.
- Updated CSS for better FireFox, Chrome and Safari user experience for when the mouse is hovered over a clickable element (added cursor:pointer where it was only cursor:hand, the old IE style).
- Multi-line fields were not always having the length properly calculated
Flynet Viewer Studio (Build: 220.127.116.11)
Flynet Studio IDE
- Graphical logic viewer could fail if timestamp was in localized format
- Initialization now ensures that the main FV Studio window is visible in cases where it may have been run on a right-side monitor that is no longer connected–the active Windows physical geometry is checked to ensure that the personalization options for window size and location do not result in a “missing Flynet Studio!”.
- Certain .NET Framework environments would prevent proper dynamic loading of the extension assemblies if a Flynet Solution or Project file was loaded by double-clicking on the file in Windows Explorer instead of loading from the initial FV Studio dialog.
- If the Flynet Studio solution or project file was readonly due to source library check-in status, the save would cause an exception–this situation will now display a message box regarding the readonly status of the target file.
- The active license key is now utilized for controlling availability of the Web Service definition and generation, Enhanced UI as well as SharePoint web part definition and generation. Each feature is separately licensed and customers should note that prior to May of 2011, legacy Studio keys will only provide Web Service generation as a default. For customers on active maintenance contracts, please contact your Flynet representitive to receive an updated Flynet Studio keys containing the options you have purchased.
- Fixed bug with displayed item name in the Tasks Treeview, when changes made to properties (wrong change would be displayed in treeview)
- Fixed bug with field deletes when a field was not valid for deleting
- Fixed bug with mouse-click in screen area when no screen loaded
- Fixed numerous issues with display format on systems with magnified display settings
Screen Mapping Wizard
- Improved management of field changes detected in recordings to prevent extra fields from being created from a definition area. Improved differentiation between fixed screen types (3270/5250) and interactive (VTxxx) to improve accuracy and differentiation between labels and data fields.
- Worked on improving visual controls when a user has a screen with magnification activated (such as a laptop with extremely his resolution in a small screen making standard font sizes too small for comfortable reading).
- Added ability to control the stripping of the ending colon on a label, so that user can choose to keep the colon or stripping it when converting to a web page layout.
- Added option to control how cursor landing detection across all recordings is used in a VTxxx environment to detect where entry fields start.
- Fixed a number of issues related to “beginner” mouse use of the unique Screen Mapper environment…
Web Service Generation
- Added IncludeDataSetCreation property to Task object, which is now defaulted false. The DataSet static method to create a DataSet from the active return Info class object is rarely used and was interfering with isolated enhancement of the returned Info class in a Task’s .cs source module.
- Added WebServiceDescription property to the TaskModule object in the Tasks Treeview–allows customized Web Service descriptions to be managed in Flynet Studio and generated into the ASMX.cs file for the web service.
- The TaskScreen.NextStateOverride property was incorrectly visible for a UI composite screen, Notebook or other extended display composition.
- Selected Visual Studio version will now be saved and restored for users of the Task Unit Tester GUI (in the past, it defaulted to Visual Studio 2008 every time unless only Visual Studio 2005 was installed).
- When clearing a previously generated Task Unit Test GUI folder during generation, any parameter values stored in the default parameters xml file that were previously entered during a test will be preserved so that the previously entered values are not lost during a folder clear action.
- Fixed a bug in the GUI Unit Tester generation for Web Service tasks that are defined in a UI Project instead of a Web Services project, as some methods were generated that were only valid in a UI project and caused compile errors as a result.
- GUI Unit tester could throw exception if Monitor event was to be logged and no session was active.
- Tuned use of the OK Screen logic in Task navigation–so that rather than selecting navigation on the first screen in the OK list, navigation is based on the next TaskScreen defined in the task, as it should be. Some OKScreen lists were producing incorrect navigation code.
- Added Visual Studio context menu item to Task objects, so that a Task Unit Tester GUI can easily be edited, and any changes to the module quickly and safely imported to the Task Custom Code properties. When finding changes and importing them, a visual display of the changes with an optional WinDiff of an existing custom code property and the active changed file is also available.
- The same Visual Studio options described for the Task object is also available for the TaskProject if a full web service generation has been performed and the Visual Studio Solution files are found in the target folder. When finding changes in a full project, all standard locations for user changes are identified for files that have been modified since they were generated.
- A warning has been added if a user includes a logon-sequence screen in a Task, as this is a beginner error that is common. Any screen that is part of the logon sequence (first screen displayed through to the home screen) should not be part of a task unless it is something like the clear screen, which can appear in multiple flows.
- Duplication of screen identifiers was occuring in navigation in task NextScreen commands (same screenID appears more than once in wait list)
- If a recording had a default screen in it, sometimes the default screen (unrecognized) would be included in a NextScreen command as part of task navigation.
- Warning on inclusion of a TaskScreen with no resulting code generated (for example, navigation-only for a screen that is the only OK screen in prior TaskScreen).
- Some Auto-Logon and Pooled Session Multi-Part tasks were not generating correctly
Enhanced UI Solution Generation
- The same Visual Studio options described for the TaskProject object have been implemented for the Enhanced UIProject object.
- Web Page Preview had some compile errors for some screens, as the “cursorOffset” member was not defined in the preview mock HostScreen class, and a few other members were not defined in the mocked MappedList class.
- Web Page Preview improved for VTxxx applications so that the mock screen image is better represented in the page.
- Better support for SharePoint generation detection, as some of the options from SharePoint were causing regressions in non-SharePoint UI solutions.
- SharePoint detection of the correct IIS Site when generating for a SharePoint environment, but only will work smoothly with the default name of “SharePoint – 80”.
Code Generation: All Project Types
- If the relatively new IOHelper project generation option was selected, in Sharepoint generated web.config files, an empty reference node was generated in the XML causing a runtime validation error.
- Both Wizards tweaked to provide better usability on systems with screen magnification active.
- Pooled session support was at times generated incorrectly depending on the type of Task project and active options
- Fixed bug in backup logic for existing projects, in some cases a merge message was issued when no merge was actually required.
- Custom Code Properties can now have the #region and #endregion tags included without breaking generation (prior builds would end-up with duplicate tags in some files
- Navigation improved so that if the session landed at any logon sequence screen, the original credentials used to logon can still be used to navigate back into the application
- Code Merge .bat file for calling WinMerge fixed for x64 platforms so that the WinMerge exe is found in the c:program files (x86) path instead of standard Program files (WinMerge is 32 bit only).
- Navigation generation for VTxxx systems improved further to support queued field-level entries consistently across more types of screen layouts and field combinations, with the Field-Level data entry option fully implemented from Project to Screen to Field for control through properties.
- Logon logic more consistent at catching and reporting failed logon…prior builds would report an exception that was not clear as to the cause.
- Some combinations of navigation could result in a runtime exception for generated applications due to a null entry in the IOBag object (fixed)