Flynet Studio Code Generation Properties

UserClassCode - Custom Code

UserClassCode - Custom Code

Previous topic Next topic  

UserClassCode - Custom Code

Previous topic Next topic  

Contains the complete user class module for the base Task class for the project.  The user class is used for any overrides in the base class that may affect all tasks.  Most commonly would be navigation methods, such as 'NavFromSCREENX' when a screen needs custom navigation.

 

The Custom Code properties are special code-oriented string properties with a dedicated editor and the capability for import/export functionality between the Tester GUI generations and the full application generation.

 

Since many quirks of systems, including specific screen-to-screen navigation can benefit from customization, it is important to implement commonly across all testing modules as well as the full web service solution.  The UserClassCode property enables these to be shared without getting into complex inter-project references.

 

Once the UserClassCode is non-empty, it will always be used to generated the user task module, so do not make any further changes to the actual modules, unless it is to test updates prior to copying the contents of the update module file back to the property.

 

Example of an empty (not modified) user class property:

 

using System;

using System.Security.Permissions;

using System.ComponentModel;

using System.Globalization;

using System.Data;

using System.IO;

using System.Runtime.Serialization;

using System.Runtime.Serialization.Formatters.Binary;

using System.Configuration;

using System.Text;

using FSCProLib;

using InsureUI2.Lists;

using InsureUI2;

namespace InsureUI2.Tasks

{

 /// <summary>

 /// This the generated "empty" class intended as a location for any overrides to

 /// methods contained in the HEFTY and chock-full of navigation logic ClientSupportTaskCG.

 /// This file is only generated once, then is not touched during regenerations.  So, you 

 /// can modify this file without worrying about regeneration and possible code merges.  Since

 /// the ClientSupportTaskCG file is almost always going to change as regenerations occur,

 /// this file is a good place to put your changes, as it is the one inherited by all the 

 /// task modules.

 /// </summary>

 public class ClientSupportTaskClientSupportTaskCG

 {

         /// <summary>

         /// Constructor

         /// </summary>

         /// <param name="ts">Active TaskSession object</param>

         public ClientSupportTask(TaskSession ts):base(ts)

         {

         }

 }

}