The Assessment Tool (run-time addition) is targeted to run on the compiled .NET assemblies (exe and dll) of your source application. Follow the steps below in order to assess the applications readiness.

Run the appropriate Assessment Tool executable (32bit or 64bit according to your OS) Extract the VWG_Analyzer.zip package, under which you should find two folders:

Within each folder you will find an executable of the Assessment Tool according to the selected platform; running it starts the following wizard:

Click Next and the wizard will walk you through the process.

Select the assembly files to be assessed; do select the assemblies for which you have the source code; do not select the assemblies of 3rd party components and external utilities of which you dont have the source code for. Click Add to add assemblies to the list of assessed files:

In this step you will get the list of dependent assemblies with 3 statuses:

• Open means that for this assembly, the source code is available according to your previous selection.
• Closed means that this is a 3rd party dependency assembly for which theres no access to the source code.
• Common System assemblies which Visual WebGui recognizes internally.

Verify that the results match your selections and then click Next.

The actual assessment process will fill the progress bar twice: the first pass is for collecting the information from the IL and the second pass is for analyzing the extracted the data.

After the process is finished, click Next.

This step shows the analysis summary:

Results summary explanations:

• X1% of your application can be automatically transported - X1% of the applications source code will be completely reused within the target Cloud enabled application.
• You have X2% warnings which needs to be revised for potential manual work - X2% of the application contains potential manual work but requires some deeper looking into in order to determine if those pieces of code do require manual work.
• There are X3% types which are used in the application and need to be replaced or created for the target platform - X3% of the types (classes, enumerations, structures etc) in the application do not have direct equivalent in the target platform (Visual WebGui) this means that those types should be replaced with either:
  • Existing similar types in Visual WebGui
  • Equivalent or similar 3rd party Web components (wrapping tasks)
  • Customized or extended Visual WebGui existing controls (customization task)
• There are X4% members which are used in the application and need to be replaced or created for the target platform - X4% of the members (methods, properties and fields) in the application do not have direct equivalent in the target platform (Visual WebGui) this means that those methods will have to be complemented, or the parent type should be replaced with a better matching type.
• X5% of the manual work is <complexity_level> complexity - X5% out of the manual work part is categorized as to a specific <complexity-level>; the complexity levels are:
  • Trivial (1) example: unmapped controls for which there is a fully equivalent control in Visual WebGui.
  • Very Low (2) example: events cross mapping to existing events
  • Low (3) example: mouse move event handling
  • Medium (4) example: missing ActiveX/COM type
  • High (5) example: overriding behaviors of Win32 messaging loops
• Estimated lines of code Y. - Since the tool runs on IL product (compiled solutions) and does not have access the source code, this number is calculated based on average # of IL statements per line of code, therefore, its estimation.
• Saving indicators:
  • X1% of your application can be transported automatically which saves you Y% compared to rewrite - This calculation is based on the level of automation discovered; your saving are specified in terms of efforts and is calculated comparing to complete application rewrite.
  • Upgrading this project will save you Z% compared to rewrite - The total saving % comparing to complete rewrite, is calculated taking into account the amount of manual work required and its different complexity levels adding the license fees for the automatic part.

Filling in some background details to help us help you with the process.

Note: those details will be attached to the report but will not leave your local machine unless you actively decide to click Send Report. However, it is highly recommended that you choose to send us the report, this will help us walk you through the upgrade process and recommend you on the best ways to tackle the upgrade process.

To view the report click on Show Report the report is shown in a browser which might require security approval to enable drill down capabilities (javascript).

To save the report locally (as a zip file), click on Save Report and then select the save path.

To send the report over to us, click on Send Report and the preffered SMTP application (i.e. Outlook) will open up a new email with the report already attached to it and Gizmox Sales email address to send to. You are welcome to provide background, additional details on the project and the motivations for moving the application to the Cloud within this email before sending it.

View the report locally within a browser

The first part of the report is a visual view of the same summary figures and estimates reported in the analysis summary above.

The second part of the report is a deeper detailed listing of the challenges with their category and suggested solution:

For each item on the list, the report specifies the usage intensively Reference Count, the nature of the issue with this item Issues and a high level recommended solution Solutions.

Drilling into the derails of an item will show the list of usages and the members involved.

At any time, it is highly recommended to consult with Gizmoxs support team as for the extracted results.

AssessmentTool page