Q: Given the absence of reported errors or warnings during the migration of ScanTool, can I assume that there won't be a need for any manual adjustments? Furthermore, if I intend to build and run this .NET code within Visual Studio, should I expect a smooth process? (Note: I am not able to find a .exe file in deploy/bin) In the event that there were any errors during the migration, could you please direct me to the location within the tool where I can access a detailed error report? When the translator reports the translation was a SUCCESS it means that no errors were reported by the translation process.
A: Generally speaking you should always expect to make additional adjustments to complete your upgrade. However, making adjustments is usually done by changing the rules and translating again.
gmStudio does not produce a detailed error report telling you how to rewrite your code. However it can produce a variety of detailed reports describing the source code and the translated code that can help teams plan, track, and direct the progress of their upgrade effort. . Ultimately each team should define their project objectives and technical requirements based on their standards, budget, and other constraints. Rewriting VB6 for .NET software is not one-size-fits all and gmStudio is a platform to help you develop a solution that helps you more efficiently and accurately rewrite your code.
For example, here is a screen shot of the default (OOTB) ScanTool UI translation. Note that all of the controls are in the Document Outline even though the DriveListbox and FolderListbox render as transparent rectangles. This version does not run because it is linked to a stub framework.
Here is screen shot ScanToolUI translated using the custom rules provided with the WinForms ScanTool sample solution. This version renders properly in the designer and runs using actual .NET framework code.
And here is the same ScanToolUI sample translated using the custom rules provided with the WPF ScanTool sample solution. The WPF version uses XAML rather than as Designer.cs file. This version also runs.
All of these examples report a successful translation, but they all produce different results reflecting the rules used.